This article will help you:
- Understand the different permissions associated with Amplitude's user roles
User permissions define the level of Amplitude access a user in your organization will have. Usually, permissions are based on a user's role, though project-level permissions and permission groups are available for Enterprise customers who need the ability to better target levels of security.
NOTE: You may also find this course on administering Amplitude helpful.
The person who sets user permissions is the Admin. The Admin is the first user of any Amplitude organization, and each organization must have at least one Admin (any Admin can designate other users as Admins as well). When new users are first invited to an organization, they are assigned the viewer role by default.
In Amplitude, user permissions exist at the organization level. Once assigned a permission level, a user in an organization will then have the same level of access to all projects within that organization.
Learn more about how to create and manage organizations and projects, and how to manage users and permissions in Amplitude.
User roles and permissions in Amplitude
Role |
Permissions |
---|---|
Viewer Recommended role for third parties, if you do not want them creating content that the rest of the organization can find. |
Note that Viewers:
|
Member Recommend for the majority of Amplitude users in your organization. |
All Viewer permissions, plus:
Note that Members:
|
Manager Recommended for users who need access to all content created within Amplitude (does not include undiscoverable dashboards and charts) and ability to make changes to project settings. |
All Member permissions, plus:
|
Admin The highest-level permissions set in an organization. We recommend limiting the number of users in an organization who are Admins. The Admin role can only be granted or revoked by existing Admins. |
All Manager permissions, plus:
|
All users |
|