Inviting your team
Adding people to your organisation and giving them access to workspaces.
People are invited to a workspace, not to your account as a whole. Someone you invite becomes a member of that one workspace and sees nothing else.
If a colleague needs access to three workspaces, they get three invitations.
Sending an invitation
Invite by email address from the workspace you want them in. They receive an invitation link, and accepting it makes them a member.
They create their own login — you never share credentials or create an account on their behalf. The account belongs to them; removing their membership later doesn't delete it, it just removes their access to that workspace.
Invitations expire after 7 days
An invitation is valid for seven days. After that the link stops working and you'll need to send a new one.
You also can't send a second invitation to the same address for the same workspace while one is still pending — cancel or wait for the first, or resend after it expires.
If the person is already a member of that workspace, the invitation is rejected too.
What a member can do
Membership is straightforward: someone is a member of a workspace or they aren't. There are no per-member permission levels — a member of a workspace works in that workspace.
That's worth understanding before inviting, because a workspace holds more than automations. It holds connections, and anyone who can build automations there can use them — acting as your connected accounts, your store, your mailing list, your CRM. They never see the credentials, but they can act through them.
So the boundary that matters is which workspaces someone is in. For an agency, one workspace per client isn't only tidiness — it's what stops someone working on one account from reaching another.
Team access is a plan feature
Inviting people requires a plan that includes teams. Without it, the organisation owner is the only member, and attempting to invite returns a message saying your plan doesn't support invitations.
See Plans and actions.
Declining and removing
An invitation can be declined by the recipient, and a pending one can be removed before it's accepted.
To remove someone who has already joined, remove their membership from the workspace. Their account and any other workspace memberships are unaffected.
When someone leaves
Remove their membership from each workspace they were in.
Then check connections they authorised. An OAuth connection carries the permissions of whoever approved it, so if a departing colleague connected a tool using their own account at that provider, deactivating them there can break the connection and every automation using it. Reconnect those with an account that isn't tied to one person.
