Your team and their handles

A batch only moves when people do their part: answering questions and approving changesets. Motions decides who may do which by two things together, the person’s role in the tenant and their handle in your motions.

Invite someone

1. Open Settings → Members and choose Invite. Only owners and admins can.
2. Enter their E-mail, pick a Role, and, if you know which handle your motions use for them, a Handle. Leave it blank to use the start of their e-mail address.
3. Choose Create invite link, copy the link, and send it to them yourself. Motions doesn’t send e-mail yet. The link works for 7 days, and only for that address.

Open invitations are listed under the members, where you can copy a link again or revoke it. When someone joins, they follow Join your tenant.

Roles and handles work together

A role says what kind of thing someone may do anywhere in the tenant. A motion then names the handles that may decide for it:

approvers: [hugo]
queues:
  fit: { owner: ari, deadline: 1d, default: hold }

To	They need
Answer a question in the fit queue	the member role or above, and the handle ari (the queue’s owner) or hugo (an approver)
Approve or reject a changeset	the approver role or above, and the handle hugo
Release a checkpoint, or upgrade a batch	the approver role or above, and the handle hugo
Make a version live	the approver role or above, and a handle among the approvers of the version that’s live now
Open a batch	the member role or above
Retry, pause or resume a batch	the approver role or above

Someone with the right role but a handle the motion doesn’t name sees the question or the changeset, but the buttons are refused with a reason such as “ana is not an approver of weekly”.

A queue that motion.yaml doesn’t list is owned by the first approver, and its questions default to hold.

The handle on an API token counts too

Pushing with --live, whether from your terminal or from GitHub, makes a version live, so the token’s handle has to be one of the motion’s approvers. Create tokens with your own handle rather than a made-up one like ci.

Change a handle

In Settings → Members, the menu next to someone has Change handle…. A handle that a live motion names, as an approver or a queue owner, can’t change until the motion does: change motion.yaml, push it live, then rename.

Roles

Role	What it’s for
Owner	Everything, including making other owners.
Admin	Manages members, motions, sources and settings, including the CRM connection and API tokens.
Approver	Publishes motions and approves changesets.
Member	Opens and follows batches, and answers questions.

A tenant always keeps at least one owner. The full matrix is in Roles and permissions.

A typical setup

For a consultant running motions for a client:

• You are an owner, with the handle the motions name as approver.
• Your client’s sales lead is an approver, and is added to approvers if they should approve writes to their CRM too.
• The people who know the accounts are members, and each owns the queue for the questions they can answer best.