Organizations

Everything in Rift belongs to an organization: the GitHub accounts it connects, the repositories it watches, the secrets it sets. There are two kinds.

• Your personal organization. Every account has one, from the moment it's made, and your work starts there. It's yours alone: nobody can be invited to it. Every tool that takes an organization takes personal for it.
• Teams. To work with other people, you make a team, or join one you're invited to. You can belong to any number of teams, as an admin or a member — a contractor working for several companies belongs to each of theirs.

This page is how teams are made and joined, and where the admin line falls. Your agent does each step with a tool, and the app's Organizations page has each one too.

Make a team

When you want to bring someone in, make a team. Before you make one for your company, ask around: a colleague may already have made it, and a company's GitHub organization can be connected to only one team on Rift.

Through your agent:

rift_org_new  "Acme Inc"

or in the app, with Make a team on the Organizations page.

You're the team's admin from that decision on; its id is the slug of its name — acme-inc — and that id is what every later tool takes. Anyone with an account may make a team.

Invite someone

Admins invite, by email. Through your agent:

rift_org_invite  acme-inc  them@example.com
rift_org_invite  acme-inc  them@example.com  role=admin

or in the app, with the team's Invite form, which takes their email and their role. The invitee gets an email that says how to join. They don't need an account yet — an invitation is addressed to an email, so it may come before the account, and it's waiting when they arrive. It's also what lets them make an account: Rift is invite-only for now, and an invitation to a team is one way in. A person without an invitation can join the waitlist at https://fixedlabs.dev/waitlist.

Nobody can be invited to a personal organization; rift_org_invite personal is refused and says to make a team.

Accept, or decline

An invitation heads the rift_whoami document an agent reads, and shows on your Organizations page, until it's answered. Through the agent, rift_org_accept; in the app, Accept or Decline. Accepting makes you a member with the role the invitation carried.

See your organizations

rift_whoami lists your personal organization first, then each team with your role in it and its members. The Organizations page shows the same, and also each team's invitations that are not accepted yet. Until you accept an invitation, you see the team's name and the role you're invited to, not its members.

Admins and members

The line is simple. Members read: the organization, its repositories, its pools. Admins change things:

• invite people
• connect GitHub accounts, and enable or disable Rift for them
• watch and unwatch refs
• set and remove a repository's secrets

In your personal organization you're the only admin. In a team, both admins and members may claim VMs from any watched ref, through an agent, and put their own VMs away. A VM belongs to the person who claimed it, not to the organization.