how it works
chaos trace supports parent-child company structures. a parent account (your firm) can create and manage child accounts (portfolio companies or clients), each with fully isolated data, connections, and team members.
setting up a child company
- go to Settings → Company → Managed Companies
- click Add Company
- enter the child company's name and domain (e.g., "Acme Corp", acme.com)
- chaos trace creates a separate account, linked under your parent account
- you're now the owner of both and can switch between them using the tenant switcher
connecting systems for a child company
switch to the child company using the tenant switcher, then go to Systems (or the onboarding page) and connect salesforce, hubspot, or marketo using the child company's credentials.
data syncs to the child company's account — completely isolated from the parent. systems are connected to the account, not to you personally. anyone on the child company's team sees the same data without needing to reconnect.
adding people at the child company
- switch to the child company's account
- go to Settings → Team and invite the child company's ops lead as admin
- they receive an invite, set their password, and log in
- they see the child company's dashboard with all data already connected
- they can invite their own team (editors, viewers) without involving you
splitting a child company out
when a child company is ready to manage their own chaos trace account independently:
- go to the child company's settings
- use the split function and enter the email of the person who will own the account
- chaos trace transfers ownership and unlinks the child from your parent account
what the child keeps
everything — connections, data, team members, history. nothing breaks.
what you lose
access to the child company's account. you can no longer see their data or manage their team.
multi-tenant users
if you're a member of more than one account (common for consultants and PE ops leads):
- →the tenant switcher shows all accounts you belong to
- →your active account persists across page loads
- →each account is fully isolated — different connections, different data, different team
- →your role can differ per account (e.g., admin on one, viewer on another)