Inviting people
Sending an invite#
Team → Invite, then:
- Email address.
- Role — see Roles and permissions.
- Server scope, optionally — restrict them to specific servers rather than all of them.
They get an email with a link. Accepting it puts them in your organisation with the role you chose.
Invites expire#
An invite link is a way into your infrastructure, so it does not stay valid forever. If someone's link has expired, send a new invite rather than looking for a way to extend the old one.
You cannot invite above your own role#
The role you offer in an invite is capped at what you hold yourself. A DevOps user cannot invite an Owner. This is the same rule that applies to promoting an existing member, enforced in both places.
Removing someone#
Remove them from the team list. Their access ends immediately.
What they did stays in the audit log — removing a person does not remove the record of their actions, which is the point of having one.
Removing them from CloudPilot ends their panel access. It does not rotate anything they knew independently: SSH keys they added to a server, database passwords they were told, or API tokens they created elsewhere. Handle those separately.
Multiple organisations#
An account can belong to more than one organisation and switch between them. Permissions are per organisation — being an Owner in one says nothing about the other.
Raise a ticket and someone will pick it up. Sign in with the same account you use for the panel.
Raise a ticket