Manage access across businesses

Access is granted one business at a time. To give someone access to a second business, invite them to it and give them a role there; their role in one business says nothing about another. People and agents then switch between their businesses, and the one they last selected is remembered.

Requirements

A role that can invite users and manage roles in each business you grant access to.

Steps

1. Invite the person to the other business. An invitation is per business; see Invite a user. A consultant already working in a client's business needs a separate invitation to the agency's own.
2. Give them a role there. Choose it for their job in that business, not the one they hold elsewhere. The same person can be an administrator in one business and have read-only access in another. See Create a custom role.
3. They switch between businesses. A person works in one business at a time and switches deliberately. Their selection is saved on their profile, so their next session opens in the business they used last.
4. Take access away per business. Removing someone's role in one business leaves the others untouched. See Change a user's role.

Agents across businesses

An agent connected as a person has that person's access in each business, and works in one business at a time. Because the selection persists, an agent can still be in the business chosen in an earlier session. Ask it which business is selected before it changes anything; see How an agent connects.

Notes and limitations

• Nothing crosses. Roles, collections, entries, automations, and reports stay inside one business. See Businesses and multi-tenancy.
• Every business keeps an administrator. The last administrator of a business cannot be removed from it.
• Whether to split at all is its own decision; see One business per client vs shared.

Related

For how roles and permissions work inside one business, see How access works.