Invite your team and set roles

Your agency staff and your clients are two separate groups in TaskJuice. Staff hold an account role (Owner, Admin, or Member) and work across the whole account. Clients are invited into a single workspace and stay there. This page covers inviting staff, understanding what each role can do across workspaces, and handing the Owner role to someone else.

When to use this

Use these steps when you want to:

• Add a colleague to your agency so they can build and run workflows for clients.
• Decide whether someone should be an Admin or a Member.
• Understand why teammates can already see every client workspace.
• Move the single Owner role to another person (for example, when a founder leaves).

To add a client to one workspace instead of your staff, see Account and workspaces. To configure who can edit your branding, see Branding.

Account roles at a glance

Every staff member holds one account role. The role decides what they can do across the entire account.

There is exactly one Owner per account. An Admin can do everything an Admin-tier surface allows, but cannot touch billing, transfer ownership, or delete the account. A Member can build workflows and connections and view everything, but cannot invite anyone, manage workspaces, or change branding.

Invite a teammate

Teammates are agency staff. Inviting one grants an account role and, through that role, access to every client workspace under your account.

1. Open Members & roles

   Go to Settings → Members & roles (the /settings/members route; the older /team link redirects there). Only Owners and Admins can open this page and see the Invite teammate button.

2. Open the invite dialog and enter an email

   Select Invite teammate. In the dialog titled "Invite teammate," enter the person's email address, for example colleague@agency.com.

3. Choose a role

   Pick Admin or Member. Member is selected by default. Owner is not an option here, because ownership only moves through a transfer (covered below). The dialog help text states: "Admins can invite teammates and clients. Members can build but not invite."

4. Send the invitation

   Select Send invitation. You see the toast "Invite sent to {email}," and the invite appears in the members table with status Pending.

The invited person receives an email. When they sign in and accept, they gain the account role you chose and immediately have Admin-level access to every workspace in your account.

What clients are, and where you invite them

Clients are your external end customers, not staff. You invite a client from a specific workspace's Clients page, not from Members & roles, and the only role they can receive is Client. A Client can view the workspace, trigger manual runs, and rotate their own connected-app credentials, but cannot edit workflows, change settings, or invite anyone. See Account and workspaces for the per-workspace invite flow.

A person can be either staff or a client on a given account, never both. If you try to add someone as a client who already holds an account role on that account, TaskJuice rejects it.

Manage pending invitations

Members & roles lists teammates and pending invitations in one table, with pending invitations at the top. Open the actions menu on an invitation's row to manage it:

• Resend invitation issues a fresh invitation. The previous pending invite is revoked and a new one is created with a new 7-day expiry. Only the new invite emails. You see the toast "Invitation resent."
• Revoke invitation cancels a pending invite. It leaves the table and its link stops working. You see the toast "Invitation revoked."

The table shows invitations that are still open: Pending, or Expired once the 7-day window has passed without an answer. An accepted invitation becomes the teammate's own row, marked Active; revoked and declined invitations drop out of the list.

Change a teammate's role

Owners and Admins can move any other teammate between Admin and Member from Settings → Members & roles. Open the Role menu on the teammate's row and choose the new role. You see the toast "{name} is now an admin" or "{name} is now a member," and the teammate's access updates within a few seconds.

You cannot change your own role, and nobody can change the Owner's role here. Ownership moves only through Transfer ownership. An Admin can change another Admin's role.

Remove a teammate

Owners and Admins can remove any other teammate except the Owner. On Settings → Members & roles, open the actions menu on the teammate's row and select Remove from account.

A confirmation opens before anything changes. It tells you how many active API keys the teammate created on this account (or, if that count isn't available, that any keys they created will be revoked). Removing them also revokes those keys, so any integration that uses one stops working. A key belongs to the person who created it, whatever their role, so an integration that must outlive a teammate should run on a key created by someone who is staying, such as the Owner. Select Remove to confirm, or Cancel to keep them.

Removing a teammate drops only this account's role from their user record. Accounts they belong to elsewhere, and API keys they created on other accounts, are untouched. They lose access to this account right away, and they get an email saying they were removed. If they have a timer running on this account, it stops at that moment and the time so far is kept; a timer they run on another account keeps running. You see the toast "{name} removed," followed by the number of API keys that were revoked and whether a running timer was stopped, if any.

Cross-workspace visibility

Visibility follows directly from the two role layers:

• Staff (Owner, Admin, Member) see and act on every workspace in the account. There is no way to limit a teammate to a subset of workspaces, and no UI to assign a teammate as Client on one workspace. Account-role access composes to workspace Admin everywhere.
• Clients see only the workspace they were invited into. They reach it through the client portal and never see the agency dashboard or a workspace picker.

If you need a person to have access to some client workspaces but not others, an account role is too broad for that. Account roles grant all-or-nothing access across every workspace in the account.

Transfer ownership

Ownership is a single role, and it moves only through a deliberate transfer. There is no "invite an owner" path.

1. Promote the target to Admin first

   The new owner must already be an Admin on this account. You cannot transfer to a Member or to someone outside the account. If they are a Member, change their role to Admin before continuing.

2. Start the transfer from Members & roles

   As the current Owner, open Settings → Members & roles and choose Transfer ownership in the actions menu on the target teammate's row. The transfer action is visible only to the Owner.

3. Confirm

   In the confirmation dialog, read the copy: "{name} becomes the account owner. You become an admin and can't undo this. Only the new owner can transfer it back. Billing access moves to the new owner." Select Transfer ownership to confirm.

The swap is atomic: you are demoted to Admin and the target is promoted to Owner in one step, so the account always has exactly one Owner. You see the toast "Ownership transferred," and your session refreshes so the change takes effect right away. Billing access moves to the new owner with the role.

For a deeper walk-through of the ownership rules, see Transfer account ownership.

Verify it worked

• After inviting a teammate, the members table shows the new email with status Pending. Once they accept, their row shows Active.
• A new teammate can open any client workspace from the account dashboard without a separate invite, confirming cross-workspace access.
• After a transfer, your role on Members & roles reads Admin and the new owner reads Owner. Only one row shows Owner.

Troubleshooting

Related

• Account and workspaces: one workspace per client, and how isolation works.
• Roles and permissions: the full capability matrix for every role.
• Transfer account ownership: the ownership rules in detail.