Team is where you invite colleagues and set what they can do. Owners and admins can manage it, so the Team row appears in Account settings for both. Only an owner can make someone an owner, or change or remove one.

Your own role is under the account name at the top of Account settings, whatever your role is. The rest of that list is what your role reaches, so you only see the sections your own role covers.

go.tito.io/acme/admin/members

A role can apply to your whole account, to named series, to named events, or to Every event with none of the account-wide settings. Each member's row shows their role and where it applies, such as Staff · Whole account. To change where it applies, open the menu on their row. Owners are always account-wide.

On Team, open the menu on an existing member's row and select Make owner to make them an owner. Only owners can do this. No invitation email is sent.

Give someone more than one role

Somebody can hold several roles, each on its own events, such as Staff on one event and Viewer on every other. Open the menu on their row and select Change access, then Add a role.

Where two roles reach the same event, they can do everything either role allows there.
Account settings only come from a role on the whole account.
No role can do more than their role on Team. To give more, change that role first.
You can’t change your own access, or give someone a role that can do things you can’t.

What they can do, under their roles, shows what the roles add up to for each group of events, and for the account.

The six roles

Owner can do everything, including managing owners, custom domains, the sign-in policy and the account’s billing.
Admin runs the events, the account, its payment settings and the rest of the team, without those four.
Staff is the day-to-day job: orders, attendees, check-in, printing badges and messages. No refunds, no data export and no settings.
Door is Check-in and nothing else, for whoever is standing at the entrance.
Viewer can read the dashboard, orders, attendees and reports, and change none of it.
Copy reviewer can sign in to your events’ copy reviews, suggest wording and leave notes. That’s all they can open in your account. See Send your wording out for review.

Open What each role can do on the same page for the full table, area by area. Give somebody the role and then the events it applies to, so door staff for one event see that event alone. See Limit a colleague to certain events.

A member's row reads Custom access where their capabilities have been narrowed from the role by hand. A narrowed set can only ever hold less than the role it came from.

In Settings > Team, choose whether to allow any sign-in method or require Google. When you require Google, you’ll sign in with Google to confirm the change. Members who haven’t already signed in with Google will be asked to do so when they enter this account. Company single sign-on requirements still apply.

Once you’ve completed both sign-in methods with the same email address in one browser, you can switch between accounts without signing in again. Each method keeps its own expiry, and signing out ends both.

Requiring Google sign-in does not block personal tokens used by scripts or the Tito command line. Tokens still require team membership and stop working when revoked.

Good to know

Read the role table before assigning a role.

Open What each role can do on the same page. It says what each role can do, area by area.

Somebody you invite has no access until they join. Their invitation is under Waiting for a reply until then, and it lasts 14 days.
You keep your own access, and the last remaining owner keeps theirs, so somebody can always manage the account.
Tito support access is its own settings section, where anyone on your team can let Tito sign in for a set time.
Each person sets their own name in Edit profile, and their email shows while it's blank.
Your timezone is on the same page. It sets how times read on the dashboard, the activity feed and the rest of the account's screens. Until you set one, those screens use your browser's own timezone instead of UTC. An account screen with times on it names your timezone at the foot, with a link to change it. Inside an event, times use that event's own timezone, whoever is reading.