---
title: "Teams"
canonical: "https://help.agiloft.com/space/A2508SD/134055152/Teams"
format: markdown
---
Teams define collections of users with similar responsibilities and system access. You can view the configured teams by going to **Setup > Access > Manage Teams**. Users can be a part of multiple teams but must always have a Primary Team. The Primary Team determines a lot about how users can interact with the system, so it's vital that your users are assigned to the right team. Improper team assignments can prevent employees from doing their jobs or can enable someone to approve records they shouldn't be able to approve. For details on configuring teams, see [Teams](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43713262) in the Help Guide.

# Team Membership

Team membership, particularly Primary Team membership, determines a user's working hours, email distribution, available views, Look and Feel schemes, and search access. However, team membership itself is determined by two Person record fields that are linked to the Teams Table: a single-choice Primary Team field and a multi-choice Teams field. By default, the out-of-the-box system adds the Primary Team value to the multi-choice Teams field. This way, all of a user's team memberships can be found in a single field, which makes searching and filtering easier. 

When you initially import users into the system, you can import both their Primary Team and Teams using multiple comma-separated values with no spaces. Once users are in the system, you can update team membership by:

- Editing the Person records of specific users.
- Editing a Team record by looking up and importing users to either the Primary Team Members table or Team Members table, which are embedded in the Custom Fields tab. Looking up and selecting a user for either of these tables changes the linked field in the user's own user record to point to this Team.

### End Users

For end users, team settings control how the End User Interface (EUI) appears. In the out-of-the-box system, the end user teams are Customer Team and Supplier Team. If you have multiple teams that require different branding, color schemes, or views, you can create multiple EUIs. EUIs are stored in the EUI templates table and are applied based on the Primary Team field. Teams can also be associated with a different default language, so it makes sense to have language-based customer teams if you plan to operate in a multi-regional environment.

### Power Users

For power users, teams are also used as a way to assign ownership for records requiring completion, follow up, or approval. Each assignment group requires a separate team. For example, of someone requests a new Contract, the Contract Management Team can be notified to review the request. Teams can be hierarchical, so it's wise to set up a hierarchy that can send an email to a mid-level team where the members of the sub-teams also receive the email. Power users are assigned a Primary Team, which defines their Look and Feel scheme and default table views. Power users should be members of as many additional teams as needed, so that they are included in relevant emails and assignment lists.

# Team Records

Team records are stored in the Teams table. The Teams table is visible by default in the Companies and People Management module. There, you can view the list of teams in your system, as well as their ID and a brief description. Each Team includes settings that are used to ensure that each member has access to the correct data. These settings are configured using the tabs of the [Teams Wizard](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714439).

### Working Hours

Team records contain a special hard-coded field called Working Hours. The Working Hours tab is used to determine each team's Working Hours, which can be used to control when emails are sent.

![Working Hours settings on the Working Hours tab](media://3a8e0d24-97d4-4bd0-992a-0865ac953a4e)

### Languages

The Languages tab determines the language choices that are available to choose from in user preferences for that team. The system supports 20 different languages, as well as additional dialects for Chinese and Portuguese.

![List of available languages on the Languages tab](media://74cb612e-60f2-443d-997f-dd9e58e1f230)

### Formats

The settings of a user's Primary Team controls how the default date and time fields appear. For example, Primary Team defines whether a date field is displayed as May 15 2025 18:00 or 05/15/25 6:00 PM. This is determined on the Format tab of the Teams wizard. Some individual date fields can be configured to use a specific, customized format. This format is used wherever a date or time field is used throughout the system and on document templates. 

![Date and Time format settings on the Formats tab](media://4d1692d4-ba1c-461f-aaad-639d82985670)

### Custom Fields

Clicking the Custom Fields tab opens the Team record for that team in the Teams table. To modify fields or add new ones, you can access table setup by clicking the arrow next to Teams in the nav bar and selecting **Setup Teams**. Go to the Fields tab to work with fields.

# Default Teams

The table below lists the default teams in the out-of-the-box system. To view the teams, go to **Setup** > **Access** > **Manage Teams**. You can delete any of the default teams you don't need, create additional teams, or rename teams to match your company's naming conventions. 

| **Team** | **Description** |
| --- | --- |
| Admin Team | This administrator team is sent system notifications about errors. |
| AI Project Team | Members of this team work with the AI Platform. |
| Budget Management Team | Members of this team manage budgets. |
| Clause Library Team | This team manages language in the clause library. |
| Company Team | This is the main parent team for other internal teams. |
| Compliance Team Approver | This team is used in Contract Approvals. |
| Contract Creator Team | Members of this team are end user Contract Requesters. |
| Contract Management Team | Members of this team manage Contracts. |
| Customer Team | This end user team is used for external customers. |
| Evaluation Committee Team | Members of this team evaluate and score Supplier Responses. |
| Executive Team | This is the Executive team for Contract and Sourcing Event approvals. |
| Finance Team Approver | The Finance team is used for Contract approvals. |
| Internal Signer Team | Members of this team can sign internal Contracts. |
| Legal Management Team | This is the default team for users who handle legal requests. |
| Legal Requester Team | Members of this team submit legal requests. |
| Legal Team Approver | Members of this team approve Contracts. |
| Litigation Team | This team handles litigation matters. |
| Patent Team | Members of this team handle patent related matters. |
| Project Manager Team | Members of this team handle internal Projects. |
| Reviewer Team | Members of this team appear in approver drop-down lists for Review type Approvals. |
| Risk Team | The Risk team approves Contracts. |
| Sourcing Event Creator Team | This is an end user team that requests Sourcing Events. |
| Sourcing Event Manager Team | Members of this team manage Sourcing Events. |
| Supplier Evaluator Team | Members of this team perform Supplier Evaluations. |
| Supplier Lead Team | Members of this team are lead suppliers. |
| Supplier Management Team | This is an internal team that manages Suppliers. |
| Supplier Team | Members of this team are external end users who submit Sourcing Event Responses. |
| Trademark Team | Members of this team handle trademark related matters. |