Update Amplitude Roles for the collaborator

Adjust the collaborator’ permissions whenever project scope changes or additional Amplitude modules come online.

When to Make Changes

A new product project is added and the collaborator needs to QA instrumentation.
Govern or Experiment is purchased and the collaborator should help administer tracking plans or experiments.
Access should be restricted to specific projects as workstreams wind down.
Your security team updates SSO group mappings or MFA requirements.

Navigate to Settings → Members & Groups and open the collaborator’s account.
Review the Organization Role and toggle admin rights if the collaborator needs to manage billing, SSO, or integrations.
Under Projects, adjust the list of assigned projects and set the correct project role for each.
Enable or disable add-on module permissions (Govern, Experiment, Accounts) as requested.
Save the changes and note the request ID or ticket number in the user’s comment field.
Notify the collaborator’s lead so they can validate access on their side.

Confirm the change in the Access Log to ensure it was recorded.
Ask the collaborator to refresh Amplitude and verify that dashboards, charts, or data tools align with expectations.
Update your IAM tracker or CMDB with the adjustment date and summary.

Tracking Plan collaboration: Assign the Tracking Plan Editor role in Govern so the collaborator can approve events.
Service accounts: For ingestion keys or data pipelines, use dedicated service users rather than the analytics login.
Temporary elevation: Set a reminder to revert admin rights after the requested work completes.