This article helps you:
Enable users to access Amplitude projects in your organization, and manage how they do it
Before a user can gain access to any Amplitude projects, you will have to add them to your Amplitude organization. You should do this immediately after creating an organization. Additionally, you’ll probably need to add new team members on a case-by-case basis as your organization changes and grows.
User management is done from the Members page, which you can reach by navigating to Settings > Organization settings > Members & Groups.
At the top of the page, you’ll find an overview of users for your organization: the number of total users, joined users, pending users, and users requesting access.
This section will review some common user management tasks.
Only admins and managers can add or remove users.
To invite new users, follow these steps:
In addition to inviting users to the organization, you can also allow team members to request access. They’ll be able to request it from the login page, an action that will prompt admin approval.
To turn this setting on, navigate to Advanced Settings and switch the Allow Team Members to Request Access toggle to Enabled.
At this time, user email address cannot be changed because it is a unique identifier for Amplitude user accounts. To work around this, you can follow these steps:
Repeat the process for other users who also need to change their email address.
All current users will be visible in the Joined Users view, while Pending Users shows those who still have an outstanding invite. An admin or manager can adjust any user's organization role or permissions with the dropdown menu in the Role column. Enterprise customers with project-level permissions enabled will need to select the checkbox next to a user's name to manage their individual permissions.
To change user permissions in Amplitude, follow these steps:
You will not be able to change the role for the only Admin in an organization.
When you remove a user, all their content (charts, dashboards and cohorts) will be designated as unassigned. Admins can transfer ownership of unassigned content to other users.
With project-level permissions, a user can have a different role for each project within an organization. This enables multiple teams in your company to operate autonomously and manage their own datasets. For example, a user may have Manager-level permission in one project, but Viewer-level permission in another. Users without access to a project cannot view any content that belongs in that project.
Project-level permissions are available to customers on Growth and Enterprise plans only.
When viewing all members of your organization, members will either be listed as User or Admin. If you are an Admin or Manager of a project in the organization, you can view and modify an individual member's role per project by clicking the checkbox next to the member's name and selecting "Manage Project Access". Managers will only be able to modify a user's role for the project where they are a Manager.
Please reach out to your Customer Success Manager to enable project-level permissions as this is not enabled by default.
When a user leaves the company or is otherwise no longer part of an Amplitude organization, any content they created will no longer have an owner. Depending on the nature of that content, situations like this can significantly hamper your company’s analytics work.
Admins can avoid this by using the bulk transfer ownership feature to designate another user as the owner of that orphaned content. Navigate to Settings > Organization settings > Members & Groups, and then click Bulk Transfer Edit Access.
This process cannot be reversed, so use it with care.
You can also transfer content when you’re removing a user. Simply check the box on the Remove Members? modal, and Amplitude will give you the option to transfer each removed user's content to another existing user.
Note that you can only transfer a user’s content before they are deleted from the organization. The user who receives the content must have logged into Amplitude at least once in the 30 days prior, and you may have to explicitly grant them the permissions they need to access the content you’ve given them.
Things to know before doing an email domain migration:
To request an email domain change, submit a ticket with the following information:
An admin must request email domain changes. If you are not an admin of the organization, CC an admin in your request.
Thanks for your feedback!
June 6th, 2024
Need help? Contact Support
Visit Amplitude.com
Have a look at the Amplitude Blog
Learn more at Amplitude Academy
© 2024 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.