Skip to content
Help Center
Submit a request Sign in

Configure divisions

Divisions separate operational areas and provide scope and defaults for Case forms, reports, knowledge and related configuration. A B2B team can use them to distinguish service operations that genuinely need different handling, while keeping a simple root-and-child hierarchy. Create a Division because the service process needs that boundary, not merely because a customer or agent needs another label.

Applies to: Supportbench Core. Location: Settings → Organization → Divisions. Editing requires Administer divisions and an enabled editor. Lists and available choices are also limited by the administrator’s Division access.

Before you begin

  • Map the actual operational difference: Case forms, routing, reporting, customer knowledge or administrative ownership. If a Company, queue or view already expresses the need, consider that simpler structure before introducing another Division.
  • Review existing root and child Divisions and their references. A move, default change or deactivation can affect more than the list you are editing.
  • Confirm Administer divisions permission and the Divisions visible to your role. An incomplete list may reflect access scope, not missing configuration.
  • Identify the active reply address, permitted knowledge community and asset categories intended for this operation. Choosing a default community is separate from granting customers access to its articles.
  • Plan representative checks with an agent who should use the Division and one who should be excluded. Use approved sample records and avoid changing customer routing simply to demonstrate the setting.

Configure and verify

  1. Open Settings → Organization → Divisions. Review the hierarchy before choosing New Division or opening an existing entry.
  2. Enter a distinct Name and useful Description. Explain the service boundary, not just an internal abbreviation.
  3. Choose Parent division only when this is a child of a root Division. Leave Root division selected for a root. Only roots are valid parents; do not plan a third-level hierarchy.
  4. Review Active and Display order. New Divisions start Active with order 0. Choose an available Display order value; lower values appear first. The dropdown starts at 0 and its highest offered value depends on the current Division count, up to 25.
  5. Choose Default email and Default KB community only when they are the intended defaults. New entries start with neither selected; options depend on active configured addresses and permitted communities.
  6. Review Asset categories carefully. New Divisions preselect all active asset categories visible to the administrator. Reduce the selection to the categories appropriate for this operation instead of assuming the field starts empty.
  7. Save Changes, reopen the Division and confirm the hierarchy, active state, defaults and category selection.
  8. Refresh the relevant consuming forms/lists and test a representative Case and knowledge path with the intended agent access. Check an excluded Division/user too; the configuration save alone does not verify every downstream workflow.

Settings reference

Division profile

SettingWhat it controlsHow to choose
NameRequired, up to 50 characters.Use a recognizable service or operational name.
DescriptionUp to 250 characters explaining the Division’s purpose.Describe who owns the operation and when records belong here.
ActiveNew Divisions start active. Deactivation also deactivates descendants.Review the whole branch and dependent work before changing availability; reactivation requires a separate deliberate review.
Parent divisionOptional root parent. Root division means no parent. Only roots can be parents; self/descendant parenting and a third level are not supported.Use a two-level structure that people can explain.
Display order0–25; new entries start at 0 and lower values appear first.Put common operational choices in a sensible sequence.

Defaults and related records

SettingWhat it controlsHow to choose
Default emailDefault sender address from active configured reply addresses; none selected initially.Verify the intended customer-facing sender on a representative communication.
Default KB communityAssociated knowledge community from choices visible to the administrator; none selected initially.Check portal/article audience rules separately. A default is not a publication or access grant.
Asset categoriesCategories available through this Division configuration. New entries preselect active categories visible to the administrator.Keep the categories relevant to the service process and verify a representative asset-selection path.

Behavior to know

  • Division changes affect Case forms, reports, knowledge defaults and role-visible lists after configuration/cache refresh. Reopen the consuming surface before concluding that a saved change did not apply.
  • Deactivating a Division also deactivates its descendants. They disappear from active routing and selection lists; inspect the entire branch and arrange the intended operational replacement first.
  • A configuration change does not mean every existing record has been moved or rewritten. Review actual Cases and references before making that claim.
  • Role access and Division defaults are different controls. A new Division or knowledge-community default does not itself grant every agent or customer visibility.

Recommended use

  • Keep the hierarchy shallow and based on a meaningful operating boundary. Use Company records for customer context and queues for work ownership where those concepts fit better.
  • Choose defaults that reduce repetitive decisions without hiding important exceptions. Verify the actual From address, form and knowledge audience in the consuming workflow.
  • Document the owner of each Division and its key dependencies. This makes later reorganization safer than inferring intent from the name alone.
  • Prefer a reviewed deactivation plan over deletion when retiring a service area. Inspect descendants, routing and linked records, and read the complete confirmation for any destructive action.
  • When access is scoped, have an appropriately authorized administrator review the full intended structure. Do not broaden a role merely to make a missing choice appear.

Worked example: regional B2B service operations

  1. A supplier has separate regional support operations. It uses regional root Divisions and adds a child only for a business unit that needs distinct forms, reporting or knowledge defaults.
  2. The administrator creates the appropriate root or child, selects the service reply address and knowledge community, and reviews the preselected asset categories.
  3. The team configures the related queues, Case policies and role scope separately; creating a Division does not automatically create these processes.
  4. A representative agent creates an approved sample in the intended Division, verifies the form and relevant choices, then checks the correct customer-facing sender and knowledge access.
  5. Before retiring a regional branch, the team maps the child Divisions and dependent work, prepares the replacement route and verifies the effect of deactivation rather than treating it as a cosmetic list change.

Troubleshooting

ProblemWhat to check
A Division is missingCheck active state, parent/descendant deactivation and the current role’s Division scope. Refresh the consuming list after a saved configuration change.
A parent cannot be selectedOnly roots may be parents. Check that the proposed parent is a root and that the choice would not create a self/descendant relationship or third level.
An asset category was selected unexpectedlyNew Divisions preselect active categories visible to the administrator. Review and save the intended subset.
A default email or community is missingCheck active reply-address configuration and the administrator’s community access. A default picker is not a permission bypass.
Several child Divisions became inactiveParent deactivation cascades to descendants. Review the branch and intended restoration deliberately rather than assuming reactivating one row restores every dependent process.
Existing Cases did not moveA Division configuration edit is separate from changing existing records. Review the intended migration or reassignment process with the responsible owner.
The save is rejectedCheck Name/Description limits, permitted parent and role scope. Keep Display order within 0–25.
Another agent sees different choicesCompare role scope and the active configuration used by that session; do not assume everyone has the same list.
  • Email configuration → Configure reply addresses and signatures
  • Self-Service → Configure a customer portal
  • Assets → Configure asset categories
  • Organization → Configure agent roles and division access

Was this article helpful?