அணிகளை உருவாக்குவது மற்றும் நிர்வகிப்பது எப்படி

A team groups the people who work together, whatever their department or job title. A team member has one department and one job title, but they can be on no team, one team or several. Like a department or a job title, a team can carry its own security roles, permissions, session timeout and charter, and these apply to everyone on it. It can also have a lead.

Only team members can be on a team: the people who work for you, AI team members included. Members, the people you serve, can't. See Members vs. Team Members Explained.

Before you start

You need the Configure System Settings right to create, change or delete teams. To change one person's teams from their profile, you need Manage Member Security.

Create a team

1. Go to Settings → Essential Setup → Teams.
2. Click Add Team.
3. Enter a Team Name of 2 to 120 characters. No other team in your organization can use the same name. Capital letters don't count, so "Sales" and "sales" are the same name.
4. Optionally set a Session Timeout (minutes), from 5 to 262,800. Leave it empty if the team shouldn't affect anyone's timeout.
5. Under Members, click Add Members, choose the people, and click Add to Team. To take someone off the team, click the × on their name.
6. Optionally choose a Team Lead: the person who heads the team. Only someone on the team can lead it. If you take the lead off the team, the team has no lead.
7. Under Expectations, write a Description of what the team is for (up to 2,000 characters), then add the team's charter items.
8. Under Associated Roles, check the security roles that apply to everyone on this team.
9. Under Direct Rights, set any right to Granted, Not Specified or Nuke. Rights your organization's security model forces are hidden, because no level can override them.
10. Click Save Team.

The team's members get its roles and permissions when you save.

If the save couldn't update the members' permissions, a message says so. Click Recalculate permissions in that message.

Choose a team's roles with care

A team gets exactly the roles you check. Unlike the job title editor, the team editor never adds a role for you.

Teams come after job titles in the waterfall (below). So a role on a team can grant back a permission that a member's department or job title nukes. Give a team only the roles and rights its shared work needs.

Change or delete a team

• To change a team, click Edit on its row. You can change anything you set when you created it.
• To delete a team, click the delete icon on its row and confirm. The confirmation says how many members the team has. They lose the team's roles and permissions, and nothing else about them changes. A deleted team can't be restored.

A person's teams

You can also choose teams from the person's side:

• On their profile. In the Work room, the Position card has a Teams field right after Job title. Anyone with Manage Member Security can change it there.
• When you add a team member. The Role section of the form has a Teams field, for anyone with Manage Member Security. When you hire an AI team member, its charter preview includes the teams you chose.

A person's teams also show on their member card, and next to their department when you pick people from the directory.

Limits: a team can have up to 500 members, a person can be on up to 25 teams, and an organization can have up to 500 teams.

How a team's permissions apply

A member's effective permissions are worked out in this order, and each level overrides the ones before it:

Role(s) → Department → Job Title → Team(s) → Member-level override

• A team's Granted or Nuke overrides what the member's roles, department and job title set.
• All of a member's teams count as one level. If their teams disagree, a permission any of a member's teams grants is granted.
• A right set on the member themselves still overrides every team.
• Someone on no team keeps exactly the permissions they had before.
• An AI team member gets its teams' permissions too, but never more than its supervisor holds. See AI Team Members Explained.

To see where a permission came from, open the member's Permissions tab. In the Granted By column, a permission from a team shows as Team: followed by the team's name.

Security Roles Explained covers the rest of the waterfall.

Session timeout

If any of a member's teams has a session timeout, the shortest of those teams' timeouts applies. It replaces the timeout from their roles, department and job title. A timeout set on the member themselves still overrides it. A team with an empty timeout has no effect. A change takes effect the next time the member signs in.

The team's charter

A team has a charter, just as a role, a department and a job title do. Under Expectations, the Description says what the team is for, and the charter lists its purpose, responsibilities, guidelines, boundaries and the rest. If the team has a description but no Purpose, the description is used as its purpose.

A team's charter becomes part of the charter of everyone on the team, so it is part of what each AI member on the team is told. An AI member's charter has one Team layer for each team it is on. These layers come after its job title's and before its own, ordered by team name. In the operating brief, a team's purpose is introduced by its name, for example "As a member of the Support team:".

Hiding and locking work as they do on a job title. The AI Charter Explained covers how the layers combine.