Help center Core configuration Assets Configure asset categories Updated Thursday, October 29, 2026 · Marc Staine Asset categories organize products, equipment or other supported assets into a useful hierarchy. Division scope helps teams select the categories relevant to their work. Applies to: Supportbench Core. Location: Settings → Assets → Categories. Editing requires Administer asset categories and the intended Division scope. Before you begin You need Administer asset categories and the intended Division scope.Plan the category hierarchy around supported assets and review existing assets before changing a parent or availability.Review the saved result and a controlled example in the consuming workflow. Configuration, customer access and actual delivery or processing are separate checks. Configure and verify Open Settings → Assets → Categories and choose New Category or open the intended category.Enter Name and Description, review Active and choose Parent category only when the category belongs in that branch.For a root category, choose the permitted Division where required. Child categories inherit the parent’s Division behavior described in the field reference.Choose Save Changes and reopen the category. Inspect the hierarchy and availability.Use a controlled asset with an intended agent to verify the category choice. Test an excluded Division/context where the category is restricted. Settings reference Category definitionSettingWhat it controlsHow to chooseName / DescriptionIdentifies and explains the record.Use terminology your team recognizes.ActiveControls normal availability.Review references before deactivating.Name / Description limitsName up to 50 and description up to 250 characters.Keep category names concise.Parent categoryPlaces the category in a hierarchy and participates in inherited division scope.Choose a parent that accurately represents the relationship.DivisionOne division for a root category. Child categories inherit their parent’s division.Review the inherited division before moving a category and check its availability from the intended division. Behavior to knowReview parent and division effects together when reorganizing a category. 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: organize supported equipment without changing Case routing An equipment-support team needs an illustrative Industrial equipment category with a Pumps child category. Agree which existing assets belong in each branch and identify the intended Division before changing a live hierarchy.With Administer asset categories, create the root category in the permitted Division and save it. Create Pumps with Industrial equipment as Parent category, then review the inherited Division rather than assuming the child creates an independent scope.Reopen both categories and verify Active, parent and saved Division behavior. Use a controlled asset and an intended agent to confirm the correct category can be selected; where scope is restricted, test an excluded Division/context separately.Check an existing asset before and after a planned category edit. Changing the category definition does not automatically move that asset into another category. Assign asset categories deliberately through the asset’s own workflow.Use the hierarchy to help agents recognize product context. It does not itself route a Case or establish a service commitment; review any consuming policies or workflows separately before relying on those outcomes. Troubleshooting ProblemWhat to checkThe category is missing for an assetCheck Active, parent hierarchy, inherited/permitted Division and the actual agent/asset context.The child uses a different Division than expectedReview its parent and the inherited category scope before changing the branch.A root cannot be saved globallyUse a permitted Division when your administrator scope requires it.Existing assets did not move categoriesCategory configuration and changing each asset’s category are separate operations. Related configuration Assets → Configure assets and their customer relationshipsOrganization → Configure divisionsUse assets and categories to understand what your customers depend onManage companies and contacts with the full support relationship in view Was this article helpful? Yes No Thank you for your feedback.