Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.slipway.sh/llms.txt

Use this file to discover all available pages before exploring further.

slipway uses token-based invites. An admin or owner creates an invite, slipway returns a one-time accept link, and the recipient signs in (or signs up) with GitHub and clicks Accept.

​
Create an invite

Under Settings → Members → Invite:
  1. Enter the recipient’s email (used for display only — slipway doesn’t send the invite for you).
  2. Pick the role they’ll get on accept (see Members & roles).
  3. Save.
slipway returns the accept link. Copy it now — the plaintext token is shown only on creation. After that, only the hash is stored. Share the link with the recipient out-of-band (Slack, email, etc.).

​
Accept an invite

The recipient opens the link. If they’re not signed in, they’re walked through GitHub OAuth first. Once authenticated, they’re auto-redirected to the accept endpoint, which adds them to the org and lands them on the dashboard. Invites are idempotent on accept — re-opening the link after acceptance just signs them in to the org they’re already a member of.

​
Expiry

Invites expire 7 days after creation. After that, accept returns an error and the invite is dropped from the list. Re-create if you need to.

​
Revoke an invite

From the invite list, click Revoke. The token’s hash is deleted; the link stops working immediately. Use this if you sent the link to the wrong person.

​
What invites don’t do

  • They don’t send email. slipway gives you the link; you decide how to deliver it.
  • They don’t bypass the GitHub install requirement — joining an org doesn’t grant access to deploy from a repo that’s not in the org’s GitHub installation. That’s an org-level concern.