Update Heap Analytics Roles for the collaborator
Modify the collaborator’ Heap permissions when new projects launch, governance responsibilities shift, or access should be reduced.
When to Update
- Additional projects (web, mobile, staging) need to be shared.
- the collaborator begins managing tracking plans via Heap Govern or customer messaging via Heap Engage/Activate.
- Engagement scope narrows and read-only access is sufficient.
- Security reviews require MFA, SSO group changes, or IP restrictions.
Update Workflow
- Open Account → Manage → Members and locate the collaborator’s account.
- Adjust the Organization Role (Admin, Member) depending on the required privileges.
- Modify the project list and select the correct project roles for each environment.
- Enable or disable Govern/Activate permissions as requested.
- Save the changes and note the ticket or request reference in your IAM log.
- Notify the collaborator so they can confirm the changes on their side.
Validation
- Check the user record for the correct roles and project assignments.
- Ask the collaborator to log in and confirm dashboards, tracking plans, or messaging tools reflect the update.
- Export the Access Log entry for your compliance archive.
Related Tasks
- Update SCIM or SSO groups if provisioning is automated.
- Rotate any ingestion keys or API tokens handled by the collaborator’s account when privilege levels increase.
- Review scheduled reports or webhooks to ensure ownership remains accurate after the change.