Departments and how they affect routing

Organize your team structure with departments — a CRUD list used to group jobs and candidates.

What a department does

A department in CVViZ is a way to organize your jobs into logical groups (Engineering, Sales, Marketing, etc.). The Departments page is described as "Organize your team structure with departments".

Practically, a department appears:

  • As a select on the job creation form's Details tab.
  • On careers page job listings (jobs can be grouped by department).
  • As a filter in jobs lists and reports.

Where to manage

Settings → Departments. Permission required:.

The Departments table

Columns visible on the page:

  • Department — the department name.
  • Company — only shown if your workspace has multiple companies (sub-accounts). Marked with a partition icon when the department belongs to a child company.
  • Description — rich-text description (rendered as HTML).
  • Default — a check mark when the department is set as the default (is_default = 1). One department can be the 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 (set up at Settings → Child Companies), each department can belong to a specific child company. The Departments table shows the company column 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 this page (yet)

To keep the article accurate, the current Departments page is a CRUD list with name, description, default flag, and multi-company scoping. It doesn't include department leads, hierarchical (parent/child) departments, or per-department routing rules.