Inviting your team

Users lists everyone in your brand — their role, their status, and which menus they are scoped to. Its own subtitle is the scope of the screen: “Invite your team and control who can author, approve, and which menus they see.”

Your own row is marked (you).

Inviting someone

Invite user takes an email address and a role. They receive a sign-in link; there is no password to set or share, so there is nothing to leak and nothing to reset. See How Tavorly fits together.

Invite people as the lowest role that lets them do their job. Roles stack, so a Brand admin can do everything a Creator can — which means handing out Brand admin “so they can help” also hands out your palette, your locations and your ability to publish straight to the line without review. See Roles, and what each one can do.

Roles, and changing them

Each person holds exactly one role: Viewer, Creator, Approver or Brand admin. Manage on their row changes it.

A role change takes effect for their next request — you do not need them to sign out and back in.

⚠ Your brand needs at least two people who can publish. A Creator cannot publish their own work, which is the point of the role. If your only Approver or Brand admin is away, nothing your Creators write can reach the line until they are back. Two is not bureaucracy; it is the difference between a menu change waiting an hour and waiting a week.

Status

Active is the normal state. Deactivating someone stops them signing in while keeping their history — their authorship, their submissions and their approvals stay attributed to them. Revoking access never rewrites the record.

Do this when someone leaves, rather than deleting them.

Scoping someone to menus

The Menus column limits which menus a person sees. — means no restriction: they see everything in the brand.

This is for multi-brand or multi-concept operators where one person genuinely works on one concept. For a single-concept brand, leave it unrestricted — a scope that hides a menu from someone who needs it produces a confusing bug report rather than an obvious permissions error.

What is not here

• Manager PINs are not users. A PIN identifies a manager on a shared screen on the line; it is not a login and it does not appear on this page. See Manager PINs.
• Recipe viewers are not users either. A device belongs to a location. See Enrolling a recipe viewer.
• Tavorly support staff do not appear in your team list. If someone from Tavorly opens your brand to help, they are not counted as one of your people.