Skip to content
Help Center
Submit a request Sign in

Configure customer roles

Customer roles classify companies and contacts and can be used to restrict portal or knowledge-base content. They differ from agent roles, which control staff permissions inside Supportbench.

Applies to: Supportbench Core. Location: Settings → Customers → Customer roles. Editing requires Administer company and contact configurations.

Before you begin

  • Define the customer audience and its operational purpose. A Customer role differs from an Agent role and does not itself grant portal or article access.
  • If using Case ID mapping, review the existing mapping and expected prefix before assigning the role to a Company.

Configure and verify

  1. Open Settings → Customers → Customer roles and choose New Role.
  2. Enter Name and Description, then review Active. Use a name that identifies the audience, such as Product A support customers.
  3. For Case ID mapping, choose an existing mapping or None. This setting affects customer-created Case IDs in the applicable creation path; it does not rename existing Cases.
  4. Choose Save Changes and reopen the role. This editor has no Division or parent-hierarchy setting.
  5. Assign the role to an approved Company or Contact through that record’s Roles controls and save the customer record.
  6. Separately configure the intended portal, Topic or article audience where appropriate. Test both an included customer and an excluded customer; a saved role definition alone has not established that access.

Settings reference

Details and availability

SettingWhat it controlsHow to choose
NameThe label people select. Required; up to 50 characters.Use a short, distinct label that describes its purpose.
DescriptionAdministrative explanation; up to 250 characters.Explain when to choose this option, including an example if useful.
ActiveControls availability in standard selection lists. Inactive items remain saved.Deactivate obsolete options when you need to retain their configuration and existing references.
Case ID mappingUses the company’s assigned role mapping when a case is created. Choose an existing mapping from API → ID mapping.Create the required mapping in API → ID mapping first, then verify the resulting case IDs.

Behavior to know

  • Assigning a customer role and configuring content access are separate operations. Verify the full portal, topic, and article audience together.
  • Assign the intended mapped role to the company before creating a case, then verify the new case ID. Existing case IDs are not changed by later role changes. If a company has multiple mapped roles, confirm which prefix is applied.

Recommended use

  • Use terminology that agents and customers already understand. Explain the intended meaning in the description.
  • Keep the initial configuration small enough for people to choose consistently. Add options when they represent a real operational difference.
  • Review existing references before renaming, changing scope, or deleting. Where supported, deactivate an obsolete option before considering permanent deletion.

Worked example: give Controller customers the intended knowledge audience

  1. A support operation serves Controller and Gateway customers. These are illustrative product names. Create Controller support customers with a Description stating who qualifies; keep Active on when the role is ready. Leave Case ID mapping at None unless a separately approved identifier requirement applies.
  2. Choose Save Changes and reopen the definition. Select one approved test Company whose associated Contacts should share this entitlement, or one test Contact when the entitlement belongs only to that person. Assign the role through that record’s Roles controls and save the customer record.
  3. Inspect both the Contact’s own roles and the roles derived from its Company. A customer who already receives the role through the Company is not a valid excluded-reader test. Do not assign the role to an entire Company merely to give one person access.
  4. Separately configure the intended Topic/article audience using the knowledge access procedure. Review the portal and Division context as well. A customer role identifies an audience; creating or assigning it alone has not made a particular article readable or private.
  5. Test a direct link and normal knowledge navigation with an intended Controller customer and a controlled customer without that entitlement. Confirm the first can read the intended material and the second cannot. Also check an ordinary shared article that both should retain.
  6. If the results differ, inspect the actual role assignments and content/portal restrictions before changing them. Keep Case ID mapping out of this diagnosis: it concerns the applicable new-Case identifier path, not knowledge visibility.

Troubleshooting

ProblemWhat to check
The role cannot be selected on a customerCheck Active and reopen the Company or Contact editor.
Assigning the role did not restrict knowledgeRole assignment and content access are separate. Inspect the portal, Topic and article rules and test the actual reader.
Existing Case IDs did not changeExpected. Mapping changes affect the applicable creation path, not existing identifiers.
A new Case uses an unexpected prefixReview the Company’s assigned mapped roles and the current Case-ID mapping guide before changing the definition.
New Role or Save is unavailableCheck Administer company and contact configurations.
  • Organization → Configure agent roles and division access
  • Customers → Manage companies and customer organization details
  • Customers → Manage contacts and customer portal access
  • Knowledge Base → Organize knowledge-base topics and access
  • Self-Service → Configure a customer portal

Was this article helpful?