Skip to content

Departments

Organize your team into a hierarchical department structure with per-member data visibility controls.

Departments allow you to model your real-world organizational structure (e.g., Sales > Enterprise > Account Managers) and control which data each team member can access.

Related Modules:

Departments support parent-child relationships for multi-level hierarchies:

Sales
├── Enterprise Sales
│ ├── Account Managers
│ └── Solution Engineers
└── SMB Sales
Engineering
├── Backend
└── Frontend
FieldDescription
NameDepartment name
DescriptionOptional description
ParentParent department (for hierarchy)
ManagerDepartment manager
ActiveActive/inactive toggle
Display OrderSort ordering

Restructure your organization by dragging departments in the tree view:

  • Drag a department onto another to make it a child
  • Drag to root level to make it a top-level department
  • Members stay with their department during reorganization

Each organization member can belong to one department:

  1. Go to Settings > Departments
  2. Select a department
  3. Click Add Member
  4. Choose from unassigned team members

Members without a department appear in the “Unassigned Team Members” section.

Each department can have a designated manager. The manager’s data visibility can be configured independently.

Data visibility controls what records each team member can see. This applies to Contacts, Deals, Activities, and Projects.

LevelRecords Visible
AllAll records in the organization
DepartmentRecords owned by members in the same department (and child departments)
OwnOnly records the user personally owns
  1. Each member has a data visibility setting (configurable per member)
  2. When viewing lists (Contacts, Deals, etc.), the system filters records based on visibility
  3. Unowned records (no assignee) are visible to everyone regardless of visibility setting

Visibility is set per member, not per department:

  1. Go to Settings > Departments
  2. Click on a member
  3. Select their data visibility level: All, Department, or Own

Visibility works alongside role-based access:

RoleVisibility Effect
OwnerAlways sees all data (visibility ignored)
AdminVisibility applies, plus sees assigned users’ data
ManagerVisibility applies, plus sees assigned users’ data
UserVisibility applies strictly

When set to “Department” visibility:

  • User sees records owned by anyone in their department
  • Includes records from child departments (recursive)
  • Always includes their own records

Scenario: Regional Sales Manager

  • Department: “Enterprise Sales”
  • Visibility: “Department”
  • Can see: All deals owned by Enterprise Sales team members and sub-departments

Scenario: Individual Contributor

  • Department: “SMB Sales”
  • Visibility: “Own”
  • Can see: Only their personally assigned contacts and deals

Scenario: VP of Sales

  • Department: “Sales”
  • Visibility: “All”
  • Can see: All contacts, deals, and activities across the organization

Not all entities are affected by data visibility:

EntityVisibility Scoped?Notes
ContactsYesOwner-based
DealsYesOwner-based
ActivitiesYesOwner-based
ProjectsYesOwner-based
Price OffersYesInherits from related contact’s owner
TicketsYesOR logic: assignee OR owner OR follower
AccountsNo (global)
ContactsNo (global)
RequestsNo (global)
SettingsNo (global)
  1. Mirror your org chart - Create departments that match your company structure
  2. Use hierarchy - Nest related departments under parent departments
  3. Set appropriate visibility - Match data access to job responsibilities
  4. Assign managers - Each department should have a clear manager
  5. Review regularly - Update as your team structure changes

See Also: