Team
Inviting members
How to invite people to your Expanse team, what happens when they accept, and how to remove access safely.
Inviting members
Invites are the safe way to add someone to your team. They get an email, accept with their own Expanse user (or create one in the same flow, depending on what we use at the time), and then appear in the member list with the role you selected.
How to send an invite (typical flow)
- Open Team (or Members) in the panel for the right team in the team switcher.
- Find Invite (wording can vary) and enter the person’s email you want to add.
- Choose a role — if you are not sure, start with Member; promote later if you need. See Team roles for the differences.
- Send the invite. The recipient should get mail from a domain you trust. If they see nothing, ask them to check spam and that the address is typed correctly.
- When they accept, they show up in the list. You can then adjust their role if your own permissions allow it.
Good practices
- Least privilege — give the lowest role that still lets them do the job. You can add power later; taking back a mistake can be messier.
- One person, one sign-in — do not “share the owner’s login.” Two separate users with the right roles are easier to audit and remove.
- Off-board people when they leave the community or company. Removing access is part of good security, not a personal insult.
Resending and expiry
- If an invite is out of date or the link was lost, send a new invite. Old links are not a safe thing to “forward forever.”
- If the product shows status (pending, accepted, expired), use that to see whether you are waiting on them or the wrong mailbox was used.
Removing someone
- In the same Team list, use Remove (or the equivalent) on that member, if the panel allows and your role is high enough.
- If you are not sure whether they still have API keys or other access outside the panel, rotate credentials for your services the same way you would when a volunteer leaves. The panel can remove team membership; you still need good habits on the game and VPS side. See Good security habits.
Owners cannot always remove the last owner; that is protection against the whole org becoming orphaned.
Trouble
| Symptom | What to check |
|---|---|
| “Already on the team” | They need to use the other email or you need to change their role, not re-invite. |
| “No permission to invite” | Your Team roles do not allow it; ask an owner. |
| Weird email / phishing | Real mail matches official domains and only asks you to sign in in the real panel, never to “confirm your password” in a reply. |
Related
- What is a team?
- Support and contact if the product will not add the member and you have checked all of the above
