Invite Your Team & Set Roles
Admin ▾ → Users…
Both Admins and Editors can open Admin ▾ → Users… to invite people, change roles, and send password resets. (Viewers and Collaborators don't get the Users screen at all.) Every new user is automatically emailed a temporary password and your hub link — you never see their password; they set their own on first sign-in. Your plan includes a fixed number of seats; if you're at the limit, adding a user is blocked until you remove one or raise your seat band in Plans & Billings (section 17). A Filter by name or email box up top finds anyone fast in a long list.
The Four Roles
- Admin — full control: the entire schedule, every feature, branding, billing, deleting projects, and managing every user.
- Editor — runs the day-to-day: edits the Schedule, Lookahead, projects, crews, and branding. Can't touch billing or permanently delete projects. Can manage users — within limits (see the ladder below).
- Collaborator — a city-scoped role for field leads; edits one office's Lookahead only (detailed further down).
- Viewer — read-only; sees the Schedule and Lookahead, not Analytics.
Who Can Add Whom — the team-building ladder
User management is tiered, so you can delegate building out the team without handing over the keys:
- Admin — creates and manages any role (Admins, Editors, Collaborators, Viewers), and is the only one who can grant the Primary‑Editor flag.
- Primary Editor — creates and manages Editors and Viewers (not Admins, not other Primaries). This lets a lead build out their own editor bench without pulling in an admin.
- Editor (regular) — creates and manages Viewers only.
Each level only ever sees the people it's allowed to manage in the Users list, so there's no way to step on someone above you.
The Primary Editor
"Primary" is a flag an Admin sets on a single Editor. It promotes that editor so they can add and manage other (non‑primary) editors, not just viewers — ideal when you want a right‑hand person running the team while you stay out of the weeds.
- Only an Admin can grant or move the Primary flag, and there's only one Primary Editor at a time — assign it to someone new and it transfers automatically.
- A Primary Editor can't be edited or removed by other editors, and still can't create Admins or touch another Primary.
- The flag only applies to the Editor role; it shows as an amber Primary badge on that person's row in the Users list.
Assigning a Collaborator to an Office (City-Scoped Editing)
The Collaborator role is built for an area super or field lead who owns the upcoming work for one region and shouldn't touch the master schedule. You pin them to a single office, and the hub locks them to exactly that — one screen, one city.
To set it up:
- Open Admin ▾ → Users… and invite the person (or edit an existing user).
- Set their role to Collaborator.
- A City dropdown appears — choose the office/region they're responsible for, straight from your active offices. It's required for this role; a Collaborator must be tied to one office.
- Save. They're now scoped to that single city.
What they can — and can't — do:
- They sign in straight into the Lookahead. The Schedule and Analytics views are hidden from them entirely — there's nothing else to get lost in.
- On the Lookahead, they can only make changes to their assigned office — staging and claiming weeks for that one city. Every other city is read-only to them, enforced on the server, not just hidden in the UI.
- Their edits sync live to you and your PMs watching the full board, so each region's plan stays current without you handing over the keys to the whole schedule.
Tip: Give each region's field lead their own Collaborator login pinned to their office. They keep their city's Lookahead current; you keep the master Schedule locked down. Need someone to cover two regions? Give them a second Collaborator grant for the other office.