A role defines the privileges that a member has within an organization. Esri defines members of an organization as a User, Publisher, Administrator or custom roles. Each of these roles has different privileges that are defined by your organization's administrator. For more information, see Organization roles.
With the December 2016 update to Community Analyst, you will need a Publisher or Administrator role to fully use the application. This update introduced a Projects-based structure to help manage and organize your data more efficiently. All your content must be stored in a Project, and to create a new Project you must have a Publisher or Administrator role. If you currently have a User role, we recommend that you request that your Administrator to grant you a Publisher role.
With a User role, you will only be able to proceed to use the application by accessing a Shared Project, i.e. a project shared with you by other users. See Shared Projects.
Different Roles have different levels of access to functionality in Community Analyst:
- Users: are not able to create new projects, and are only able to use the features and functionality in Community Analyst by accessing Projects shared with them by other users, with limitations. It is recommended to request a Publisher role from the Administrator to fully use the application.
- Publisher: can fully use Community Analyst. The easiest way to enable users that currently have a User role to fully use the application is to grant them a Publisher role.
- Administrator: can fully use Community Analyst.
- Custom roles: these must be defined by the Administrator of the Organization. To use Community Analyst, a Custom role must have access to certain premium features, which are needed to use the complete functionality and features of Community Analyst:
In ArcGIS Online, Administrators may set up Custom roles with any combination of Privileges. To have a full access of Community Analyst using a custom role, all the privileges shown below must be included in that custom role.
To enable non-administrator users in your organization to collaborate on a shared project, you must grant them a custom role that includes the Update privilege, without which they will not be able to add or modify items in the shared project.