User Management on the Chord Platform
Collaborating with your colleagues is essential when it comes to store operations and analyzing your store performance metrics. The Chord Commerce Data Platform has three core permission levels that enable collaboration. These roles and permissions are outlined below.
Note: The Order Admin role is only applicable for Chord Autonomty customers that use Chord OMS to manage orders. Additionally, Chord Commerce team members are Super Admins on the platform and won't be visible on your team page or count toward your total platform user count.
Activity | Member (Regular User) | Order Admin | Team Admin |
|---|---|---|---|
Can view data & analytics dashboards | β | - | β |
Can create new custom reports using Explores functionality | β | - | β |
Can view and manage Chord OMS orders (Applies to Chord Autonomy customers) | β | β | β |
Can view team members | - | β | β |
Can invite new users | - | - | β |
Can remove users | - | - | β |
Can upgrade or downgrade user permissions | - | - | β |
Can update or edit Model Amplifications | - | - | β |
Can publish custom reports | - | - | β |
Can add data sources | - | - | β |
You need to have Team Admin level permissions to create a user on the Chord platform.
A Team Admin level user should follow the steps below to create a new user:
- Log in to Chord and click Team on the left navigation panel.
- Click Invite User.
- Select the appropriate role and related permissions for the user: Member, Order Admin, or Team Admin.
- Provide the userβs email address and click Invite to join.
- Once the newly invited user receives the invitation email, they will be prompted to provide their full name before their first sign-on.
- You can check whether or not the newly invited user established their account by viewing the status of their invitation on the Team page.
π‘ Developer documentation on SSO via Okta can be found here.
- The user logs into the IdP dashboard (e.g. Okta) and selects the Chord Hub application.
- Okta servers request that the user authenticate the login.
- On success, the user is redirected to the Chord platform.
- The user will automatically be granted Member (Regular User) level access to the Chord platform.
- The Chord platform validates the session information from the IdP and logs the user in.
You need to have Team Admin level permissions to upgrade roles and permissions on the Chord platform. On Chord, the Team Admin role is the role with the most permissions on the platform.
A Team Admin should follow the steps below to upgrade a team memberβs permission level:
- Log in to Chord and click Team on the left navigation panel.
- Click on an existing team member that is currently a Member or Order Admin.
- Select whether or not the existing team member should have Admin level privileges by selecting Team Admin in the dropdown selector.
- Click Save Changes.
You need to have Team Admin level permissions to downgrade another userβs permissions on the Chord platform.
A Team Admin user should follow the steps below to downgrade a team memberβs permission level:
- Log in to Chord and click Team on the left navigation panel.
- Click on an existing team member with Team Admin level permissions.
- Select either the Member or Order Admin role option, as applicable to the individual's role, via the dropdown selector.
- Click Save Changes.
To remove an existing user on the Chord platform, you need to have Team Admin level permissions.
A Team Admin user should follow the steps below to remove a collaborator:
- Log in to Chord and click Team on the left navigation panel.
- Click on the user you wish to remove from the platform.
- Click the Delete button.
- You can verify that the user has been removed by clicking back into the Team link.
Note that if a userβs SSO access is revoked, there is no way for that same user to log into Chord. Chord does not currently support automatic user removal in the platform if a user has been revoked access via SSO.
To remove an SSO user from the Chord platform, an existing Admin level user should log into Chord and delete the user following the steps outlined above in the βRemoving a Userβ section. Note that this step should be completed after the userβs access to the Chord platform via SSO has been removed.
Please contact [email protected] if you need help removing a user or have any questions about this process.