Manage organisation membership
Create and select an organisation, invite colleagues with role-based access and manage shared customer records in context.
- Select workspaceCreate or select the organisation to manage.
- Invite colleagueEnter their account email and suitable role.
- Accept invitationInvitee signs in with matching email within seven days.
- Maintain accessAuthorised managers can change roles or remove members.
- Check contextContext and role govern shared resource visibility.
Create and select
Organisations lists memberships, owners, members and open invitations. Create a workspace with a name of at least two characters and optional billing email. The creator becomes owner and member, and the new organisation is selected. Selecting a different context changes shared resources shown; it does not merge personal records.
- Create the workspace with its intended name and billing email.
- Select the organisation to manage from the list.
- Confirm context before opening shared resources.
Choose member roles
Owners and administrators have broad organisation access and can manage members, keys and webhooks. Billing members can view billing and orders. Members can view support, orders, keys and webhooks but cannot manage them. The owner cannot be changed or removed through these controls. Give each colleague only the authority needed for their work.
- Choose admin only for broad management duties.
- Choose billing for billing and order visibility.
- Use member for ordinary access without management rights.
Invite a colleague
A member manager enters an email and selects admin, billing or member. Existing members cannot be invited again. The invitation expires after seven days and its link contains a private token. The recipient must sign in with the invited email and accept through that link. Do not forward it to another person.
- Enter the colleague email and least-privilege role.
- Send the returned invitation link privately to them.
- Ask them to accept signed in with matching email.
Change or remove membership
An authorised manager can change a non-owner member among supported roles or remove that membership. Changes are recorded. Removing membership does not delete the person's account. Consider ownership of personal resources and continuity before removal. The owner row is locked, so arrange owner-level changes through the supported organisation process.
- Check member identity and work dependencies first.
- Save a supported role change or remove membership.
- Verify the member list reflects the new access.
Use shared records
Organisation context and role affect visibility of orders, billing, API keys and webhooks. Owners and administrators manage keys and endpoints; billing users view billing and orders. Members can view keys and webhooks but cannot manage them. A missing record can be caused by selecting the wrong organisation or lacking its required permission.
- Select the organisation before searching shared records.
- Check your role for the requested action.
- Ask an owner or administrator to make restricted changes.
Resolve invite and access issues
An expired, invalid or already-used link, mismatched signed-in email or removed membership can block entry. An authorised manager can verify an open invitation and issue another. If shared data disappears, check selected context and role. Never share passwords or use another member's account to diagnose access.
- Sign in with the exact email that was invited.
- Ask a manager to verify or replace the invitation.
- Request only the role needed for your task.
Frequently asked questions
How long does an invite last?
Seven days; a manager can issue another.
Can any user accept it?
No. Account email and invitation token must match.
Can I remove the owner?
No. Owner membership is locked in these controls.
Can billing rotate keys?
No. Key management requires owner or admin.
Does removal delete an account?
No. It removes organisation membership only.
Why are records missing?
Check selected organisation and role permissions.