Invitations and access
See where invitations to your email address appear, accept one, and know which actions each role can take.
Two questions bring people here: how do I bring a colleague in, and someone sent me an invitation, now what. The honest answer to the first one is short, so it goes first.
Adding people is not available yet
Every account today is a one-person organisation. There is no members screen, the account menu has no organisation section, and attempts to add a second person are refused with this message:
This organisation is on an individual plan, so it can only have one member. Adding a second person needs a Team plan, which is not available yet.
That refusal is enforced in more than one place, so there is no workaround worth hunting for. Everything below is about invitations that come to you.
Where an invitation appears
Invitations show up in one place: Personal settings, then Invitations in the settings sidebar. That item is always there, even with nothing waiting.
You also get a nudge in the workspace dropdown at the top of the sidebar. When something is pending, an extra row reads 1 invitation waiting, or names the number when there is more than one, and links to the same screen. The row is absent when the count is zero.
An invitation row names the organisation, the role you would have and the expiry date, in the shape "Member · expires 12 Mar 2026", with a Join button.
Invitations are addressed to an email address, not to you as a person. If you were invited at your work address but signed in with a personal one, this screen will be empty. It is empty on purpose in a way you can diagnose: the message reads "No invitations are waiting for" followed by the exact address it searched, so you can see the mismatch and sign in with the invited address instead.
Accepting one
Press Join on the row. The button reads Joining… while it works, every other Join button on the screen is disabled until it settles, and a toast names the organisation you joined.
Joining adds access. It never replaces or removes what you already have, which is what the screen means by "Joining one gives you access to every workspace in it, alongside the workspaces you already have." After joining, those workspaces appear in the workspace dropdown and you can switch between them.
If joining fails the toast names the reason. On today's product it is the individual-plan refusal quoted above, because that limit is checked when you join and not only when someone invites you. The row stays where it is.
Two others are possible if the invitation changed under you between opening the screen and pressing Join: Invalid or expired invite, when an admin revoked it or it was already used, and Invite has expired. Both need a new invitation, and the row leaves the list once the screen reloads.
Opening an invitation link
An invitation email carries a link. What you see when you open it depends on the state of the invitation and on who you are signed in as.
- Signed in as the invited address, with the invitation still valid: an Accept invitation button.
- Signed out: sign-in first, with Continue with Google as the main path and Use email instead below it. The invitation is accepted for you once you are signed in.
- Signed in as a different address: Wrong account, naming both the invited address and yours, with no button. Sign out and sign in with the invited address.
- More than seven days after it was created: Invitation expired. Links last seven days.
- Withdrawn by an admin before you used it: Invitation revoked.
- Already used: Already accepted. If you are signed in you are sent straight into the app instead.
- Unknown or mistyped: Invite not found, with the line "This invitation link is invalid."
The expired and revoked screens both end with the same advice, which is to ask an admin to send a new one. Your email address also has to be confirmed before it can join anything.
Who can do what
An organisation has three roles: owner, admin and member. In your own organisation you are the owner, so none of this restricts you. It applies once you have joined someone else's.
| Action | Owner | Admin | Member |
|---|---|---|---|
| Create, rename and delete projects | Yes | Yes | No |
| Rename the workspace | Yes | Yes | No |
| Write documents, run checks and simulations | Yes | Yes | Yes |
As a member, the workspace Name field and its save button are disabled. A blocked project action reports either You don't have permission to do that. or That doesn't exist or you can't access it. The second wording is deliberately vague, because saying which of the two it is would confirm that a project you cannot see exists.