Sub-Accounts

Sub-accounts group multiple Vouched accounts under a single parent for consolidated billing and unified management.

Sub-accounts let you organize verification activity across teams, environments, regions, or end customers without standing up multiple commercial relationships with Vouched. Each sub-account is a real, independent account with its own API keys, webhooks, and feature configuration but pricing and billing roll up to the parent on a single monthly invoice.

Sub-accounts are widely used by enterprises with regional or departmental segmentation and by partners who resell Vouched services to their own customers.

To enable sub-accounts on your account, please contact Support

Overview

Sub-accounts give you organizational separation where it matters (jobs, users, integrations, and configuration) while keeping the commercial side simple. Admins of the parent account can access and switch between linked sub-accounts from a single login, and analytics and reporting can be filtered to any individual sub-account or rolled up across the hierarchy.

Common use cases include:

• Regional or departmental separation: segregate verification activity by region, brand, business unit, or department.
• Resellers and platforms: partners who resell Vouched can create a sub-account per end customer they manage.

Account hierarchy

A parent account can have one or more sub-accounts linked to it. The hierarchy is two levels deep: a parent can have sub-accounts, but a sub-account cannot itself have sub-accounts. Each sub-account is linked to its parent, and consolidated billing flows up to the parent on a single monthly invoice.

Parent Account
├── Sub-Account A
├── Sub-Account B
└── Sub-Account C

What's shared and what's separate

Sub-accounts share the commercial setup with the parent but are otherwise independent:

Because each sub-account has its own API keys and webhook configuration, jobs submitted under a sub-account must use that sub-account's keys. Anywhere an API key is referenced (your JS plugin, server-side calls, the Find API, Crosscheck API, etc.) needs to use the correct sub-account's keys.

Users, roles, and switching accounts

Users and permissions are scoped per account, with a few rules that make hierarchies easy to manage:

• Admins of a parent account can access and switch into any of its sub-accounts directly from the dashboard. They inherit administrative rights over child accounts.
• Non-admin users of the parent do not automatically have access to sub-accounts. They must be granted access explicitly.
• A single user can hold different roles in different accounts: for example, admin in a staging sub-account and reviewer in production.
• Standard roles include Account Admin, Reviewer, Downloader, and Support, and can be assigned independently in each sub-account. Admin users switch between linked accounts using the Change Account dropdown on the account page. Sessions are preserved across switches, and on next login the user lands in the account they last used.

Sub-Accounts vs. Groups

Sub-accounts and Groups both organize verification activity, but they solve different problems. Groups are lightweight labels within a single account; sub-accounts are full child accounts with their own configuration and integration surface.

Rule of thumb: if you need different configurations, different webhooks, different API integrations, or different feature settings between segments of your business, use sub-accounts. If you only need to label and filter jobs or users within a single shared configuration, use Groups.

Migrating from Groups to Sub-Accounts

Groups can be converted to sub-accounts, but because a sub-account is a separate account, the migration involves a few customer-side actions. Plan for the following before migrating:

1. New API keys. The new sub-account starts with its own API keys. Designate someone on your team to log into the new sub-account and generate them, then update everywhere the old key was used — JS plugin code, the Find API, Crosscheck API, and any other integrations.
2. Historical jobs. Users in the new sub-account will not have access to jobs that were submitted under the original account. If you need ongoing access to historical job data, plan to keep at least one user in the original account, or export the data before cutover.
3. Initial users. Decide who should be granted access to the new sub-account at setup. Once those users are in, they can invite others.
4. Timing and coordination. Coordinate the cutover with your integration owners so API key updates happen alongside the migration to minimize disruption. Vouched support can assist with key generation, integration updates, and dashboard access during the transition.

FAQ

Can a single user belong to multiple sub-accounts? Each user is associated with one initial account, but admins of the parent account can access linked sub-accounts via the Change Account dropdown without needing to be reassigned. A non-admin user can also be granted explicit access to additional sub-accounts.

Can an admin switch between the parent and sub-accounts? Yes. Admins of the parent account see all linked sub-accounts in the Change Account dropdown and can switch between them. The session is preserved on refresh, and the account you last used is the one you'll land in on next login.

Can a sub-account have its own sub-account? No. Sub-accounts are limited to two levels — a parent and its direct children.

Do sub-accounts share API keys with the parent? No. Each sub-account has its own public and private API keys. Requests must use the keys for the specific sub-account that owns the job.

Do sub-accounts share webhook configuration with the parent? No. Each sub-account has its own webhook configuration so you can route events to different endpoints per environment, region, or end customer.

Can sub-accounts have different feature settings (e.g. liveness on/off)? Yes. Configuration and feature flags can be set independently per sub-account.

Will I get a separate invoice for each sub-account? No. Billing is consolidated at the parent — you receive a single monthly invoice covering all sub-accounts, and the parent's pricing tier applies across combined usage.

What if a child needs different pricing from the parent? A child that needs a different pricing structure should be set up as its own primary account rather than a sub-account, since separate pricing requires a separate subscription.

Can users be deleted? Users currently can't be deleted, but they can be disabled, which prevents them from logging in or performing actions.

How do I move a user between accounts? Moving a user between accounts is handled by the Vouched team. Open a support ticket with the user, the source account, and the destination account, and we'll make the change.

Getting started

To enroll in sub-accounts, please visit Support Our team will set up the parent–child relationship, provision the new sub-accounts, and walk through API key generation, webhook configuration, and user access.