Teams

A team is a named group of people. Teams form a tree: a team can have sub-teams. The tree does two things in SalexHub: it decides whose records a person sees when their role gives them the Team scope, and, on Enterprise, a team can give its members a role.

Teams are in Settings > Members & access > Teams. The page is for people whose role holds the Teams right. Owners and Admins hold it, and an Admin can grant it to a custom role in Settings > Members & access > Roles. Without it the page says: "Managing teams needs the teams permission."

The tree#

New team creates a root team. Add sub-team on a team creates one under it. Each team in the tree can be renamed, moved, or archived.

• Rename changes the name only.
• Move under puts a team, and everything under it, below another team or at the top level. Moving a team under its own sub-team is refused, because that would be a loop.
• A parent team sees the records of every sub-team. A sub-team does not see its parent's. The page Access and sharing explains what that changes for a person.

Members#

Select a team to see its Members. Add member puts one or more people in the team. A person has one Primary team and any number of Additional ones; the member list marks which is which.

Taking someone out of a team removes them from that team only. Adding or removing people changes who sees which records, so the Agent never does it on its own: it proposes the change and a person confirms it, and it may not add the person who is asking.

Adding people, moving a team and restoring one widen who sees what, so they need the View all records right as well as the Teams right.

Roles a team gives#

On Enterprise a team can give its members a role. The role is added to each person's own role: they keep what they have and gain what the team's role grants.

• A role goes to the people directly in the team, never to the members of its sub-teams and never to an external user.
• Whoever joins the team later gets it too.
• Give role shows how many people would receive it and which restriction rules on that role bind them, and asks you to confirm. It asks you to confirm it is you first when you have not in the last two hours.
• You can only give a role whose permissions you hold yourself, and only when every member it changes holds no right you lack. The Owner role and the External role cannot be given by a team.
• Take back removes the role from the team's members. They keep their own role and what their other teams give them.
• Exclude from roles keeps one member out of what the team gives, without removing them from the team. The exclusion holds if they leave and rejoin. Give roles again reverses it.

If your plan does not include roles held by teams, the team's roles are marked Roles paused. They are kept and give nothing; they apply again on Enterprise.

Giving, taking back and excluding need the People right, not only Teams, and the same bounds as editing a person's role: you cannot give what you do not hold. Only a person does them. The Agent cannot, whatever its autonomy mode, and for a team that gives roles it is also refused adding or removing members.

Archive and restore#

Archive moves a team to the archive below the tree. Its members are kept, but the team grants nothing while it is archived: its members stop seeing its records through it and its roles stop applying. Records the team's members own are never touched. A team with live sub-teams cannot be archived: move or archive the sub-teams first.

Restore brings the team back with its members and its place in the tree, and they see its records again. If its parent is archived, restore the parent first.