Teams & Organizations
Inviting teammates, roles and permissions, switching between organizations, and seats.
Every Project you create lives inside an Organization. You get a personal one automatically when you sign up; this page covers inviting people into it (or into another one you belong to).
Roles
Each member of an Organization has one role, which decides what they can do. There are four built-in roles:
| Role | Can do |
|---|---|
| Owner | Everything: projects, servers, secrets, billing, members, custom roles, seats and organization settings. The owner pays from their wallet, and their role can't be changed or removed. |
| Admin | Everything a Developer can, plus view billing, invite members, change members' roles and remove members. Can't top up the wallet, manage custom roles or add seats. |
| Developer | Create, deploy, change and delete projects, apps and databases; register and manage servers (clusters); create and change secrets. The day-to-day working role. |
| Viewer | Read-only: projects, apps, databases, logs, metrics, servers, secret names (never their values) and the member list. |
Custom roles
When none of the built-in roles fits — say, someone who should deploy apps but never touch servers or secrets — create a custom role: give it a name and pick its permissions from the list below. Then assign it like any other role, when inviting someone or by changing an existing member's role.
| Area | Permissions |
|---|---|
| Projects | View projects, apps, databases, logs and metrics · Create, deploy, change and delete them |
| Clusters | View servers and nodes · Register, change and decommission them |
| Secrets | View secrets (never their values) · Create, change and delete them |
| Billing | View the wallet, transactions, payments and subscriptions · Top up, pay, redeem vouchers and manage subscriptions |
| Members | View members and roles · Invite members and manage pending invites · Change members' roles and remove members |
| Access control | Create, change and delete custom roles |
| Organization | Manage seats and organization settings |
Each "change" permission includes its "view" permission. Some rules keep this safe:
- You can't hand out more than you have. A role you create or assign can only contain permissions you hold yourself, and you can't change or remove a member who holds permissions you don't.
- Nobody changes their own role, and nobody can change or remove the Owner.
- A role in use can't be deleted. Move its members (and any pending invites) to another role first.
By default only the Owner can manage custom roles.
Inviting a teammate
From your Organization's Members page, invite someone by email and choose their role — a built-in one or a custom role. This needs permission to invite members (Owner and Admin have it by default).
The invitee receives an email with an accept link. The link itself is only in that email; it's never shown in the dashboard. They accept it while logged into a Raklane account using that same email address.
An invite counts against your Organization's seat count from the moment it's sent, whether or not it's been accepted yet — so a pending invite still uses up a seat.
Pending invites
The Members page also lists every invite that hasn't been accepted yet. Revoke one to cancel it — for example a typo in the email address, or someone who no longer needs access — and its seat is freed straight away. An invite that's already been accepted can't be revoked; remove the member instead. If someone lost their invite email, revoke the invite and send a new one.
Seats
Your Organization's plan tier includes a certain number of seats; active members and outstanding invites both count against that limit. If you're out of seats, inviting someone new fails until you either free one up or add more.
Adding seats requires permission to manage the organization, which by default only the Owner has (stricter than inviting, since it changes what the Organization is billed for). Some plan tiers have unlimited seats, in which case there's nothing to add.
Billing
Adding seats and any usage across the Organization's projects is paid for from the owner's wallet — Raklane doesn't keep a card on file, so make sure your wallet has enough credit before adding seats or scaling up.
Seeing everything at once
An Organization's Deployments page lists every deployment across all of its Projects in one place — handy for an Admin or Owner who wants a bird's-eye view without clicking into each App individually.
Belonging to more than one Organization
If you're a member of multiple Organizations (your own personal one, plus any you've been invited into), you're only ever acting within one at a time. Use the Organization switcher in the dashboard to move between them — everything you see (Projects, Apps) reflects whichever one is currently active.
Removing access
Removing a member needs permission to manage members (Owner and Admin by default). Removing a member (or an Organization deleting itself) doesn't touch anything they built — Projects and Apps belong to the Organization, not to any individual member.