You are here:
Administrator Role in B2C Commerce
The administrator role is the top-level role for an organization. This role is automatically created and can't be deleted directly or indirectly by import. This topic applies to B2C Commerce.
The administrator role has the following properties:
- Is always available in a new instance.
- Cannot be deleted through B2C Commerce tools or the import.
- Has access to all known system modules in all known sites (per organization).
- Automatically gets access to all system modules of a newly created site.
- Automatically gets access to new modules when deploying new releases (for all organizations and sites).
- Can be extended with functional permissions.
- Can be extended with access permissions for custom modules.
- Can access permissions on all locales assigned to all roles. For locales created after Release 16.9, administrators must explicitly grant locale-specific permissions to a relevant role.
Administrator access for all system modules is ensured via the following mechanisms:
- When a new site is created, the administrator role automatically receives the required access permissions for all site system modules. The administrator role maintains full access to all modules within all sites.
- When the server starts, B2C Commerce checks whether the organizational and site level administrator roles still have access to all known system modules in all sites. The administrator role automatically gets access to newly introduced system modules (for example, when deploying new releases).
Retrieving Passwords
We recommend that all customers and partners have one administrator who is responsible for the passwords of all their instances. This administrator is usually the default admin user account included with every new instance. The admin user can create other named accounts that also have administrator permissions.
Developers use their own accounts to access instances and don't change or reset the global administrator password. After a dbinit is run on a sandbox, the administrator is responsible for changing the passwords for the sandbox back to the original passwords. See Using Dbinit.
Security settings let the administrator configure Business Manager passwords behaviors. An administrator can retrieve or reset a forgotten password using the Forgot Password feature.
Import and Export
The import logic rejects deletion attempts for the administrator role (for example, via DELETE mode import). The import logic also rejects any modification of system module access privileges (for example, via REPLACE mode import). The import log records both cases as warnings.
Business Manager Module Permissions
Module permissions grant access to specific Business Manager modules. If a logged-in user has permission to access a Business Manager module, the application appears in the left navigation pane.
Grant read-only permission to certain modules and preferences. Users with read-only permission can view preferences and modules, but can't edit them. Read-only permission is available for the following modules: customers, products, product sets, global custom preferences, Content Assets, Customers, Inventory Lists, Job History, Libraries, Library Folders, Ordering, Price Books, Products, Product Sets, Site Preferences, and Variation Attributes. Enabling write access also enables read access.
You can also grant read-only permissions to Business Manager modules for all site-specific preferences. These preferences include locking, baskets, A/B tests, locales, currencies, source codes, gift certificates, guided search, sequence numbers, order, coupons, promotions, storefront toolkit, storefront URLs, system object definitions, and custom preferences.
If a Business Manager module provides site-specific functionality, permission is granted in context of that particular site or the entire organization. For example, orders are managed in the context of a site, so the permission on the Ordering module is granted in the context of the site.
Business Manager Locale Permissions
Business Manager supports localization of business objects. Specify which users have access to a locale's data.
To give users access to a locale, first create a role using the Locale tab on the Roles and Permissions page. Assign the role to the user. Enabling write access also enables read access. Because every role requires read permission for at least the default locale, read permission is automatically assigned.
For example, a user with write permission can edit products within a locale. The user can edit localizable fields, such as description and name, and non-localizable fields, such as the brand and the merchandiser.
A user with read permission only on the selected locale can't edit any fields, even non-localizable fields.
Business Manager Functional Permissions
Functional permissions aren't associated with a B2C Commerce tool module. They let a user perform specific functions in B2C Commerce.
For example: to make Alice an agent who can log in on behalf of any customer of site ABC,
Alice needs the functional permission
Login_On_Behalf
for site ABC.
To edit data, these permissions must be combined with Business Manage module permissions.
Organization-Wide Functional Permissions
The following table lists the functional permissions that apply to your organization as a whole:
Site-Wide Functional Permissions
The following table lists the available functional permissions to restrict a role to a specific site or sites.
WebDAV Permissions
To grant access to specific WebDAV folders, use WebDAV permissions. WebDAV permissions apply to your entire organization.
| Permission | Description |
|---|---|
/cartridges
|
Write access to the files in the /cartridges folder
and its subfolders. |
/catalogs/*
|
Read or write access to your organization's catalogs. You can grant access to all catalogs or selected catalogs. |
/dynamic/*
|
Read or write access to your organization's dynamic folders. Grant access to all dynamic folders or selected dynamic folders. |
/libraries/*
|
Read or write access to your organization's libraries. Grant access to all libraries or selected libraries. |
/realmdata
|
Write access to the files in the /realmdata folder
and its subfolders. |
/securitylogs
|
Read access to the files in the /securitylogs
folder and its subfolders. |
| (all other folders) | Read or write access to other top-level folders. |
Permissions for Impex Folders
If you grant permission to a root folder with an asterisk, B2C Commerce grants full permission to all its subfolders, even if you haven't granted permission to a specific subfolder. For a subfolder with an asterisk, B2C Commerce also grants read and write permissions to all its subfolders unless you set permission for a subfolder to read only.
For example, the root
folder /impex/* has an asterisk. You have access to
/impex/subfolder, even if permission isn't granted.
For the subfolder /impex/test/*, select the read option to
limit access to /impex/test/subfolder as read only.

