Members

You can invite other team members via email. Navigate to the team member settings by clicking on “Team” in the left sidebar, or select “Team Settings” in the team dropdown menu inside the main navbar on top.

From there, click on “Add Collaborator” and enter the email address of the user you want to invite. Pick the permissions the new member should have and click on “Send Invitation”.

If the invitee does not have a Sliplane account yet, they will be asked to create one. Otherwise, they will get an invite email with a link to join your team. The email that you invited needs to match the primary Github email address of the invitee.

Permissions

Every team has exactly one owner and any number of additional members. Members are granted individual permissions rather than a fixed role, so you can hand out exactly the access someone needs. Permissions are additive: a member with none can still read every resource in the team, and each permission you grant unlocks a specific set of actions on top of that.

You can set permissions when inviting a collaborator and change them later from the member’s menu via “Edit Permissions”.

Permission	What it allows
Manage resources	Create, update and delete servers, services, projects, databases and buckets
Manage collaborators	Invite and remove members, and edit their permissions
Billing	View invoices and billing history, and download invoice PDFs

The owner

Each team has exactly one owner. The owner implicitly holds every permission and is the only member who can:

• change team settings (like the team name)
• access the compliance page and sign the DPA
• transfer ownership of the team
• delete the team

The owner cannot have their permissions edited or be removed like a regular member. To change who owns a team, use an ownership transfer.

The owner is responsible for billing

The owner is the billing owner of the team and is responsible for paying its invoices. This applies to every team you own, so if you own multiple teams you carry the billing responsibility for all of them.

If invoices go unpaid, the team is restricted: after repeated failed payment attempts its services are suspended and its API keys are revoked until the outstanding balance is settled. Because you are the billing owner for every team you own, unpaid invoices are not contained to the team that owes them. As long as a balance stays outstanding, your other teams are also at risk of being restricted, so settle any unpaid invoice promptly. Because the owner carries this responsibility, a team must always have exactly one owner.

Transferring ownership

Ownership is handed over through a transfer that the recipient has to accept, so ownership never changes without both people agreeing to it.

To start a transfer, open the “Unsafe Territory” page in your team settings, pick the collaborator you want to hand the team to, and click “Transfer ownership”. You will be asked to confirm by typing the team name. Only the current owner can start a transfer, the recipient has to be another active member, and there can only be one transfer pending at a time.

A transfer is blocked while the team has open (unpaid) invoices. Settle any outstanding invoices first, otherwise the transfer cannot be started or accepted.

A pending transfer expires 24 hours after you start it. If the recipient does not accept within that window the offer lapses on its own, ownership stays with you, and you can simply start a new transfer if you still want to hand the team over.

Once started, the recipient sees a banner prompting them to accept or decline the transfer, along with how long they have left to accept. Ownership stays with you until they accept, and you can cancel the pending transfer at any point before that. When the recipient accepts:

• they become the sole owner and take over billing responsibility for the team
• you stay on the team as a full-permission member

Accepting is not just a permission change. The new owner becomes the billing owner of the team: they are responsible for paying its invoices, and if invoices go unpaid the billing owners services can be suspended and its API keys revoked (see The owner is responsible for billing above). Make sure the recipient understands this before they accept.

You cannot undo a transfer yourself after it is accepted, so the new owner would have to transfer it back.

Personal teams (your default team) cannot have their ownership transferred.