Departments setup

Manage your team's departments — a CRUD list with name, description, default flag, and multi-company support.

What departments do

Departments in CVViZ group jobs (Engineering, Sales, Marketing, etc.). Practically, a department appears:

  • On the Add Job form's Details tab as a select.
  • On the careers page (jobs can be grouped by department).
  • As a filter in jobs lists and reports.

Where to manage

Settings → Departments. Permission required:.

Page header: Departments with subtitle "Organize your team structure with departments".

The Departments table

  • Department — the department name.
  • Company — only shown if your workspace has child companies (sub-accounts) active. Marked with a partition icon when the department belongs to a child company.
  • Description — rich-text description (rendered as HTML).
  • Default — checkmark if is_default = 1; one department can be default and is auto-suggested on new jobs.
  • Actions — Edit and Delete.

Creating a department

  1. Click + Add Department in the top-right.
  2. Fill in the name and (optionally) the description.
  3. For multi-company setups, pick which child company the department belongs to.
  4. Optionally mark as default.
  5. Save.

Editing or deleting

From any row's Actions, click Edit to update or Delete to remove. Removing a department can affect existing jobs that reference it — be careful with deletions on departments in active use.

Multi-company / sub-account support

If your workspace has child companies active (set up at Settings → Child Companies), each department can belong to a specific child company. The Company column appears on the table to disambiguate.

Best practices

  • Keep the list flat and short. 5–15 departments covers most orgs.
  • Match your org chart at a high level. Don't model every team — group small teams under a parent (e.g. "Engineering" rather than "Backend / Frontend / DevOps").
  • Set a default. The most-common department for new jobs makes job creation faster.
  • Don't model locations or seniority as departments — those are separate fields on the job.

What's not in the page

  • No department leads field.
  • No hierarchical (parent / child) departments.
  • No per-department routing rules (e.g. "all candidates for this dept go to recruiter X").
  • No bulk merge across departments.

Tips

  • Audit yearly — merge or rename as your org evolves.
  • If you have many small departments, ask whether one parent label would serve reporting better.
  • Use the description field to capture the department's mission for new joiners.