Roles
Odin has four roles: Owner, Admin, Member, and Read only, each with a different level of access. See Roles & Permissions for a full breakdown of what each role can do.Owners cannot be edited or removed from within Odin, by anyone. To change or remove an Owner, contact [email protected].
Inviting members
1
Open the Team page
Go to Management > Team in the sidebar.
2
Click Add user
The Invite team members dialog opens.
3
Enter emails and choose a role
Type or paste up to 20 addresses, separated by commas, semicolons, spaces or new lines, then choose Send. Press Ctrl+Enter (⌘+Enter on Mac) to send from the address box. Repeated addresses are sent once. Odin lists any address that is invalid or already on the team, so you can fix them all before sending.Everyone in the batch gets the role you choose, which defaults to Member. To give people different roles, send a batch per role, or change a role later from the team table. The role list only offers roles below your own, so an Admin can invite Members and Read only users but not another Admin.
4
Confirm your identity
Inviting requires step-up verification, so you are asked to confirm who you are before the invitations go out.
5
Invitations sent
Each person receives an email telling them who invited them, to which organisation, and with what role, plus a link to the Odin sign-in page. They appear in the team table straight away with an Invited badge.
The dialog checks your seats before you send. If none are left, or you have entered more addresses than seats, it says so up front with a Manage seats link to buy seats in Billing and sends nothing until you remove addresses or buy seats. If a seat is taken by someone else between opening the dialog and sending, it stops at the first blocked address; invitations already sent in that batch still stand, and the unsent addresses stay in the dialog with the reason. Inviting someone who is already in the organisation is rejected rather than duplicated.
Requests to join
People who sign in with a verified address at your organisation’s domain can ask to join. So can people at the domain of the verified address your organisation was created with, even when it has no domain on file, unless it lists other domains only. Inviting someone never shows your organisation to their colleagues. Owners and Admins get an email and a notification, and the request appears in a Requests to join list above the team table. Nobody joins this way without your approval: only a verified domain lets people join automatically. Pick a role for each person (Member by default) and select Approve, or select Decline. Approving uses the same rules as an invitation: you can only grant roles below your own, it needs step-up verification, and it takes a seat. If no seats are left, the request stays in the list until you add seats. The person isn’t told who declined, and can’t ask again for 7 days. Requests that nobody answers expire after 14 days. To stop accepting requests, switch off Join requests in Organisation Settings.Searching and filtering
Above the team table you can:- Search by name or email
- Filter by role (Owner, Admin, Member, Read only)
Changing a role or name
Click a member’s row, or use the actions menu on the right and choose Edit, then change their role, first name, or last name. The row is only clickable for members you are allowed to manage. The rules the platform enforces:- Only Admins and Owners can edit anyone
- You can only edit someone whose role is below your own, so an Admin cannot edit another Admin
- You can only assign roles below your own
- You cannot change your own role
- Nobody can edit an Owner
- You can set a member’s name only until they first sign in. After that, only they can change it, from their profile
If your organisation uses directory sync with group role mapping, your identity provider decides roles. A role changed here for a directory-managed person is overwritten at the next sync, and someone removed here returns if they are still assigned in your identity provider.