Add team members

Sending an invite

1. Open the team panel. The Members nav item in Studio.
2. Enter the email. An address without an @ is refused: Enter a valid email address.
3. Pick a role. Anything unrecognised falls back to viewer. See Roles and permissions for what each one means.
4. Send. The invitation email reads You've been invited to <workspace> on Appsinity and points at the Studio sign-in.
5. Wait for activation. If the address already has a Studio account the member is active at once; otherwise it is pending until they register with that exact address.

How a member is identified

Membership is keyed on the email address, derived deterministically from the owner and that address. Two consequences:

One account per address. If the invitee registers a different address, the pending invite never activates and they see nothing.

Members belong to one owner. A person cannot be invited into two workspaces by the same address and expect both; the workspaces list is built from the owner's membership plus what they own.

• A pending invite is a record, not a claim on a mailbox — there is no re-send timer and no expiry.
• Inviting an address that later gets registered by somebody else gives that person your workspace.
• Set a display name at invite time; the member list shows it instead of a raw address.

Changing a member

A member can be updated: role, individual permission overrides, status, and display name. Changing the role re-applies that role's preset, and any permission you had manually overridden is rebuilt from the new preset.

• To grant a single extra right without changing the role, patch the permissions object directly — the record then reads as custom.
• Setting a status back to pending does not send another email; it just changes the record.
• Removing a member is immediate and irreversible in the sense that they must be re-invited.

Removing access

Deletion removes the membership row outright. There is no suspension state that keeps their history, and no audit trail of what they changed while they had access.

So the operational rule is: remove on the day someone leaves, and keep your own release notes, because Studio will not show you who edited a listing.