Settings > Team is where an owner or admin invites colleagues and sets what each one can do.
Inviting someone
Enter their work email, pick their role, then what they do, and send the invite. The job function is the work, not a title, and it does not change what they can see. See choose a job function. Aptiro emails them the link. If your organisation has its own email set up (Settings > Notifications) it goes from there; if not, it goes from Aptiro, and the confirmation tells you which. Either way, the link is also shown so you can copy and send it yourself, over Slack or however you prefer. To stop it being used to send spam, an organisation can send a limited number of invite emails an hour; past that, the invite is still created and the link still shown.
The invite email's Join button opens Aptiro's sign-up with the invited address already filled in. Someone new creates an account with that address (or signs in with Google using it) and is added to your organisation straight away; someone who already has an Aptiro account just signs in.
The link works for seven days, for one person only: whoever accepts it must sign in with the exact address you invited, Google or email and password. See your first sign-in if they have not used Aptiro before; a password, if they use one, is reset from the sign-in page. Someone who signs in with a different address, a personal account instead of their work one, say, is refused and told so. Invite that address instead, or ask them to sign in with the one you invited.
It can only be accepted once. If it is not accepted, or you need to resend it, Pending invites (below the member list) shows every outstanding invite: who it was sent to, their role, and when it expires. From there you can copy the link again, resend the invite email (the expiry date does not change), change the role before it is accepted, or revoke it outright. An expired invite is still listed but cannot be resent; copying its link reissues it with a fresh seven days, after which you can resend it.
Sending a password reset
If a teammate who signs in with a password has forgotten it, an owner or admin can open their actions in the member list and choose Send password reset. They get an email with a code to choose a new password. You never see or set their password. Their current password stops working straight away, and the next time they sign in with email and password they are asked for the code we email them. Anyone already signed in stays signed in; use Sign out everywhere for that. You cannot send one to yourself (use Forgotten password on the sign-in page), only an owner can send one to another owner, and it is not offered for members who sign in with Google, who have no password to reset.
Seats
Your plan includes a number of seats (Starter 3, Growth 10, Scale 25), and you can buy extra ones in Settings > Billing. A seat is held by each active member and by each pending invite, so inviting ten people at once uses ten seats before any of them has joined. An invite that expires, or that you revoke, gives its seat back. A member whose custom role your plan no longer includes, or whose subscription has lapsed, is paused and does not hold one; giving that member a built-in role brings them back and takes a seat, so it needs one free. Complimentary accounts have no seat limit.
The invite form shows how many seats are used and available. When there is none left, Send invite is switched off. An owner, or anyone else who can manage billing, sees Add a seat, which opens Billing; everyone else is told to ask someone who manages billing to add a seat. Reissuing an expired invite needs a free seat too, because it brings the invite back to life.
Going over is never used to remove anyone. If your organisation already has more people than seats, they all keep their access; you just cannot invite anyone else until you are back under the limit or have bought more seats. Accepting an invite that is already pending always works.
A reminder about a day after you sign up
About a day after the organisation is created and activated, Aptiro emails the owners with a link to Settings > Team. The email comes from Aptiro, once, during the daytime in the UK. Ignore it if you have already invited people, or if you are working on your own for now.
Built-in roles
Every member has one role, named for what it lets them do rather than for a job title:
- Admin, everything Full access can do, plus settings, integrations, the team and finding new accounts. Billing (plan, seats and credit purchases) is for owners, and so is seeing everyone's pay.
- Full access, every account, and every bulk and automation tool: scans, triggers, sequences, bulk edits, exports, assigning owners, and building, sharing and scheduling reports. It does not change settings, integrations, website forms or the team.
- Team manager, edit, bulk-change, assign owners and export within your branch. Run scans and work signals on those accounts, and build and schedule your own reports. It does not change settings, the team or billing, and it does not run organisation-wide jobs.
- Standard, your own records, one at a time. You can also see your team's records and unowned ones. When you win a deal, you can still open that deal and its account, read only, after the account moves to someone else. You do not see the account's other deals, contacts or activity, and you cannot open its files, draft outreach on it or take ownership of it: those show as not found. This applies to any role that closes deals on its own records.
- Read only, look at your own and your team's records, and unowned ones. No financial figures.
- Audit, read everything, plus the audit log. Build reports and export them. Changes no records.
These roles used to be called Manager, Sales, Viewer and Auditor. Only the names changed: Manager is now Full access, Sales is now Standard, Viewer is now Read only and Auditor is now Audit. Everyone kept the role they had, with the access they had.
None of these roles makes someone a team lead. Leading a team is set on the team, as described under Team leads below. Team manager is the role for someone who should change records across their branch. The lead flag does not add that.
What Team manager can do
Team manager works the records in their branch, not only their own:
- Records: add and edit accounts, contacts, deals and activities in the branch, and unowned accounts, on the same unowned rules as Standard. They delete only their own accounts, contacts, deals and activities, as Standard does, not a rep's.
- Bulk changes, owners and exports: change several records at once, assign an owner, and export accounts, contacts and deals in the branch. An export does not include accounts they can only open because someone they lead also belongs to another team.
- Signals and scans: mark a signal actioned, snooze it, dismiss it, log one by hand, and scan or enrich accounts in the branch. Scans do not reach unowned accounts. Deleting a signal, and scanning or re-scoring every account at once, stay with Full access.
- Reports: build their own, and schedule one to be emailed to themselves. Sharing a report, and sending it to other people or to Slack, stay with Full access.
They cannot change settings, integrations, the team or billing. They cannot find new accounts, build sequences, see the audit log, or see everyone's pay. Billing stays with owners.
What Standard and Audit can do on their own
Standard works the records they own, and the unowned accounts, and reads their team's:
- Signals: mark a signal actioned, snooze it, dismiss it, log one by hand, and scan or enrich the accounts they own, not unowned ones. Scans and enrichment cost credits as usual. Deleting a signal, scanning or enriching an unowned account, and scanning or re-scoring every account at once, need Full access.
- Bulk changes: select several contacts and enrol them in a sequence, or change the owner of several contacts or deals. This reaches records they own, plus those on unowned accounts, and no one else's.
- Reports: build their own, export them as CSV or Excel, print them, and schedule one to be emailed to themselves. An export holds the records they own plus those on unowned accounts. Sending a report to other people or to Slack, and sharing it with the organisation, stay with Full access.
Audit stays read-only on records, and can also build and save reports, and export or print them across the whole organisation. Deal values stay visible to them.
No export from any role includes pay figures. Where a role that can change some things cannot do something else, the button is still there, greyed out, and says to ask someone with Full access. Inside a branch, Team manager can make the day-to-day changes, bulk changes, owner assignments and exports that Standard cannot make on a colleague's records. Organisation-wide jobs, settings and billing still need Full access, an admin or an owner. Read only has no change controls at all, so shows none.
Any member can also be made an owner. Being an owner is a flag, not a role: it grants everything, including billing, whatever role is set alongside it, and is the only way to manage billing at all. The Billing page in Settings is for owners only: no built-in or custom role can be given it. Everyone else still sees what an action costs in credits, wherever they use it. How many credits are left, the seat price and credit usage need the Credits: View permission, which Admin, Full access, Team manager and Audit have. Standard and Read only do not.
Custom roles
On the Scale plan, build your own roles instead of using the built-in ones. Each role sets a level, None, View, Work or Full, per area: accounts, deals, reports, settings, and the rest, rather than one switch per permission. Record areas also have a reach, Own, Team or All, set separately for what a role can see and what it can change, so "sees the whole team's accounts, changes only their own" is one setting rather than a workaround.
Teams (also under Settings) group members around a slice of accounts, prospects, clients or churned, so a scoped role's "Team" reach has something concrete to mean for that member. The team is only half of it: joining a team changes what someone sees only if their role's reach for that area is Team. A role that already reaches the whole organisation, or one scoped to its own records, is unaffected by any team.
Ticking a type the team covers reaches that type within the team's branch. "All clients" means every client account owned by someone on the team or on the teams beneath it, for every member on a Team-reach role, and for a role whose changes reach is Team that includes editing and deleting them. It does not reach clients owned by other teams. Unowned accounts follow your organisation's unowned-account setting, not the team's coverage. The team dialog reads your choice back in a sentence as you tick, so check that sentence before saving.
Team leads
A team can have one or more leads. An owner or an admin, anyone who can manage teams, picks them in the team dialog under Settings > Teams, when the team is created or later by editing it. Leads are chosen from the team's members, so add someone to the team first. Taking a member off the team also takes away their lead flag.
Being a lead is not a role, and it is not Full access or Team manager. A lead cannot edit membership or appoint other leads. To let someone see their team's accounts, give them a role whose reach is Team. Team manager is that kind of role, and it also lets them change records in the branch. The lead flag then also lets them open accounts that someone in their branch can already see through another team. They can read those accounts. Editing, deleting, bulk changes, assigning owners, taking ownership, scanning and exporting stay on the reach their role already had. What the flag also does is mark that person as the team's lead. A lead can set quotas for their team (see set quotas for people and teams), and turn on the team's notification roll-up. Leads also appear in the Team lead filter on the Past close and Retention dashboards, which lists the people whose teams they lead.
Coverage targets, a number or a percentage of hot accounts to reach, are set in Goals, not on the team. In a team's settings, the link to set coverage takes you to Goals. On the dashboard, the Outreach card (team view) lists this period's coverage goals under the hot-account count, grouped by team. Each shows what has been achieved against its goal with a small progress bar, and the card links on to Goals when there are more than four. A team that had a coverage target under Settings, then Team, before it moved onto Goals needs it set again there: that older value was not carried over.