Set up one workspace per client

Goal

Set up your agency account so that every client lives in its own workspace. Each workspace holds that client's workflows, connections, and run history, and nothing in one workspace is visible from another. By the end you will have your account, one or more client workspaces, and a clear picture of what each workspace keeps separate.

The model: account, then a workspace per client

Your agency is a single account. You create it once through the setup wizard, and the person who creates it becomes the Owner. Everyone you hire onto your agency, whether you label them Owner, Admin, or Member, holds an account role on that one account.

A workspace is one client engagement. You create one workspace per client. A workspace belongs to exactly one account and holds all of that client's work: workflows, connections, invitations, dashboards, and run history.

Two populations live on an account, and they never mix:

• Teammates are your agency staff. They hold an account role (Owner, Admin, or Member) and automatically have full access to every workspace on the account. There is no per-workspace invite step for staff.
• Clients are your customers. A client is invited into a single workspace and can see only that workspace through the client portal. Clients are read-only: they can view execution history, trigger a manual run, and rotate their own connected-app credentials, but they cannot edit workflows or change settings.

A single person cannot be both a teammate and a client on the same account. That rule is enforced, not just a convention. See Isolation: what each workspace keeps separate.

When to use this

Follow this page when you are onboarding a new client and want their automations to stand apart from every other client you manage. The one-workspace-per-client pattern is the default agency setup: it keeps run history, connected credentials, and billing contacts scoped to a single client, and it lets you hand that client read-only portal access without exposing anyone else's work.

If you only need to invite staff or change who can do what, see Invite teammates and assign roles instead.

Before you start

You need an account. If you have not created one yet, run the setup wizard at Create your account. The wizard creates the account and your first workspace in one step, and assigns you the Owner role.

To create more workspaces, you must be an Owner or Admin. Members can build inside existing workspaces but cannot create new ones.

Your plan sets how many workspaces you can have:

The limit is checked when you create a workspace. If you are on Starter, your one workspace is the one the wizard already made, so plan to upgrade before onboarding a second client.

Create a workspace for a client

1. Open the Clients page

   Go to /clients. This page lists every workspace on your account, one row per client engagement, with columns for name, slug, client count, workflow count, and last activity.

2. Start a new workspace

   Select New workspace. The Create a workspace dialog opens.

3. Name the workspace and set its URL slug

   Enter a Workspace name between 1 and 100 characters, for example Acme Inc.. This name appears in workspace navigation and on the invitations you send.

   The URL slug auto-fills from the name. It must be 2 to 50 characters and use only lowercase letters, numbers, and hyphens (acme-inc). A live check shows Available or This slug is already taken as you type. The slug becomes part of the workspace URL, so pick something the client will recognize.

4. Create it

   Select Create workspace. On success you see a Workspace created confirmation and land on the new workspace's dashboard, ready to build.

Slugs are unique only within your account, not across all of TaskJuice. Two different agencies can both have a workspace named dashboard. You cannot have two workspaces with the same slug on your own account.

Invite the client into their workspace

Staff already have access to every workspace, so there is nothing to do for your own team. To give the client access, invite them into this one workspace from its Clients page at /{workspaceSlug}/workspace/members.

The invite has no role picker: every workspace invitation grants the Client role, which is read-only plus the ability to trigger runs and rotate the client's own credentials. Invitations expire after 7 days. For the full invite walkthrough, including resend and revoke, see Invite teammates and assign roles.

Workspace defaults you can tune

A new workspace ships with sensible defaults. Two are worth knowing because they change behavior for that client:

To rename a workspace later, open /{workspaceSlug}/settings/workspace. Only the name is editable there; the slug is fixed after creation. Deleting a workspace also lives on that page and requires you to type the workspace name to confirm. Both actions require Owner or Admin.

Isolation: what each workspace keeps separate

The one-workspace-per-client setup is worth doing because the boundary between workspaces is enforced by the platform, not left to careful naming.

• All client data is scoped to the workspace. Workflows, connections, invitations, dashboards, and run history belong to a single workspace. When you delete a workspace, that data is removed with it.
• Clients see only their own workspace. A client signs in to the client portal and sees that one workspace, branded as your agency. They cannot reach the agency dashboard or any other client's workspace. The portal sends a client with no workspace membership back to their home screen rather than showing a picker.
• Staff and clients are mutually exclusive on an account. A person who holds any account role cannot also be added as a client on a workspace under that same account, and a workspace client cannot be given an account role. If you try to add an account teammate to a workspace's client list, the action is rejected.

This last rule is what keeps a client from accidentally gaining staff access. It holds even under concurrent edits, so two people changing roles at the same time cannot slip a user into both populations.

Verify it worked

After creating a workspace, confirm the setup:

• The new workspace appears as a row on /clients with its name and slug.
• Opening the row takes you to that workspace's dashboard at /{workspaceSlug}/dashboard.
• The invited client receives an invitation email and, after accepting, can sign in to the portal and see this workspace only.

Troubleshooting

You cannot create another workspace. You have reached your plan's workspace limit. Starter allows 1, Growth allows 5, and Scale allows 25. Upgrade your plan to add more, or remove a workspace you no longer need. If your plan has not resolved yet, the limit falls back to the most restrictive tier (1 workspace).

The slug shows "This slug is already taken." Another workspace on your account already uses that slug. Slugs must be unique within your account. Choose a different one. The slug also must be 2 to 50 characters using only lowercase letters, numbers, and hyphens, with no leading or trailing hyphen.

Adding a teammate as a client is rejected. A user who holds an account role on your agency cannot be added to a workspace's client list, because staff and clients are mutually exclusive on the same account. If that person needs read-only client access for testing, invite a separate email address that is not on your staff.

You do not see the New workspace button, or creating one fails with a permission error. Creating workspaces requires the Owner or Admin role. Members can build inside existing workspaces but cannot create new ones. Ask an Owner or Admin to create the workspace, or have them promote you.

Related

• Invite teammates and assign roles
• Brand your account and client portal
• Create your account