Partners manage multiple Dynamic Yield customers in multiple accounts. Partners can create Partner Users, whose permissions apply across all of their associated accounts.
Managing partner users
Certified partners require access to multiple accounts (for each one of their customers). Partner users with Admin permissions can add additional partner users.
- Click the User icon at the top right corner of the screen, and select Manage <partner name> Users.
- Here, you can invite, delete, and edit users and their assigned permissions. Any permissions defined for partner users apply to all accounts associated with the partner account.
Managing your customer’s users
Partners that have Admin permissions can also manage the users in the accounts associated with the partner account. For example, if a person from a customer’s team wants access to one of their sites in the Experience OS, the partner’s admin can grant it.
- Click the User icon at the top right corner of the screen, and select Manage <account name> Users.
- Here, you can invite, delete, and edit users and their assigned permissions. Any permissions defined for these users apply only to the selected account.
For more details, see Managing Your Accounts and Teammates.
Both partner users and regular users have the same available permission levels. The only difference is that partner user permissions apply across all accounts associated with the partner account, and regular user permissions only apply to the account they are defined in.
- No access: The user has no access to the specific site.
- No role: User permissions to the site are configured manually by the admin.
- Admin: The user can edit all areas in the system, and can create new users and account sites. We recommend having at least one admin user.
Admins and editors have an additional level of permissions that disables or grants code-editing rights. Code editing rights should be reserved for technical users only, as the code can be used to manipulate any content on the website. The available code-editing permissions are as follows:
- Can view code: The user has viewing permissions for all code-based elements in the system (such as templates and evaluators). However, the code is always inactive and uneditable.
- No access to code: The user can't view any code-based elements in the system.