Teams
Use teams to organize triage, applications, jobs, and saved views in your workspace.
Overview
Teams let you organize recruiting work inside a workspace. Use them for recruiting groups, business units, regions, brands, departments, or any group that needs its own hiring workflow.
A team can own jobs, applications, application statuses, application labels, and team-shared views. Candidates remain workspace-level records, but their applications, labels, files, and activity can be scoped through the team connected to the job.
When a workspace is created, Attia creates an initial team. Admins can add more teams later as the workspace grows.
Your teams
Teams you belong to appear in the settings sidebar under Your teams. Open a team to manage its details and the recruiting work connected to it.
Each team is organized around:
| Area | What it contains |
|---|---|
| Triage | Newly created applications and hiring work to review before they enter the team's workflow |
| Applications | Applications for the team's jobs, including statuses and labels |
| Jobs | Roles owned by the team, including job status and team-specific access |
| Views | Personal, workspace, or team-shared saved views for recruiting data |
Team settings
Open Settings > Administration > Teams to see active and archived teams. Select a team to manage it.
| Team settings page | Configure |
|---|---|
| General | Team name, identifier, icon, parent team, timezone, estimates, issue creation by email, and detailed history |
| Members | Team members, team leads, inherited owners, and member removal |
| Application labels | Team-level application labels, label groups, and inherited parent labels |
| Templates | Team-level templates for applications, jobs, and documents |
| Recurring applications | Scheduled applications and recurring hiring work |
| Slack notifications | Team-level Slack notifications |
| Application statuses/workflows | Statuses, workflow automations, git automations, branch naming, auto-close, and auto-archive |
| Triage | Triage enablement and triage responsibility |
| Cycles | Cycle planning, cycle schedules, and cycle automations |
| AI & Agents | Team AI behavior, agent assignments, and automation guidance |
| Hierarchy | Parent team, sub-teams, inherited settings, and hierarchy rules |
| Danger zone | Leave, retire, restore, or delete a team |
Some settings are only available to workspace admins or team leads. Attia also keeps frozen teams read-only so retired or deleted teams cannot be changed accidentally.
Team limits
Team and sub-team limits depend on the workspace plan.
| Plan | Teams | Sub-teams |
|---|---|---|
| Basic | 1 | None |
| Business | 10 | 1 level |
| Enterprise | Unlimited | 5 levels |
Existing teams remain readable if a workspace later moves to a lower plan. New team creation and parent changes are checked against the current plan.
Create a team
Workspace admins can create teams from the Your teams section in the settings sidebar or from Settings > Administration > Teams.
When creating a team, set a name and identifier. The identifier is used as the short team key and must be unique inside the workspace.
You can also:
- Choose an icon and color.
- Place the team under a parent team.
- Copy settings from an existing team.
- Make the team private.
If a new team is created under a private parent team, the new team must also be private.
Privacy and access
Public teams and their recruiting records are visible to workspace members who can access the workspace. Private teams are limited to direct team members, workspace owners, and admins on non-Enterprise plans.
Team-scoped jobs, applications, files, comments, activity, labels, and views follow the same team access model. A saved view can be personal, workspace-wide, or shared with a specific team.
Workspace admins can create teams, add or remove team members, change member roles, retire teams, restore teams, and delete teams. Team leads can manage team-scoped resources such as application labels and workflow settings where those settings are available.
Sub-teams
Sub-teams let you model a hierarchy, such as Recruiting > Executive Search or EMEA > Germany.
A team can be nested under another team up to the hierarchy depth limit. A team cannot be moved under itself or under one of its own sub-teams.
Sub-teams keep their own members and settings. A parent team does not automatically add every child-team member. Statuses and labels can be inherited or mapped where the team settings surface supports it.
Private-team rules also apply through the hierarchy. A public team cannot sit under a private parent. When a parent team is made private, Attia asks for confirmation before applying that privacy change to affected sub-teams.
Tips for structuring teams
Start with the fewest teams that match how your hiring work is actually managed. You can add more later.
Common patterns include:
- One team for a small company or early hiring workspace.
- Teams by function, such as Engineering Hiring, Sales Hiring, or Operations Hiring.
- Teams by geography, such as US, EMEA, or Nordics.
- Teams by sensitivity, such as Executive Search or Confidential Hiring.
Use private teams when the hiring work should only be visible to a smaller group. Use team-shared views when several people need the same filtered view of jobs, applications, or candidates.
Manage teams
Make a team private
Admins can make a team private during creation on Business and Enterprise plans. Private teams limit access to team members, workspace owners, and admins on non-Enterprise plans. Sub-teams under a private team must also be private.
Add, remove, or leave members
Admins can add active workspace members to a team, change a member between member and lead, or remove a member from the team. Attia prevents changes that would leave a team without a lead.
Team members can leave a team from the team detail page. After leaving, they are sent back to workspace settings.
Retire a team
Retire a team when it should stop receiving new work but its history should stay available.
Retired teams are frozen. Past applications, discussions, and history stay accessible, but new work cannot be created or edited in that team. Retired teams can be restored later.
Delete a team
Deleting a team soft-deletes it and starts a 30-day restoration window. During that window, admins can restore the team from Settings > Administration > Teams > Recently deleted.
After the grace window, the team and its team-owned jobs, applications, workflow settings, statuses, labels, files, comments, and timeline records are eligible for permanent deletion. Workspace-level candidate records are not deleted just because one team is deleted.
Restore a team
Admins can restore a retired team at any time. Deleted teams can be restored during the 30-day restoration window.