Appearance
Teams
Administration › Teams keeps the teams people work in. A team has a name, a manager and members, and can be part of another team, so teams nest the way your company does: Sales, and under it London and Berlin. People who manage users manage teams; everyone sees them, to pick one. A role's own permissions on Teams give no more than seeing them.
Teams decide what team scopes reach, so someone who manages users without being an administrator cannot put themselves in a team or make themselves its manager, and cannot change the people or the place of a team they are in, or of a team below it.
New team adds one; the pencil changes it, the bin moves it to the trash. Teams are listed under the team they are part of. A team cannot be part of itself or of a team below it.
Putting records in a team
Teams are an entity like any other, kept in the system module. To put records in a team, add a related record field that points at Teams, such as Team on deals. People then pick a team for each record.
In a filter or a quick filter on such a field, My teams finds the records of the teams the person looking is a member of: one saved view, My team's deals, works for everyone.
Teams can have fields of your own too, such as a phone number or a region: Design on the teams entity adds them. Its built-in fields (name, part of, manager, members) stay.
Who sees a team's records
With Qorekit Pro, a role can let its people see, change or delete the records of their teams (Team), or of their teams and every team below them (Team and below): see roles. A record is a team's when someone in the team created it or is assigned to it, or when a field that points at Teams has the team chosen, so a team field is not needed for team permissions to work.