Skip to main content
Team, Roles & Permissions

Set up child companies for subsidiaries and divisions

Use Child Companies to organize subsidiaries or divisions under a parent CVViZ workspace. A child company can have its own users, jobs, location, currency, and working-hours s

Use Child Companies to organize subsidiaries or divisions under a parent CVViZ workspace. A child company can have its own users, jobs, location, currency, and working-hours settings.

Before you start

An administrator must manage Child Companies on an eligible parent account. Open Settings → Team & Access → Child Companies. If unavailable, ask the parent workspace administrator to check access and the account’s allowance.

Enable and add a child company

  1. Review Child company access and enable it if your account permits the change.

  2. Choose Add child company.

  3. Enter the Child Company Name and the address or location details needed for that operation.

  4. Set the currency, working days, and working hours offered by the form.

  5. Save and confirm that the company appears in the list.

Use distinct names so that users can select the correct company when assigning records. Review the company association when adding users, departments, or jobs.

Manage existing companies

Use Edit child company to update the saved details. Review the list’s location information and refresh if a change has not appeared.

Before deleting a child company or disabling access, review its users and work. Ask support about unclear consequences; deletion does not move work between companies.

Choose the right structure

Use a child company for a subsidiary or division that needs its own operational setup. Use a department to group jobs within an operation.

Roles and record permissions still control access. A child company does not automatically hide all records and reports from the parent workspace. Ask an administrator to check the required access for each role.

If a change fails

Read the error shown and keep your form open while correcting it. Check administrator access, feature availability, the parent workspace context, and the company name. Contact support with the action and message if it remains blocked.

Related articles

Was this helpful?

Still need help? Ask the team