Treema HQ
Workspace settings

Team

Inviting people, granting module permissions, and activating or deactivating accounts.

The Team tab is where people are invited to the workspace and told what they may do in it. It is visible to the workspace's owner and its admins only — no level of Settings access opens it.

The list

Team screenshot
  1. 1
  2. 2
  3. 3
  1. Headcount by status, the status filter, and Invite User
  2. A pending invitation — resend it, or revoke it
  3. A deactivated account — the green button brings it back

The tab is headed "Team Members" with a running count underneath — "n active · n invited · n inactive". Beside it are a Filter by Status dropdown (All Statuses, Active, Invited, Inactive) and the Invite User button.

People who have accepted show their name, an Active or Inactive badge, their email and phone, and the line "Active account" or "Inactive account". People who have been invited but have not signed up yet sit at the top of the list with an Invited badge and the date they were invited.

Inviting someone

Invite User opens "Invite New User", which sends an invitation by email. It has two parts.

Team screenshot
  1. 1
  2. 2
  3. 3
  1. Who they are — all four fields are required
  2. Admin — grants everything at once, and greys out the rest
  3. The properties this person works at

General Information — First Name, Last Name, Email and Telephone. All four are required. The email you enter is the address the invitation goes to and the one they will sign in with.

Property Configuration — where you decide what the person may actually do:

  1. The Admin switch. Turning it on grants everything: as its description says, "Admins have access to all modules in all properties and workspace-level modules." It also gives them this Team tab, so they can invite and deactivate people themselves. The rest of the form greys out, because there is nothing narrower left to choose.
  2. Properties — tick the properties this person works at. Someone who only works at one hotel should only have that one ticked.
  3. Module Permissions — the per-module grid, described below.

Send Invite sends the email. If the address already belongs to someone in the workspace you get "User already exists in this workspace", and if an invitation is already outstanding, "User already has a pending invite".

Module permissions

Team screenshot
  1. 1
  1. One card per module, three choices each — nothing is granted by default

The permissions grid has one tab for Workspace plus one tab per property you ticked. Each tab lists the modules available there as cards, and each card offers three choices:

ChoiceMeaning
AdminFull use of the module, including the parts that manage it.
UserEveryday use of the module.
No AccessThe module does not appear for them at all.

The distinction between the two kinds of tab is what people most often get wrong:

  • A property tab grants access to that module at that property. Someone with Smart Inbox at Riverside Lisboa sees Lisboa's conversations and nobody else's.
  • The Workspace tab grants access to the module across the whole workspace, and it is also the only place the Settings module appears — "Workspace settings access", the grant described in What's in Settings.

Only modules switched on for your workspace appear here, so the grid may be shorter than the full product.

An invitation with no permissions is an account that can't do anything

Nothing is granted by default. If you send an invitation without setting any module to User or Admin, the person will sign in successfully and find an application with nothing in it. Set their access before sending, or edit it straight afterwards.

Changing someone's access later

The pencil button on a person's row opens "Edit User" — the same two sections as the invitation, so permissions are changed exactly the way they were granted. Names, phone and permissions are all editable; the email address is not, as the form notes: "Email cannot be changed after invitation". Save Changes confirms with "User updated".

Activating and deactivating

Deactivating is how someone leaves: their account stops working while everything they did stays attached to their name.

  • The red person button deactivates. It is deliberately absent on two rows — the workspace owner's, and your own — so nobody can lock the workspace's owner out, or themselves.
  • A deactivated person keeps their row, greyed to Inactive, and the green button reactivates them with the same permissions they had before.

Pending invitations

An invited person's row has two buttons instead:

  • Resend invite — sends the invitation email again, for the address that swears it never arrived. This is limited to once every five minutes; sooner than that and you get "You can resend an invite once every 5 minutes."
  • Revoke invite — cancels the invitation. The link in the email stops working, and the row disappears from the list.

Tracking who has actually started

Each person's row carries a badge showing how far they have got with their own Getting Started checklist, which is the fastest way to see who is genuinely up and running:

BadgeWhat it means
Not startedThe invitation was accepted but they have never opened the workspace.
Getting started n/nThey are working through the checklist.
Waiting for accessThey can sign in, but there is nothing for them to work with yet — open their row and grant a module.
Set upFinished, or dismissed by them.
Waived · n/nYou excused them from the checklist; their real progress is still shown.

The menu at the end of the row offers Send a reminder, which prompts them to pick the checklist back up — once a day, so it reads "Reminded in the last 24h" if you have already sent one — and Waive onboarding, which stops prompting an experienced hire who does not need the tour. Restore onboarding puts it back. Neither appears on your own row.

On this page