Information about managing B2C Commerce users, roles, permissions and OCAPI client IDs within Account Manager.
Please see the video and detailed instructions below:
Adding / Creating a User
You must be an Account Administrator to create an account. Each account must belong to at least one organization, and you can create accounts only for organizations of which you are a member.
Enabling / Disabling an Account
In terms of how Account Manager works, deleting the account moves it into a state where the user can no longer log in. The user account is not deleted and can be enabled again later which effectively 'disables' the account. Undeleting the account moves it into a state where the user can log in again and this action effectively 'enables' the account.
Note: Purging the account after deletion removes the user from Account Manager and is irreversible.
Unlocking a Locked Account
An account is automatically locked if multiple unsuccessful logins are attempted. If you are an account administrator, you can explicitly unlock locked accounts within your organization/s.
To unlock an account, follow the steps below:
Resetting a User Account
Account Administrators can use Account Manager to reset a user's account. This operation is useful if the user in question forgets or loses their login credentials. When you reset a user's account, you put the account in the same state it was in when it was initially created. This means the user must reactivate the account.
Follow the steps below to reset a user:
Account Manager resets the user's account and sends a message to the user's email address. This email message contains an activation URL, which serves as a starting point for the user to re-activate their account.
Notes
Adding a Client ID for the Open Commerce API (OCAPI)
Account Administrators and API Administrators can use Account Manager to create client IDs for the Open Commerce API, which requires that each client have a client ID. The client must append this ID to any URLs they use to interact with the Open Commerce API.
Any one of the following Roles are required for viewing the API Client ID tab in account manager -
A. Role - Account Administrator
Permits this user to view other user accounts. Permits this user to add other user accounts. Permits this user to edit other user accounts. Permits this user to edit API clients for their organization. Normally, only user accounts that belong to the same organization as the user are shown. If a user with the Account Administrator role is assigned to multiple organizations, the user is the Account Administrator for all of the assigned organizations.
B. Role - API Administrator
Permits the account to view API client IDs. Permits the account to add API client IDs. Permits the account to edit API client IDs. Enables the Account Manager API Client tab for the user.
C. Role - Read Only Account Administrator
Permits the user read only access to the organization's details, API clients and users. Users with this role can't update or create organizations, API clients, or users.
To add a Client ID, follow the steps below:
Note: By default, the client ID is enabled.
Enabling or disabling a Client ID for the Open Commerce API (OCAPI)
Account Administrators can use Account Manager to enable and disable client IDs for the Open Commerce API, which requires that each client have a client ID. The client must append this ID to any URLs they use to interact with the Open Commerce API. Client IDs are enabled by default; however, you can disable a client ID if necessary.
Follow the steps below to enable/disable a client ID:
Please see the Roles Managed in Account Manager topic.
000391212

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.