Sub-accounts

Sub-accounts let a Faraday Enterprise account create and manage other accounts beneath it. Each sub-account is its own environment, with its own data, resources, and API key, so nothing crosses over between the clients or brands you manage.

Who uses sub-accounts

Partners and agencies that run Faraday for their own clients use sub-accounts to give each client an isolated environment. Companies with several brands or business units use them to keep each one's data apart, for example when a client's security requirements call for it.

What's shared and what isn't

The billing plan is inherited from the parent account. Data, like connections and datasets, is not shared between accounts. Resources, like cohorts, outcomes, and pipelines, are not shared either, so you create them in each sub-account. The parent account can see usage across itself and all of its sub-accounts.

Setting one up

Using your parent account's API key, create a sub-account with the create account endpoint. You'll get back an API key for the new sub-account, which you use to set up its connections, datasets, and everything else. You can also create and manage sub-accounts through the MCP server. For the full step-by-step setup, see Accounts > Sub-accounts.

Sub-accounts are available on Faraday Enterprise.