Consultant — accounts and client workspaces

This page is for users who joined through the consultant registration path (or who were later granted consultant capability by the platform). It complements the general team features described under Individuals and businesses.

1. Create your account

1. Open the application’s sign-up entry point and choose the consultant path when offered (wording may vary by deployment).
2. Complete email verification via the magic link (or follow the deployment’s password flow if magic link is unavailable).
3. Finish the onboarding wizard. The wizard should resume at the correct step after you return from email verification.

After completion, your user record is marked with the consultant capability. You still receive a standard personal workspace like any other user.

2. Create the first client workspace

During or immediately after consultant onboarding, you are prompted for minimum client workspace details (name, slug, and other required fields). Submitting the form creates a new team workspace for that client.

That workspace is recorded as consultant-managed because you created it. It appears in your consultant workspace list alongside any teams later assigned to you by a platform administrator.

3. Scoped access (what you can open)

You can list and open a client team only when at least one of the following is true:

• You created the team during onboarding or a later “create client workspace” flow.
• A platform administrator assigned that existing team to you.

If neither applies, the application must not reveal whether that team exists (no tenant enumeration). You will see a normal “access denied” or “not found” style experience.

4. Invite client users and set roles

Inside the client’s team workspace:

1. Go to Settings → Members (or Members in the team menu, depending on layout).
2. Invite client stakeholders by email and assign a role (for example owner for the paying administrator, member for staff).
3. Invited users accept via the invitation link and then appear in the member list.

Consultants often need a role that can configure workflows, forms, and public site content; the exact role names depend on how the deployment maps permissions. Sensitive account actions typically remain with the client owner unless your process says otherwise.

5. Platform administrator assignment

If you must operate a workspace you did not create, a global administrator uses an internal assignment action to link your consultant user to that account. Until that assignment exists, the workspace will not appear in your list.

Related routes (for orientation)

Replace [account] with the client team slug:

• Team home: /home/[account]
• Members: /home/[account]/members
• Settings: /home/[account]/settings

Next: Public site, data, and workflows for how to configure the product on behalf of the client.