The question this page answers
Who can sign in to this workspace, what may each person do, which doors do they hold, and who is still waiting on an invitation? Team is the roster: people, invitations and the rungs they stand on.
What you see
- 1The figure row, People then every rung and state that has a row.
- 2Invite opens the drawer that sends an invitation.
- 3Require two-step sign-in, the admin's switch beside the search.
The head is the page's name and its one act, Invite; like every Settings page it carries no sentence. Under it, the figure row counts People, then Admins, Members, Viewers, Tightly staff, Deactivated and Invitations. People always shows; every other count appears only where it has rows, so no zero prints as a decision.
For an admin, while two-step sign-in is required, the figure row carries one more count, the active people who have not set it up yet: "Two-step not set up".
The table gathers its rows under two headings, People and Invitations, in five columns, and a sixth for an admin. Person is the name; a row that cannot sign in carries a badge beside it, Deactivated, and an invitation carries Invited and no name. Email is the address. Role is one of three customer rungs, Admin, Member or Viewer, with Tightly staff for a Tightly seat. Doors names what the person signs off: on Tightly Pro the doors are Commitments, The Buy and Skills; off Pro the one door is Skills. An admin passes every door and reads Every door on Pro and Skills off it; a person holding none reads None. Since is when they joined or were invited. An admin also sees Two-step: On or Not set up for each person, and a dash for an invitation, which has nothing to set up yet. Nobody else is shown the column.
The three rungs, lowest first: a Viewer reads; a Member works the product and may invite people; an Admin also runs the team, its roles, doors and access. Tightly staff stand above every customer rung, and their row is not yours to edit.
A search box, Find a person, narrows the rows; a search that matches nobody reads "Nobody matches “{query}”."
What to do
- Press Invite, add an Email and a Role per row (Add another for more), then press Send invitations. Members and admins may invite; a Viewer sees the button with "Members and admins invite people".
- Open a person's menu and press Open to see their Details, Signs off doors, What they can do and Access.
- Edit Role, Title or Department under Details, then press Save.
- Turn a door on or off under Signs off; an admin's own read "Admins always can".
- Press Deactivate… or Reactivate from a person's menu to stop or restore their sign-in.
- Press Remove… to take someone off the tenant for good.
- Turn on Require two-step sign-in, the switch beside the search, to hold everyone to a second step.
- Press Reset two-step sign-in… on a teammate's menu when they lose their phone.
An invitation's menu offers Resend invitation and Revoke invitation… in place of Deactivate and Remove. The consequence lines stand before each button. Deactivate: "{name} cannot sign in until an admin reactivates them; their doors still stand." Remove: "{name} loses access to this tenant now. Their recorded acts stay under their name." Revoke invitation: "{email} will lose their invite link, and getting them in would mean sending a new invitation." The decline is Keep. A row that is not an address reads "That is not an email address."; the same address twice reads "Listed twice."; an address already on the list reads "Email address already exists."; a drawer with nothing to send reads "Add at least one email". Each invitation row's own result is the server's sentence, printed beside it.
Require two-step sign-in's confirm says who it holds: "Everyone on this account who has not set up two-step sign-in is asked to set it up before they can carry on, from the next page they open." An admin with no second step of their own is asked to set up theirs first, and the confirm waits until the admin's own is read; where it could not be read, the drawer says so, with Try again. Reset two-step sign-in appears only on rows below your own role, never a fellow Admin's, staff's or yours: change your own from Profile, with your password.
Roles, doors and access are an admin's to change; the page says so once, "Admins change roles, doors and access", and a member sees the controls disabled. Nobody changes their own: "You cannot change your own role" and "You cannot change your own details, doors or access" stand where the controls would be. On the wire the role, the door grants and the removal need an Admin, and changing another person's details or access needs one too; inviting and revoking an invitation need a Member. A seat below the rung a write needs is answered:
Your access level does not cover this. Ask an admin on Team to raise it.
When it is empty or failed
A failed read prints "The team list did not load." in place of the table, and Try again takes the Invite button's place. An empty list prints "Nobody on the team yet." in place of the table; the Invite door stays. A refused write prints the server's sentence in the drawer, or in a banner above the table when the drawer is closed, with Dismiss.