Attia for large and scaling companies
How owners and admins on Enterprise control access, structure teams and follow hiring across many teams.
Overview
This guide is for owners and admins at large companies, and at companies that grow fast, on the Enterprise plan. It covers how to control access, how to structure teams and which features to use when many teams hire at once.
Each section links to the article with the detail. If your workspace is not on Enterprise, read Attia for startups and mid-size companies instead.
Set up your workspace
SAML and SCIM
Enterprise adds two ways to manage people from your identity provider.
- SAML lets people sign in through your identity provider. Attia sets the connection up for you. On Settings → Security, the SAML & SCIM row has a Contact us button that starts the request.
- SCIM lets your identity provider add and remove workspace members. Only the workspace owner can set it up. People added through SCIM join as members.
- The Group to team row under a connection maps a group from your identity provider to a team, so people land in the right teams without anyone adding them by hand.
Roles
Everyone in the workspace has one workspace role. A team can also have leads.
| Role | What it means |
|---|---|
| Owner | A workspace admin with a few powers of their own, such as managing SAML and SCIM. Workspace owner lists them. |
| Admin | Administers the workspace. On a paid plan only the owner and members with the Admin role count as workspace admins. |
| Team lead | A role inside one team. Leads are that team's owners. See Team owners. |
| Member | The standard role. What a member can manage beyond their own work follows the workspace rules and team permissions below. |
| Guest | Reaches only the teams they are added to. A guest is refused every workspace rule below and never passes a team permission. |
Members and roles explains each workspace role.
Structure your teams
Teams and sub-teams
A team has its own members, application statuses, labels and templates. Teams covers what a team owns and who sees it.
A sub-team sits under another team. On Enterprise, teams nest up to five levels deep.
A structure that holds at scale
We recommend a small number of top-level teams, one per part of the organization that runs its own hiring and needs its own access. Use sub-teams for the lasting groups inside each one.
For a company of a few hundred people, that could look like this:
- Engineering, with a sub-team for each product area that hires on its own.
- Sales, with a sub-team per region.
- Operations, with no sub-teams.
- Executive search, as a private team.
A sub-team under a private team must be private too.
When to create a team
Create a team or a sub-team when the work has most of these:
- A group that hires together and will keep doing so.
- A process of its own, with its own application statuses.
- A real privacy boundary.
- Its own leads, or membership that someone needs to manage.
For hiring that cuts across teams, a temporary push or a reporting category, use what you already have. Job labels belong to the workspace, so they group jobs across every team. A custom view shared with the workspace shows the same slice to everyone.
Team permissions
A team's Access and permissions page has a Team permissions section. Each row is set to All team members or Admins & team owners only.
The rows are Settings management, Label management, Question management, Template management, Member management, Agent skills management and Loop management. Team owners explains what each one controls and who can change them.
What a sub-team keeps
A sub-team can keep its own application statuses, or take its parent's with Inherit statuses from parent team on its statuses page. Sub-teams lists what else a sub-team shares with its parent and what stays its own.
Workspace rules
Settings → Security has a Workspace management list. Each row decides who can do one thing across the workspace: Only admins or All members.
| Row | Starts on |
|---|---|
| Team creation | Only admins |
| Manage workspace labels | All members |
| Manage workspace templates | All members |
| Manage loops | Only admins |
| API key creation | All members |
| Modify agent guidance | Only admins |
All members never includes guests. Workspace security covers every row and who can change them.
The row New user invitations decides who sends invitations. It starts on Only admins. On All members, a member invites with the Member role, into teams they may add people to, and invites a guest only into a team they own. Only an admin invites an admin. See Invite members.
The audit log is part of the Enterprise plan.
Plan
Jobs
A job is one role you are hiring for. It carries a status, a priority, a start date and a target date, and it can have one lead. Working with jobs explains who can create a job and how to share one between teams.
Assign a lead
A job can have one lead. Pick the person who will keep the role moving. It does not have to be a team lead.
Write the brief
The job page holds the description candidates read and the job's properties. Documents hold the rest, such as a role brief or an interview guide.
Hire
An application is one candidate's submission to one job. It moves through the statuses of its team. Give it an assignee and labels.
An SLA puts a deadline on an application. Rules can set one automatically on Business and Enterprise.
A loop is a standing instruction for Attia Agent. It runs on a schedule or when something happens to a record.
Follow progress
Updates
A job update carries a health, On track, At risk or Off track, and your text. Updates live on the job's Activity tab.
A job also moves through the workspace's job statuses, and its job graph plots applications day by day.
Custom views
A custom view saves a set of filters and display settings under a name. Keep it personal, or share it with the workspace or a team.
Insights
Insights draws a chart of the records in a list. Use it to compare teams, for example how many applications each job holds or which status most of them sit in.