Skip to Content
Author's profile photo Suman Saurabh

Business Roles – Field & Action Restrictions

You have a scenario where you want to restrict the access of an Employee/Business User to some Fields & Actions.


Scenario: A new employee John Kerry has joined your organization; as an administrator your task is to create the employee ID for him and assign the required authorization. The Sales Manager has requested you to disable Set as Lost action for John Kerry in the Opportunities and set the read-only access for the Probability field on opportunity header.

To achieve the requirement, you need to:

  • Create a New Employee ID.
  • Create a Business Role.
  • Enable the Fields & Action Restriction in the Business Role.
  • Assign the Business Role to the Business User generated for the new employee.


Admin_General_Settings.JPG



Step 1: Create a New Employee ID for John Kerry:

  1. Login to the Silverlight UI.
  2. Go to the Administrator work center.
  3. Go to the General Settings view.
  4. Click on Employees under Users section.
  5. Click New button -> Select Employee.
  6. Add mandatory details.
  7. Save the Employee -> So John Kerry has been hired as an employee.
  8. Go to the Application and User Management work center.
  9. Go to the Business Users view.
  10. Search for the Employee John Kerry.
  11. You will find that a Business User is already assigned to the John Kerry.


Employee_Creation.JPG


Step 2: Create a Business Role:

  1. Login to the Silverlight UI.
  2. Go to the Application and User Management work center.
  3. Go to the User and Access Management view.
  4. Go to the Business Roles sub view.
  5. Click on New button and select Business Role.
  6. Add Business Role ID, Name & Description in the General tab.
  7. Go to the Work Canter & View Assignments tab to assign the required work centers & views.
  8. Go to the Access Restrictions tab to define the required authorizations.
  9. Select Actions and click on Activate.
  10. Save the changes.


WC_Assignments.JPG


Step 3: Enable Fields & Action Restriction in a Business Role:

  1. Login to the Silverlight UI.
  2. Go to the Application and User Management work center.
  3. Go to the User and Access Management view.
  4. Go to the Business Roles sub view.
  5. Search and open the Business Role.
  6. Go to the Fields & Actions tab.
  7. Use Business Field Restrictions, Extension Field Restrictions & Business Action Restrictions sections to add field & action restrictions.
    • You can Restrict the Fields & Actions for the Business Role.
    • Mark Probability field of Opportunity as Hidden and mark the action Set as Lost as Disabled.
  8. Save the changes.


Field_Action_Restriction.JPG


Step 4: Assign the Business Role to the Business User:

  1. Login to the Silverlight UI.
  2. Go to the Application and User Management work center.
  3. Go to the User and Access Management view.
  4. Go to the Business Users sub view.
  5. Edit the Access Rights of the Business User.
  6. Go to the Business Role Assignment tab.
  7. Select Business Role and select the checkbox Assigned to User.
  8. Save your changes.


BR_Assignment.JPG


Step 5: Check if the above changes have been applied to the Opportunities for user John Kerry:

  1. Login to the HTML UI with the John Kerry user.
  2. Go to the Sales work center.
  3. Go to the Opportunities facet.
  4. Create a new opportunity.
  5. Here you can see that the Probability field is hidden for the user.
  6. Add other mandatory details in the opportunity.
  7. Select Save and Open.
  8. Select the Actions button – the option Set as Lost is grayed out for the user.


Assigned Tags

      5 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo C4C Admin
      C4C Admin

      Hello Suman,

      It is nicely explained for defining new business roles and restriction.

      I am looking for providing access restriction/authorization of one document type (for example ticket type T1) to one business role BR1 and other ticket type T2 to other business role BR2. So then the user assigned to business role BR1 can only maintain the ticket type T1 and other user assigned to business role BR2 can only maintain the ticket type T2.

      I tried but did not find any option to get this done. Do you have any idea to achieve this?

      Regards,

      Harshad Patel

      Author's profile photo Suman Saurabh
      Suman Saurabh
      Blog Post Author

      Hi Harshad,

      If Ticket type is a Drop Down field, then you can use "Code List Restrictions" to restrict the values.

      You may check below blog related to CLR:

      How to Use Code List Restrictions to Control Dropdown Field Values

      Regards,

      Suman

      Author's profile photo Former Member
      Former Member

      Very useful information, thanks Suman.

      Author's profile photo C4C Admin
      C4C Admin

      Hello Suman,

      We are working on PCM PORTAL for partner user and we are facing issue on access/authorization. We want lead to be forwarded to partner by brand owner and partner can also create the lead themself.

      Currently all lead created in C4C are visible to all partner user. We want lead assigned to specific partner can only be visible to that partner only. i.e. one partner can not see leads of other partners.

      I checked the access context for lead "1015" but unable to set that way. i.e. either through 'partner' role from party-involved tab or through "Sales unit" of partner (partner org. unit defined as 'sales unit' in brand owner org. structure and all partner contact user assigned to that sales unit as employee).

      Can you please suggest to control access to partner for lead?

      I understand the option like ACE in on-prem CRM is not provided in C4C but looking for same kind of way/option in C4C for partner access.

      Thanks,

      Harshad Patel

      Author's profile photo Suman Saurabh
      Suman Saurabh
      Blog Post Author

      Hi Harshad,

      I do not know how to achieve this.

      I would suggest you to raise this question in a separate thread.

      Also check below blog:

      Access Control Management: Access restrictions explained - Access Context

      Regards,

      Suman