How Departments work in Continu — added to user profiles, used to search, assign, and segment. Supports two levels of sub-departments.
Departments are one of Continu's core user attributes. They land on user profiles via HRIS sync, SCIM, or manual entry, and they drive search, assignment, segmentation, and reporting throughout the platform. Setting up Departments well is foundational — once they're wrong, every downstream Smart Segment, Profile, and Automation that uses them is wrong too.
Departments support two levels of sub-departments below the parent, so an org structure like Engineering > Platform > Infra is representable.
For broader user management context, see User Management: Who Has Access to What, and Why.
How to Manage Departments
Navigating to Departments. From the left-hand navigation, click Connect > Departments.
Adding a Department
Step One: Navigate to Connect > Departments.
Step Two: Click the Add Department text cell, enter the Department name, click the + icon to finalize.
Adding a Sub-Department
Step One: Navigate to Connect > Departments.
Step Two: Click the parent Department. The Sub-Department column highlights.
Step Three: Click the Add A Department text cell in the Sub-Department column, enter the name, click the + icon.
Editing a Department
Click the pencil icon next to the Department, change the name, click the check icon to confirm.
Deleting a Department
Click the pencil icon next to the Department, then the red trash can icon. Users previously in the deleted Department lose that attribute and need reassignment.
Considerations
Match your HRIS structure. If Departments are synced from an HRIS, the structure in Continu should match what's in the HRIS. Otherwise sync errors and mismatched attributes cause downstream issues.
Resist over-nesting. Two levels of sub-departments is enough for most orgs. If you find yourself wanting three or four levels, you may be conflating Department with another attribute (Team, Function).
Plan for org changes. Departments reorganize over time. When they do, Continu's Department values need to update too. Build a process for catching reorgs before they break Smart Segments and Automations.
Use Departments for content scoping, not for everything. Department is one of many user attributes. Use it for what departments naturally mean (content audience scoping, manager hierarchies). For other patterns (skill-based, location-based), use other attributes.
Configuration Pitfalls
Department Names That Don't Match HRIS. "Engineering" in Continu vs "Eng" in HRIS means sync mismatches and broken segmentation. Match exactly, including capitalization.
Deleting Departments With Active Users. Users in a deleted Department lose the attribute, which can break Smart Segments and Automations that depended on it. Reassign users before deleting the Department.
Using Departments to Encode Geography or Function. Departments should mean "department." Geography goes in Location; function goes in Job Title or a custom attribute. Mixing meanings into the Department field makes downstream queries harder.
Letting Sub-Departments Drift. Sub-departments often reorganize internally without HR doing a full hierarchy update. Verify sub-department accuracy periodically.
Forgetting Department Drives Automations. Many Automations trigger on Department membership. Renaming a Department can break those Automations silently. Audit before renaming.
Where This Fits
You're here because you're setting up or managing Departments. For broader user attribute management, see User Management: Who Has Access to What, and Why. For how Departments drive Automations, see Automation Audience Trigger Guide.
See Also
- User Management: Who Has Access to What, and Why — the strategic anchor.
- Locations in Continu — location attribute.
- Levels in Continu — level attribute.
- Skills in Continu — skills attribute.
- Categories In Continu — content categorization (distinct from user Departments).
- Automation Audience Trigger Guide — how Departments drive Automations.
Match HRIS structure exactly. Two levels of sub-departments is enough. Reassign users before deleting. Don't encode geography or function in the Department field.