Team Management
The Team page lets you manage who has access to your Aelo organization and what they can do. Each user is assigned a role that controls their permissions.
Owner Admin
The team list shows all users in your organization:
| Column | Description |
|---|---|
| Name | User’s display name |
| Email Address | Account email address |
| Role | Assigned role (Owner, Admin, Supervisor, Rep) |
| Projects | Number of projects the member is assigned to; click it to manage the assignments. A Supervisor with none sees a “No projects” warning instead of a number |
| Access | The member’s narrow access (preset and scope) — By role when there is none. Shown when assigning narrow access is open for the organization, or when someone already holds one — see Narrow Analytics Access |
| Status | Active or Pending Invitation (invited but not yet accepted) |
Owner Admin
- Click Invite User on the Members tab of Settings → Team & Access.
- Enter the user’s Email Address.
- Select a Role from the dropdown: Owner (offered only to an Owner), Admin, Rep or Supervisor.
- For a Supervisor, tick at least one project under Projects to supervise. A supervisor can open calls only in the projects assigned to them, so the invitation cannot be sent without one. If there are no active projects yet, create one first.
- Click Send Invitation.
The user receives an email with an invitation link. Their status shows as “Pending Invitation” until they accept.
The invitee does not need to sign up: after clicking Accept Invitation the account is created automatically, and the person lands in the organization right away with the assigned role. If the email did not go out, Aelo tells you right after the invitation — resend it.

Notes:
- The dialog takes one email address, so invite users one at a time.
- Sent invitations are listed on the Invitations tab, where a pending one can be resent or revoked with the buttons at the end of its row.
- Admin users cannot assign the Owner role to others.
- Admin users cannot change the role of an Owner or remove one.
- To give a new user only a narrow view of the numbers, tick With limited access in the invitation — see Invite with limited access.
- The organization always keeps at least one Owner: the last Owner cannot be demoted or removed. Assign the Owner role to someone else first.
The organization owner with unrestricted access:
- Full control over all settings, billing, and projects
- Can manage team members and change roles
- Can delete projects and records
- Access to all reports and analytics
Administrative access with safeguards:
- Same as Owner except:
- Cannot manage billing
- Cannot assign the Owner role or change an Owner’s role
- Cannot delete projects
Team lead focused on performance:
- Views team analytics
- Sees calls from assigned projects, plus calls handled by anyone under them in the org structure (department tree) — and can open any call within that same boundary
- Can view alert events
- Can add notes to records in assigned projects
- Can create projects, and administers the ones they create
- Cannot edit projects created by others, evaluation profiles, criteria, or settings
Handles conversations with customers:
- Uploads conversation records
- Views own quality scores and performance
- Receives coaching recommendations
- Cannot view other reps’ data, unless given a narrow access such as Group lead
- Can add notes to their own calls
- Needs no project assignment: a rep reaches their own calls directly
Their own call is a record whose rep is this very user: their Aelo account or, for a record from a connected CRM, their employee in that CRM matched to their Aelo account (in Uspacy a match by email does not link the account — see Importing from Uspacy below). A record uploaded through the public API belongs to the Aelo user whose id is in agentId, so a rep sees it as their own only if that is the id of their own Aelo user; the Aelo interface does not show this id yet. A value that is not the id of any Aelo user (a CRM or telephony id, for example) is a separate person in analytics, linked to no account.
| Resource | Action | Owner | Admin | Supervisor | Rep |
|---|---|---|---|---|---|
| Projects | Create | ✅ | ✅ | ✅ | ❌ |
| Edit | ✅ | ✅ | ✅** | ❌ | |
| Delete | ✅ | ❌ | ❌ | ❌ | |
| View | ✅ | ✅ | ✅* | ❌ | |
| Records | Upload | ✅ | ✅ | ❌ | ✅ |
| List all | ✅ | ✅ | ✅† | ❌ | |
| Open all | ✅ | ✅ | ✅† | ❌ | |
| View own | ✅ | ✅ | ✅ | ✅ | |
| Delete | ✅ | ✅ | ❌ | ❌ | |
| Add notes | ✅ | ✅ | ✅* | ✅*** | |
| Rate analysis | ✅ | ✅ | ✅† | ✅*** | |
| Quality scores | View all | ✅ | ✅ | ✅* | ❌ |
| View own | ✅ | ✅ | ✅ | ✅ | |
| Export | ✅ | ✅ | ✅ | ✅ (own) | |
| Alerts | Create/Edit | ✅ | ✅ | ❌ | ❌ |
| View events | ✅ | ✅ | ✅* | ❌ | |
| Team | Invite users | ✅ | ✅ | ❌ | ❌ |
| Change roles | ✅ | ✅‡ | ❌ | ❌ | |
| Remove users | ✅ | ✅ | ❌ | ❌ | |
| Settings | Organization | ✅ | ✅ | ❌ | ❌ |
| Billing | ✅ | ❌ | ❌ | ❌ | |
| CRM Integration | ✅ | ✅ | ❌ | ❌ | |
| Profile | ✅ | ✅ | ✅ | ✅ | |
| Evaluation | Create/Edit | ✅ | ✅ | ❌ | ❌ |
| Scripts | Create/Edit | ✅ | ✅ | ❌ | ❌ |
| View | ✅ | ✅ | ✅ | ❌ | |
| Reports | View | ✅ | ✅ | ✅* | partly — see Reports |
| Deals | View | ✅ | ✅ | ✅† | ✅*** |
| Create CRM task | ✅ | ✅ | ✅† | ✅*** |
* Scoped to the supervisor’s assigned projects only.
** Supervisors can edit only the projects they created — creating a project makes them its project admin.
*** A rep acts only on the call they handled, and needs no project assignment to do so: their boundary is the record itself. Project membership is a supervisor mechanic.
† Includes subordinates: a supervisor’s boundary here is assigned projects plus anyone under them in the org structure (department tree) — see Org Structure And Supervisor Visibility below. A supervisor with neither an assigned project nor a department underneath them sees only their own calls.
‡ An Admin cannot assign the Owner role or change an Owner’s role.
Owner
Aelo can import your company’s department tree from a connected CRM (Bitrix24 or Uspacy), or you can build it by hand when you don’t use a CRM or prefer not to import. Either way, a supervisor at the head of a department sees the calls of everyone under them — including subordinate departments — in addition to their assigned projects. This is the same boundary for the call list, for opening a call, for search, and for rating an analysis: assigned projects ∪ subordinates by org structure.
One source for the tree. An organization’s tree comes either from the CRM or from your own hand, never from both. While the tree is built by hand, the Owner adds, renames, moves and deletes departments and sets each department’s members on the Org structure tab; a department with sub-departments can’t be deleted until those are moved or deleted. Once the tree is imported, it changes only in the CRM and with a new import — the department head is the one thing you can still assign by hand. Importing over a hand-built tree asks for confirmation first: the import replaces the whole tree — departments, their members and their heads — and «Group lead» access to the departments it removes is revoked. Importing from another CRM replaces an imported tree the same way, but without asking. To stop following the CRM — for instance after disconnecting it — choose Manage manually: the departments, members, heads and accesses stay, and from then on the tree is edited by hand. Employees who were waiting for an Aelo account leave the tree at that moment, so their calls stop appearing for their head.
Import order matters. Importing runs in two steps: it first matches your CRM users to Aelo accounts by email, then imports the department tree. For Bitrix24, a department head is only recognized once that matching step has found their Aelo account — importing the tree before matching users would leave every head unresolved. Uspacy works differently; see Importing from Uspacy below.
Syncing CRM users. On the Org structure tab, next to the Import from CRM button, there is a Sync CRM Users button: it matches CRM users to Aelo accounts by email. The button is available to the organization owner. The import works for Bitrix24 and for Uspacy; the separate user sync is for Bitrix24. In Uspacy the import does the matching — an employee matched by email joins their departments but gets no sign-in link (see below) — so the sync button is not shown there.
Importing from Uspacy. The import reads your portal’s employee directory (name, email, whether the person is active, departments; the portal’s app bots are skipped) and its departments (name, parent, head). It gives the same result as for Bitrix24: the department tree, its members, the employees who don’t have an Aelo account yet (shown by name) and the heads. Two things differ:
- A match by email makes someone a member, not a signed-in person. An employee whose email matches an Aelo account becomes a member of their departments, and the CRM id is kept on the membership — but their Aelo account is not linked to the portal. So the head of a department from Uspacy is assigned by hand by the organization owner — in the Head column on the Org structure tab; a manual assignment always wins and survives later imports. A head matched only by email gets no access.
- Processing must be active. The import works only while your organization’s Uspacy processing is active. Otherwise it refuses. An owner or an administrator reauthorizes processing under Settings → Consent Management, then the owner runs the import again.
If the portal — Bitrix24 or Uspacy — refuses the app access to its employee and department directory (the app’s token lacks that right), the import and the user sync say so: a portal administrator has to grant the app access, then run the import again.
The directory is read in full or not at all. If the CRM’s employee or department directory cannot be read in full — it holds more than 10,000 employees or departments, or the portal stops serving its pages — the import and the user sync change nothing and say so. If running them again gives the same answer, contact support. Importing part of the portal would drop the employees past the cut from their departments.
A department with no head assigned grants no access through it. If a department has no head in the CRM, its head is not an active employee of the CRM directory (dismissed, an app bot or a deleted user), or its head has no Aelo account tied to the CRM, nobody sees records through that department. Assign a head manually under Settings → Team & Access → Org structure to fix it.
Demo data comes with a sample org structure. While your organization has demo data, the tree also shows demo departments — a demo company with Sales and Customer support under it — headed and staffed by the demo employees and matched to their demo calls. Make someone from your team the head of a demo department, or give them «Group lead» access to it on plans that include it, to see these boundaries work on the demo calls. The demo data and its departments go away on their own: once your organization has its first record of its own, Aelo removes them when the organization owner opens Overview in the Aelo web app (the embedded Bitrix24 app does not remove them). So to practise on the demo calls, assign a demo department’s head before that point. Removing the demo data removes these departments, along with «Group lead» access that covers only them — that person is back on their role’s access, while an access that also covers other departments keeps those; departments imported from your CRM are not touched. Demo data loaded before October 2026 comes without these departments.
Subordinates without an Aelo account are covered too. In an imported tree, a head sees the calls of everyone in their part of the tree, including employees who have never signed in — the import keeps them from your CRM even when there is no account to link them to, and their calls are matched by their CRM identity. This works the same in the call list, on the record page and in search. The head’s own account is still required, because access is granted to a person: a department whose head has never signed in grants nothing to anyone.
Deactivated CRM users leave the department roster. The import only takes employees the CRM marks as active (for Uspacy: not dismissed), and in either CRM only an active employee is set as a head — a dismissed one, even with their Aelo account still matched, an app bot or a deleted user is not. So once someone is deactivated there, the next import drops them from their department — and their earlier calls stop appearing for their former head, in the call list, on the call page and in search alike. The calls themselves are untouched and stay visible to anyone with org-wide access. The same goes for a head: a head set by an earlier import keeps the department only while the CRM still names that person and their Aelo account is still matched to them, so a dismissed or replaced head — or one whose account is no longer matched — loses its calls with the next import. A head the Owner assigned by hand stays.
Notes and analysis reviews are not covered by this boundary: a department head can read a subordinate’s analysis, but sees its notes and can add notes or reviews to it only as a Supervisor assigned to that record’s project.
The Org structure tab lists the departments with their Members, Head and Coverage — how many people, across how many departments, the head sees through that department. Choose the head in the Head column (or leave ”— No head —”). Filter departments by name, or tick Only problematic to keep only those with no head or with people still waiting for an Aelo account.

Owner Admin
Sometimes a person needs analytics other than what their role opens — an analyst who only reads reports, or the head of a group who needs one department. A narrow access is a layer on top of the role that replaces what the role shows for analytics with what the chosen preset opens, in the scope you choose. It can be narrower than the role or wider: an Analyst sees aggregates only, while a Group lead on a Rep opens colleagues’ calls, transcripts, audio and team scores in the chosen departments, which the Rep role never shows. Only an Owner or an Admin can assign it. Narrow access is available on Pro and up.
| Preset | What the person sees | Scope |
|---|---|---|
| Analyst | Section aggregates only — flow, sales, quality, team and Voice of Customer. No records, quotes, audio, rep scores, finance or Alerts screen. | The whole organization, or the projects you pick |
| Group lead | Everything about their group: the same aggregates, plus rep scores and ranking, the record list and card, transcripts, quotes and evidence, and call audio. A chosen department includes the departments under it in the tree. | The departments you pick |
Employees without an Aelo account. A Group lead can open the page of an employee of their departments who has no Aelo account yet, as long as the organization has only ever connected that CRM through one portal. Once it has had two or more portals of that CRM, such a page stays closed. The page opens in the web app: inside the Bitrix24 app the name is not a link.
- Who: the Owner and the Admin of the organization. Nobody can change their own access.
- To whom: only a Supervisor or a Rep. A narrow access cannot be given to an Owner or an Admin — their settings, team, integrations and API keys stay with the role.
- While a person holds a narrow access, their analytics is exactly what the access opens — not what their role opens. Their role, project assignments and billing rights do not change. An action on a project — editing, archiving or deleting it, uploading a record into it, its scripts, supervisors, alert channels, routing and delivery rules — still needs the role, and goes through only for a project the access covers: any project for an Analyst on the whole organization, the chosen projects for an Analyst by projects, none for a Group lead, whose scope is departments. Creating a project goes through only with an Analyst access on the whole organization. Reading a project’s scripts, routing and delivery rules stops at the same boundary: a project outside the access is refused, and the lists show only the projects it covers. When the access is revoked they return to the rights of their role.
- Open Settings → Team & Access. The Access column shows each member’s access — By role when there is none.
- In the row of a Supervisor or a Rep, click the shield icon at the end of the row (Manage the access of …).
- Choose a preset and a scope — the whole organization or projects for Analyst, departments for Group lead. The dialog lists what will open.
- Click Save access. To take it away, click Revoke access and confirm.

Saving a new access for someone who already has one replaces it.
Deleting a project or a department takes it out of every access that names it, right away — the same when an org-structure import drops a department. The access keeps the projects or departments that are left; an access left with none is revoked, and the person is back on their role’s access.
In the invitation dialog tick With limited access and choose the preset and scope there. The person joins as a Supervisor or a Rep without projects and sees analytics as the access opens it. The invitation and the access are created together: if they cannot both be created, neither is. The new member’s row shows the access in the Access column right away.

A person who holds a narrow access cannot be changed to Owner or Admin. Revoke the access first, then change the role — when Aelo refuses the change, it offers to open the access dialog.
- A digest for the access. A person who holds a narrow access receives the daily and weekly email digest and the monthly Voice of Customer email built for their access, instead of the letter of their role. The area of the letter is the whole organization, the access’s projects, or the people of the access’s departments together with the person themselves; the letter names the area in a line under its intro — the whole organization, N projects or N departments — without any names. It carries only the sections the access opens: call flow and quality with alerts (Flow aggregates, Quality aggregates), sales (Sales aggregates), the best rep and the rep at risk (Team aggregates together with Rep scores and ranking), objections and Voice of Customer (Voice of Customer aggregates). The letter takes the team form when the access opens both Team aggregates and Rep scores and ranking, and the overview form otherwise: sales appear only in the overview form, the best rep and the rep at risk only in the team form. Calls, quotes and audio are never in these letters, and rep names appear only with Rep scores and ranking. Nothing is sent when the sections the access opens have nothing to report for the period, or when the access no longer covers any project or person. A Rep who holds the Group lead access receives the department letter instead of their personal digest. The same daily and weekly report switches apply. When the access is revoked, the letters of the role resume.
- Voice of Customer in the letter. The block of customer questions and decline reasons is included only when the access opens the text of records: a Group lead gets it, an Analyst does not. The monthly email follows the organization’s plan and is sent on Pro and up: after a downgrade below Pro it stops even while the access is active, whereas the daily and weekly digests keep arriving.
- Notifications are narrowed too. The role still decides who is notified, but the access narrows what each person sees. A notification about a call outside the access is not shown in their notification list, and nothing is sent to them by email, Telegram or webhook. For a call inside the access, a Group lead receives the usual notification; an Analyst, whose access opens no records, receives a message on those channels without details — a generic New notification, with no rule name, severity, participant, analysis text or link. Notifications that are not about a call (billing, system) follow the role as before.
Assigning a narrow access is available on Pro and up, and for a free organization during its 14-day Pro trial. Below Pro and outside the trial, the assign dialog and the invitation option are not offered. An access that is already assigned stays in force — also after a plan change or when the trial ends — and can still be revoked, but a new one cannot be given.
Every assignment and every revocation is recorded in the organization’s audit log right after it is saved. The entry is written separately from the change itself: in the rare case that writing it fails, the change still takes effect but has no entry in the log. Owners and admins read it in Settings → Organization → Access log.
Owner Admin
- Find the user in the team list.
- Click the trash icon (Delete User) at the end of their row.
- Confirm the action.
Removed users immediately lose access to the organization. Their historical data (records, notes) is preserved.
| Feature | Owner | Admin | Supervisor | Rep |
|---|---|---|---|---|
| View team list | ✅ | ✅ | ❌ | ❌ |
| Invite users | ✅ | ✅ | ❌ | ❌ |
| Change roles | ✅ | ✅‡ | ❌ | ❌ |
| Remove users | ✅ | ✅ | ❌ | ❌ |
| Assign narrow access | ✅ | ✅ | ❌ | ❌ |
‡ An Admin cannot assign the Owner role or change an Owner’s role.
- Assign the minimum required role — use Rep for individual contributors, Supervisor for team leads.
- Use Supervisor for team leads who need team analytics and oversight but shouldn’t change configurations.
- Keep the number of Owner accounts minimal (ideally 1-2 per organization).
- Review pending invitations periodically and revoke expired ones.
- When an employee leaves, remove their access promptly for security.