Members & roles

Every org member has exactly one role. Manage them under Settings → Members.

​

How people join

Automatically, through the upstream account. When a teammate signs in with GitHub or GitLab and belongs to the account your organization is linked to, slipway adds them as a developer with no invite needed. The check runs on every sign-in, so a new teammate picks up access the next time they log in. Removing someone upstream does not revoke their slipway membership. Remove them here as well. Manually, through an invite. For collaborators outside the upstream account, an admin sends an email invite or creates a one-time link.

​

Roles

Viewer is read-only, for people who need visibility without the ability to change anything. A viewer can read variable values. No role can read a secret’s value once it is set. Developer is the usual engineer role: create, deploy and tear down projects, compose them (add or remove services, edit specs), and manage secrets and variables. Admin adds organization-wide configuration: members, invites, registries, domains and billing — plus service runtime settings like compute size, alerts and edge access controls. Owner adds the ability to delete the organization. There can be more than one. Change a member’s role from the chip next to their name, which requires admin or owner. Removing a member does not tear down anything they deployed, because deployments belong to the organization. Anyone can leave from Settings → Members. The last owner has to promote someone else first.

​

Invites

To invite an external collaborator, click Invite member, pick a role, and choose how it reaches them:

• Send an email. slipway emails the accept link directly. The dialog also shows the link, in case the email does not arrive.
• Share a link. slipway returns a one-time accept link to pass along yourself. Copy it immediately, because only its hash is stored afterwards, and treat it like a password: anyone who opens it can join.

The recipient opens the link, sees the organization and role being granted, signs in with GitHub or GitLab, and lands on the dashboard. Invites expire after 7 days and are single-use. Revoke kills a link immediately. An invite does not grant repository access on its own. That comes from the organization’s GitHub or GitLab installation.