Skip to content

Members and invitations

An account can have several people. Each is an owner or a member.

What a person may do Owner Member
Create, start, stop and delete pipelines yes yes
Create sources and credentials, rotate a source’s credential yes yes
Read everything: pipelines, history, alerts, usage, what was sent yes yes
Add a destination, or rotate a credential a destination uses yes no
Top up the wallet yes no
Change where the account’s notifications go: its address, switches and channels; resend yes no
Invite people, change roles, remove people, read the account’s changes yes no
Choose their own email, and leave the account yes yes

The API reference says, on every operation, who may call it (x-reyansh-access: member or owner). A member’s request to an owner operation is 403 owner_required. Two member operations need an owner in one case each (x-reyansh-owner-when): creating a pipeline with the older destination credential form (it creates a destination), and rotating a credential a destination uses (it changes where the data goes).

An account always keeps at least one owner. Removing or demoting the last owner is refused (409 last_owner), and so is changing your own role: another owner does that.

A role changes only when you confirm it. Choosing Owner or Member in a person’s row changes nothing by itself; press Change role, and a dialog names the person and the new role before Yes, make

an owner (or a member) makes the change. (Moving through the list with the arrow keys used to change the role at once.)

Settings → Members → Invite a member (owners), which opens the Invitations pane with its address field ready. Type the address and choose the role (member by default), then Send invitation. The invitation lasts 7 days.

  • The email carries a link only that person can use. We never show the link anywhere else, and no API answer carries it. If the email could not be sent, the answer says delivery: not_sent: press Send again.
  • Send again sends a new link; the old one stops working. One send a minute, four in all.
  • Withdraw ends an invitation at once.
  • One address has one open invitation per account. An account sends at most 30 invitation emails a day and holds at most 50 open invitations.
  • A pending invitation’s role cannot be changed: withdraw it and invite again.
  • Invitations are being switched on account by account while we prove the flow. Until yours is, Settings says “Invitations are not enabled for this account yet” (GET /v1/me answers invitations_enabled: false), and an open invitation reads paused.
  1. Open the invitation email’s link. The page shows the account, the role, who invited you and until when. Opening it changes nothing, so a mail scanner that opens it first does no harm.
  2. Press Email me a sign-in link. It goes to the address the invitation was sent to: you join as that address, never another.
  3. Open the sign-in link and choose Join .

Nothing is chosen for you. If you already belong to an account, or have an invitation, the sign-in page lists Your accounts and, apart from them, Invitations sent to

, each with who sent it and until when, and a Decline button. Your sign-in link stays usable until you choose, so declining one invitation, or finding that one has just ended, does not cost you a new link.

If the page says the address is not a member of any account and you were invited, sign in with the address the invitation was sent to.

One person can belong to several accounts with one address. The top of the sidebar shows the account you are in and, when you have more than one, a list of them with Switch. Switching keeps the time left on your session: only a sign-in link starts a new 12 hours.

Settings → Members → Remove (owners). Before you confirm, the dialog shows what the person created:

  • Pipelines they created, running ones first, each with Stop. Pipelines this person created keep running until you stop them.
  • Destinations and sources they created, with how many pipelines use each.
  • Credentials they wrote. Rotate them: they know the value. Change the secret where it is used (the database user’s password, for instance), then store the new value under the same reference: a destination’s on its page (Replace its connection string in its Settings pane for PostgreSQL, its Key rotation pane for Snowflake), any other with POST /v1/credentials/{ref}/rotate. The destination page also says who wrote its credential’s value (written_by on GET /v1/credentials/{ref}).
  • People who joined through their invitations.
  • API keys they created, each with Roll and Revoke. A key is the account’s, so it keeps working after they go; but they saw its secret once. See API keys.
  • What was made before people were recorded, counted, because nobody can be named for it.

Removing someone ends their sessions in the account at once and withdraws the invitations they sent, and their row leaves the list as soon as the removal is made. Nothing they made is stopped or deleted. If the account’s notifications went to their address, the dialog offers to send them to you instead; nothing changes that address silently.

Leave (everyone, on your own row) ends your access at once. The last owner cannot leave: their Leave is greyed out with “The last owner cannot leave. Make someone else an owner first.”

Settings › Notifications, the Your notifications section: which pipelines (the ones you create, every pipeline, or none) and whether errors and warnings, sent to your own address. Owners are always told when an owner is added or removed, and running out of credit goes to every owner, whatever they chose here (None included), and never to members. See Notifications.

Settings → Members, the Recent changes pane (owners), lists invitations sent, re-sent, withdrawn, accepted and declined, role changes, removals and people leaving, with who did each (GET /v1/membership-events). A decline names the person who declined.