Child Companies (Sub-Accounts) for multi-entity orgs

Run multiple subsidiary entities under one CVViZ workspace via the Sub-Accounts feature.

What it is

Child Companies in CVViZ — internally called Sub-Accounts — let you run multiple subsidiaries or divisions under one parent workspace. Each child company has its own users, jobs, settings (working hours, currency), and location.

Description from the in-app card: "Child companies are subsidiaries or divisions of your main company. They can have their own users and job postings. Child companies allow for decentralized management while maintaining oversight from the parent company."

Where to manage

Settings → Child Companies.

Activating the feature

Child Companies is gated by a workspace-level toggle: Active / Inactive at the top of the page. The toggle stores its state in thelocalStorage flag.

  • Buttons: Activate / Deactivate.
  • Until you activate, the feature is dormant; jobs and users live in the parent workspace only.

Adding a sub-account

  1. Click + New Sub-Account.
  2. Fill in:
    • company_name (required).
    • address, city, state, employer_country, zip.
    • currency_code.
    • working_day_start and working_day_end (e.g. Monday → Friday).
    • work_hrs_start_time and work_hrs_end_time (24-hour TimePicker).
  3. Save.

The sub-accounts list

Columns:

  • Company Name
  • City
  • State
  • Country

What sub-accounts enable

  • Each child can have its own users and jobs.
  • Per-child currency for salary fields and reporting.
  • Per-child working hours used by automations and scheduling.
  • Departments can be scoped to a specific child company (see Departments).

How users see sub-accounts

When sub-accounts are active, the Users list shows a Company column indicating which child a user belongs to. Departments can be scoped per child company. Filtering jobs and candidates by child company is supported in the relevant lists.

Common patterns

  • Holdco + portfolio companies — strict data isolation between sub-accounts.
  • Parent + regional offices — different working hours / currencies per region.
  • Agency with multiple practice areas — separate sub-accounts for tech / healthcare / finance practices.

Pitfalls

  • Don't use sub-accounts as a substitute for departments. Sub-accounts mean separate operations; departments mean groupings within one operation.
  • Migrating between sub-accounts after the fact is disruptive — plan the structure up front.
  • Cross-child reporting only makes sense if leadership genuinely oversees both sides; otherwise, separate workspaces may be cleaner.

Tips

  • Activate first, add sub-accounts second — the toggle gates everything else.
  • Keep child company names distinct enough to avoid filter confusion.
  • Coordinate currency and working hours with the parent's defaults if you want sane reports.