What are Roles?

A role is a collection of actions. An action identifies what functionality a user can access such as pages, menus, menu items, toolbars,and buttons. Secured actions are attributed to UI elements in the Application Architect and assigned to roles in the Web Client. Users are also assigned to roles, giving the user access to the role's actions. Tell me more...

Elements are secured in the Application Architect by assigning an action to them, or applying security. The value of the Applied Security property is the action name. To secure an element in the UI and allow users access to that element you must:

  1. Add an action to the Applied Security property for the element in the Application Architect. See the "Understanding Secured Actions" topic in the Application Architect Help for more information.
  2. Add the action for that element to a role in the Web Client.
  3. Assign users to the role.

Default Roles

By default, new users are assigned the Standard User role. This allows access to all non-administrative functions in the Web Client. If you remove a user from this role, the user will not have access to any items that are secured unless you assign a new role. Current secured entities are accounts, contacts, and opportunities.

The default roles are:

Security in the Network Client is defined using feature security, function security, and administrative roles. Web security combines all Network elements into one security model - a role. You cannot use the Network security model for a user who is logged into the Web Client or the Web security model for a user who is logged into the Network Client.

How do I?

Create a Role

Edit or Delete a Role

Assign a Role to Users

Add or Edit Role Actions

Assigning All Users to the Standard User Role

 

Tell us how we can make the Help better.