Access Rights

By default, EPiServer Commerce uses a customized role and membership provider where users are stored in the Commerce Manager database. Users with Commerce Manager accounts will be available both from inside Commerce Manager under Customer Management, as well as from the EPiServer CMS Admin modeSystem administrators will work in the EPiServer CMS Admin mode to administer the system, for instance to modify system settings and access rights for the entire website.. You will administer access rights both for users working with web shop administration in Commerce Manager, as well as users working with editorial contentContent such as articles or news, created by website editors through the EPiServer CMS editorial interface. Compare this to content that is displayed as pages on the website, but where the content itself is data fetched from Commerce Manager. This type of data cannot be only be edited in Commerce Manager. in the CMS system. These may or may not be the same individuals, depending how your organization is set up.

The user1. The number of unique IP adresses that visited this page/URL during a specified period. 2. A person using a product, or someone visiting a community website either anonymously or as a registered member. administration in Commerce Manager is based on contactsUsers that are created either when an external customer registers on the public site or when a Commerce Manager admin creates them directly from the Commerce Manager; typically, users that are internal to your organization are assigned to organizations or organization units and assigned varying permissions based on role. By default, new users that are created by registering from the public site are given the "Registered" and "Everyone" roles.. A contact can have an accountA user account that can be created under a Contact. Once an Account has been created, the Contact can be assigned Roles and access the Commerce Manager. A user account is automatically created for a user who registers from the front-end public website which allows a customer to login prior to checking out. They default to the "Everyone" and "Registered" roles and permissions. associated with it, which is needed if you want to assign Commerce Manager access rights to that contact. Only contacts with associated accounts will appear in the CMS user administration interface.

A contact must have an account associated with it to in order to be able to apply rolesThe Commerce Manager system has its own set of user roles covering the different tasks that online store managers work with. Order Supervisor, and Order/Shipping/Receiving Manager are examples of the role setup. There are also roles for managing the website as such, for instance editor or administrator. A "visitor" to the website is also a role in this context. Roles control the level of access privileges of each user account in Commerce Manager. Users can be either granted or restricted access to an entire subsystem or a particular menu item within a subsystem based on the role assigned to them. Different roles may be added to user accounts (i.g., store operator or webmaster) so that they can access, edit, or process relevant information. By default, a customer who registered his/her account to make a purchase in the front-end site will have no roles assigned to them, hence giving him/her preventing access to both the editing feature of the front-end site as well as the back-end Commerce Manager. and set access rights in Commerce Manager and the CMS system respectively. Users created from the CMS Admin interface will not appear in Commerce Manager.

When an online shopper decides to register with the website, a contact with an account is created. However, anonymous shopping is allowed, which means that shoppers are not required to create an account in order to purchase. Contacts can belong to organizationsGroups or sub-groups of registered users and customers. An organizational unit is a "child" or subsidiary of a "parent" organization. Within Commerce Manager, you can assign an organization as a parent of another organization. For example, the parent company Company X, and the organizational units are Company X West and Company X East. Organization units include regional branches or departments or you could name them by business categories such as "Computer and Electronics" or "Clothing and Accessories." Organizations can be structured into a tree structure with sub-units with different levels of permissions assigned to each. So for example, you can set up your company as a parent level organization while your departments such as Sales & Marketing, IT/Development, and Operations as organization units. With this scenario, you can allow users in each departments to have access to only relevant subsystems, screens and functionality within Commerce Manager. Same as "organization units".. The relationship between organizations, contacts, accounts, roles and user groups, is illustrated below.

Contacts, accounts and organizations are administered from the Customer Management system in Commerce Manager. This includes managing user accounts and adding roles to users (contacts). Setting access rights for editorial content management in the page tree of the website is done from the CMS administration interface.

The EPiServer Commerce sample site has a number of predefined users, roles and groups both for administering e-commerce tasks as well as managing editorial content. Remember that these users and groups are only examples of how you can set up access rights for your website.

Version: EPiServer Commerce 1 R2 SP2| Last updated: 2012-09-20 | Copyright © EPiServer AB | Send feedback to us