Team members

Inviting someone#

Owners and admins invite people on the Team page of the console. An invitation is a mail with a link that stays valid for 7 days. Whoever accepts it gives their name and is in.

Each member has one role. Roles lists what each role may do. The admin role comes with the Business and Enterprise plans; on Solo, and without a plan, there are owners and members.

Your plan decides how many people the organisation can have: an open invitation takes a place until it is used or revoked. See Billing.

Note

An organisation needs at least one owner. To leave as the last owner, make someone else an owner first.

Signing in#

Brewless has no passwords. There are two ways to sign in:

• By mail. Enter your email address and you get a sign-in link and a six-digit code. Open the link, or enter the code.
• With a passkey. A passkey signs you in with your fingerprint, face or device PIN. No mail needed.

A link or code works once and for 15 minutes; after five wrong codes the request is dead and you ask for a new mail. One address can ask for five mails in ten minutes and twenty in a day. Brewless keeps only a hash of a link, a code or an invitation, never the secret itself. Every sign-in, sign-out and wrong code or link is written to the audit trail of the organisation.

A sign-in keeps you signed in on that browser for 30 days, also after you close it. Sign out on a computer that is not yours.

Brewless support in your console#

To help you, an administrator of Brewless can open your organisation's console as its first owner, with the same access. It takes a link that works once and for one minute, made in Brewless's own admin, where asking for it is recorded too. It cannot be done for an organisation that is ended or blocked.

While it lasts, the console shows a bar with the administrator's name and a Stop button; stopping signs the administrator out. The session ends with that, after an hour at the latest, or earlier when its sign-in expires.

Nothing made in such a session outlives it. Brewless support cannot:

• make a pipeline token;
• approve a sign-in from the command line;
• add a passkey;
• invite anyone;
• change a role.

The console says so where those are. Those stay for your own owners.

Everything in such a session is written to the audit trail of your organisation, in the administrator's name and marked Brewless support, as the owner whose access was used: the sign-in, every change, and the sign-out. Looking around is written down as it is for your own team: not each page, but what the console always records, such as looking at the values of your variables.

Command line clients#

A sign-in from the command line acts as you. The Account page lists the clients that are signed in, and lets you sign any of them out. See Signing in.