Context
Google Tag Manager allows you to delegate access to other users at the Account and Container level. Users can be granted the ability to view or administer other users at the Account level and can be granted read, edit, approve, or publish rights at the Container level.
Add Hyly.AI as a user to the Tag Manager account
To add Hyly.AI as a user to a Tag Manager account:
Edit users on an account.
To edit an existing user on a Tag Manager account:
Step 7 - Click Save to save your changes.
Add Hyly.AI as users to a container
To add user permissions for a specific container:
Edit user access to a container.
To edit user permissions for a specific container:
Invitations
If a Tag Manager administrator has added a user to a Tag Manager account, that user will receive an invitation to access the account. The user will be notified via email, and an invitation card will appear on the Tag Manager's Accounts screen. Click the Invitations card to view the list of invitations. Expand an invitation entry to view the details of the invitation. Click Accept to accept the invitation or Reject to cancel the invitation.
Account permissions
Account permissions at the account level can be set to Admin or User. You may also fine-tune permissions for specific containers on the Container Permissions table.
Container permissions
Access can be assigned on a per-container basis. For a given container, a user may be assigned:
- No access: The user will not see the container listed in the account.
- Read: The user will see the container listed and may browse the tags, triggers, and variables in the container but will not have the ability to make any changes.
- Edit: The user can create workspaces and edit but not create versions or publish.
- Approve: The user can create versions and workspaces and make edits but not publish.
- Publish: The user has full rights to create versions and workspaces, make edits, and publish.
A permission level is considered "inherited" if it is received indirectly from another place, such as a user group or organization role. A permission is considered "direct" if it is explicitly assigned to the user. Direct permissions will persist even if the user loses an inherited permission.
Next: