A team is one owner and the people they invite. Each team is completely separate: its own projects, profiles, proxies and people. Nobody in one team can see another team. Everything about people is under Users on the left, for the owner, admins and managers, in tabs: Team, VAs, Project access, Roles, and for the owner and admins Computers, Sites, Security and Activity. A VA sees none of it (What a VA sees).
The team's plan is at the top of the Team tab for the owner and admins, with what it uses. The owner chooses and pays for it under Account, Plan and billing; admins see it there read only (Plan and billing, the plans).
Team roles#
| Role | What it can do |
|---|---|
| Owner | One per team. Everything an admin can do, plus the security policy and making or unmaking admins. |
| Admin | Sees every project without being given it, creates and deletes projects, invites and lets people in, changes the roles of managers and members, reads the Activity log. Cannot touch other admins or the owner. |
| Manager | Sees only the projects given to them and does there what their rights allow. Sees Users (the team, project access, roles) and the team's proxy sheet. Can be allowed to give access to others inside those projects. Cannot invite people or create projects. |
| Member | Sees only the projects given to them and does there what their rights allow, and their own account. Does not see Users, the team's proxy sheet, the plan or the team's lists (What a VA sees). Can never give access to others, even if the box is ticked. |
A VA is normally a member. The team role is the ceiling; what someone may do inside a project is set on Project access.
To change a role, pick another in the Team role column on the Team tab. Making someone an admin asks first: an admin sees every project, whatever their access shows.
What a VA sees#
A VA works in the profiles they are given, like in AdsPower, and sees nothing of running the team. The team server refuses a member the same things, so nothing is hidden only on screen.
SablePower counts each person's active time per team profile: the minutes its window is in front and the mouse or keyboard is in use. The owner sees the team's in SableSpace on sabledesigns.com, and the owner and admins see the last 24 hours per profile in the VA time column. VAs do not see these numbers, in SablePower or anywhere else. Tell your VAs, it is their working time.
| A member sees | A member does not see |
|---|---|
| The projects and profiles given to them, opened and changed as their rights allow. Where a right is missing, the window says which. | Users: the people of the team and their email addresses, invitations, roles, who reaches which project, other people's computers, the security policy, the Activity log. |
| Who has a profile open, by email, in In use. | The computer someone else has a profile open on. |
| Their own Account: profile, language, password, their second factor, their sessions. | The plan and billing. |
| The proxies of their profiles. With Attach or detach a proxy or Create profiles, every team proxy to pick in a profile's Proxy tab, with its address hidden, and a new one pasted there. | The team's proxy sheet: vendor, price, expiry, notes, the team's own columns, adding, deleting or pasting many. Proxies shows them this computer's sheet only. |
| Their own computer, under Settings. | The team's domain lists and the domain lists of Settings, Data. |
| Help, What's new, Getting started, Extensions of their profiles. | The + that makes a team project, and renaming, sharing or deleting one. |
| The Local API and AI assistants, only with Export cookies and the bundle: automation reads every cookie (API). | Sharing a profile with a person: that is Grant access to others, which a member can never hold. |
A manager sees Users and the team's proxy sheet, and does there what the manager role allows. The owner and admins see everything.
Invite someone#
- Users, Team tab, Invite.
- Type their Email and pick the Team role, usually member.
- Optionally pick the Project they will work in and their Rights in the project: it is then ticked for you when you let them in.
- Press Create invitation. A code appears.
- Send it to them privately: Send… writes the whole message with the download link, the code and the steps, ready for By email, In Telegram, or Copy the text.
The code is shown once: the server keeps only a scrambled copy, so nothing can show it again. If it is lost, make another. It works once, for 48 hours. Whoever types it first gets the account, so never post it in a group chat; the verification code below catches it if that happens.
Every plan includes the owner. Each other person, admin, manager or VA, takes one member seat: an extra member seat is $2.50 a month, with the step discount from 10 seats. Open invitations hold a seat on your plan until they are used or run out (plans). The list shows them as Invited, not yet enrolled, with when they expire.
Let them in#
After they sign up, they appear on the Team tab as waiting to be let in, and the tab shows a number. Until you let them in, they can sign in and open nothing.
- Press Let them in on their row.
- Ask them, privately, for the 8 digit verification code their SablePower shows. Your window shows the code it must be.
- Tick They told me this code only if the two codes match.
- Tick the projects they should see. Only those open to them; the rest stay invisible.
- Press Let them in. Their screen opens by itself.
Letting someone in hands over the team key from your computer to theirs. That key never passes the server in a form it could read. Nothing ticked hands over the key alone (Give them the key), and you open projects for them later.
If the codes do not match#
A different code, or none at all ("the invitation has already been used"), means somebody else signed up with this invitation. Do not let them in. Press Remove on that row and send your VA a new invitation.
VAs: which profiles each one gets#
Like the VAs page of your Sable account: the VAs listed, and for each one the team's profiles with a switch each. A VA then sees exactly what is switched on for them, and nothing else of the team (What a VA sees). The team server checks it on every request, so nothing is hidden only on screen.
- Users, VAs tab. Each VA has a row: their address, whether you let them in yet, their team role, their rights, and how many of the team's profiles they can open.
- Click a row, or Choose profiles. Their page lists every project with its profiles.
- Choose their Rights at the top (below).
- Switch on Whole project to give every profile in it, also the ones added to it later. Or switch on single profiles.
- Each switch saves at once. The line above the projects says what it did, or why not.
Teams have hundreds of profiles: search by name, tag or the start of the ID, and narrow to one project, one tag, or what is switched on or off.
| Switch | What it gives | Where the VA finds it |
|---|---|---|
| Whole project | Every profile in the project, also the ones added later. The same as adding them on Project access. Single switches in it are folded into it. | The project in the sidebar, and its profiles in Profiles. |
| One profile | That profile only. Opening and working in it as their rights say; never making or deleting profiles, and never giving it to others. | Shared with me, and the command palette (Ctrl+K or ⌘K). |
Their rights#
Four boxes, for everything they get from you: Open (open the profiles), Edit (name, tags, notes, start pages), Cookies (export cookies and the bundle, and automation) and Passwords (saved logins and proxy passwords in the clear). Changing a box changes it at once on every project and profile they hold of yours. Changing the fingerprint or the proxy, and creating and deleting profiles, stay as set on Project access. Which to tick: Which rights a VA should get.
When the team has project roles, pick one instead: everything they hold follows the role, and changes when the role does. A single profile gets what of the role one profile can carry. Chosen here goes back to the boxes.
Before anything is switched on, the boxes say what the first switch will give. A box half filled means it differs between their projects; clicking it sets it for all of them.
Switching off a profile they have open#
Their access ends at once. A browser they have open stays open on their computer until they close it; what they did in it then stays there and is not saved to the team. To get their work into the team first, use Ask to close on the profile's row (One person at a time), then switch it off.
A VA you have not let in yet can be given profiles already: they see them once you let them in. Managers see on this tab the projects where they may give access to others. Every switch is in the Activity log.
Give access to a project#
- Users, Project access tab.
- Pick the project at Project:.
- At Add from the team, choose the person, then Add.
- Tick their rights. Each box saves as you tick it.
Remove from project on their row ends their access to that project at once. Owners and admins reach every project anyway and are not listed to be added.
To invite someone new straight into a project, pick that project when you invite them.
The rights#
| Right | What it allows |
|---|---|
| See the profiles | Always on: a grant without it is no grant. |
| Open them | Open and work in the profiles. |
| Change name, tags, notes, start pages | The profile's own details, not its fingerprint. |
| Change persona and fingerprint | The device and fingerprint settings. |
| Attach or detach a proxy, add new ones | Change which proxy a profile uses; add proxies. |
| See passwords and proxy credentials in the clear | Read saved logins and proxy passwords on screen, and copy the logins when duplicating. |
| Export cookies and the bundle | Take cookies and the whole profile out, and copy the cookies when duplicating. This also opens the profile to automation (API). |
| Create profiles | Make new profiles in the project, and duplicate its profiles. |
| Delete profiles | Move profiles to the Trash. |
| Grant access to others | Share the project with others. A manager can hold it; a member never can. Taking over a profile someone has open is not part of it: that is for the owner and admins only (One person at a time). |
Which rights a VA should get#
| Right | For a VA |
|---|---|
| See the profiles | Always |
| Open them | Yes |
| Change name, tags, notes, start pages | Yes, if they keep notes |
| Change persona and fingerprint | No |
| Attach or detach a proxy, add new ones | Only if they manage proxies |
| Create profiles | Only if they set up new accounts |
| See passwords and proxy credentials in the clear | No |
| Export cookies and the bundle | No |
| Delete profiles | No |
| Grant access to others | No |
With Export cookies and See passwords off, SablePower holds the VA to working the account, not carrying it away: the browser's developer tools are off, exporting passwords and bookmarks is blocked, automation is closed, and nothing of the profile stays on their computer after it closes. The proxy still works for them; they just do not see its password. When a profile opens like this, a line at the top says which limits apply. These limits stop the buttons and the usual ways, not a determined technical person who has the profile open on their computer. More in Privacy and security.
Many VAs with the same rights: project roles#
Users, Roles tab, New role…: tick the rights once, name it, for example "VA", and Save role. Then on Project access, pick it at Role: on each VA's row. Change the role later and everyone on it changes with it. Pick by hand to tick one person's boxes yourself.
Sites a VA may open#
The Sites tab holds the team's domain lists. Tick a list beside a person on Project access, and their profiles in that project refuse every site on it. A list whose first line is @allow-only works the other way: only the sites it names open. That keeps a VA's profile on the one platform it exists for. Owners and admins are never restricted.
A blocked https site shows the browser's own error, ERR_TUNNEL_CONNECTION_FAILED; see Troubleshooting.
Team computers#
Every person's SablePower tells the team server what kind of computer it runs on, each time it starts: the system and its version (Windows 11, macOS 15.2), the processor and memory, the graphics card, the screen and its scaling, how many speech voices the computer has and in which languages, and the SablePower version. It says nothing about the person: no files, no accounts, no addresses, and the voices' names are never sent, only how many there are and a code that tells two computers' voices apart.
The owner and admins see them under Users, Computers: each person, their computers, and when each was last seen. A person who has not started an updated SablePower yet shows No computer seen yet. Each person can see what their own computer sends under Settings, Team server, What is sent.
The device and the computer it opens on#
A profile is a device, for example a Mac. The browser still takes its speech voices, and a few other things no setting hides, from the computer it really runs on. So a Mac profile opened on a VA's Windows PC looks like two computers at once to a site that checks. Give each profile a device of the system it opens on. SablePower helps in three places:
- The profile window, Fingerprint tab, Who opens this profile, for the owner, admins and managers: the people the profile's project is given to and the system of their computers, with a warning that names who opens it on another system, and the fix beside it.
- A new team profile starts on the system most of its project's people use (a tie goes to your own computer's system), and the window says why.
- Opening: before a team profile whose device is another system than this computer opens, SablePower says so. Open anyway opens it and the Activity log records it. Opened through the API or a script, nobody is asked, and the log records that too.
The owner can make it a rule: Users, Security, tick Block opening a profile on a computer with a different system and Save. Such an open is then refused, by the team server and again by SablePower on the computer itself. Phone profiles are never refused: a phone profile runs on any computer by design. An app too old to say which system it runs on is refused while this is on, and is told to update.
Use someone's computer as the device#
Instead of a catalogue device, a profile can be a measured copy of the very computer it opens on. In Who opens this profile, press Use Anna's computer as the device, then Ask Anna, or on Users, Computers, Use as a device on her computer's row.
- Anna's SablePower shows the request on her computer: who asks, what is recorded, and that nothing else is.
- She presses Allow, or Decline. Nothing runs before she allows it.
- Her SablePower opens Google Chrome for a few seconds on a page on her own computer, records what sites see of it (system, screen, graphics card, fonts, speech voices), and sends the result to the team as a device. It needs Google Chrome installed.
- Your window, still open, says when it is done and uses the device: a new profile takes it at once; a saved profile asks first (below).
A request waits a day for her answer. A capture that finds a computer that could not exist is not kept, and you are told why.
Changing a saved profile's device#
A saved team profile keeps its device: sites that know the account would see another computer. When it opens on the wrong system anyway, Who opens this profile offers Change the device to Windows 11 (or the system concerned). It asks once more, saying what it costs, and needs the profile closed and the right Change persona and fingerprint. The change counts from the next open and is in the Activity log with both devices. Better done before an account is warmed up.
One person at a time#
A team profile is open on one computer at a time, like AdsPower: while someone has it open, everyone else sees In use with their name (and, for the owner, admins and managers, their computer), and there is no Open. Two people pressing Open at the same moment: exactly one gets it. The same profile cannot be opened twice on one computer either.
While the browser is open, SablePower on that computer tells the team server so every ten seconds, also with its window minimised or closed. One message that does not get through is tried again within seconds, so a computer that is on and online stays In use, never Not answering or free.
When you need a profile someone else has open:
- Anyone: ask them to close it. Closing saves their session to the team, and it then opens for you, logged in.
- The owner and admins have Ask to close on the row. Their SablePower closes the browser within about ten seconds, saves their work to the team, and the profile then opens for you by itself. They are told who asked. Nothing is taken from someone who is working.
- When their SablePower stops answering (the computer is asleep, offline or turned off), the row says Not answering after about 45 seconds, and the owner and admins get Take over. You get the profile as last saved; what they did after that stays on their computer. When their SablePower answers again, it closes that browser so two people are never in one account, and tells them who took it over. Every take over is in the Activity log.
- After about a minute and a half without an answer, the hold ends by itself and anyone with the right to open it can.
A SablePower older than this does not know Ask to close and keeps the profile open. Ask the person, or end their session under Users, Security: the hold then ends within a minute and a half.
When someone leaves#
Users, Team tab, Remove on their row. Their access ends at once, and the team key is replaced, so nothing they kept a copy of opens anything new. On the other computers SablePower asks once for the password to take the new key.
What they already downloaded stays on their computer: nobody can undo that part. That is why a VA should not have the export and password rights.
A lost or stolen computer#
Users, Security tab, Replace the organisation key. Everyone still in the team keeps their profiles; any copy of the old key stops opening anything new. Removing a member does this for you.
Activity#
The Activity tab (owner and admins) lists what happened in the team: invitations, grants, launches, deletions, sign ins, with who and when. Filter by kind, by email or by date.
A new team for someone else#
A team owner cannot make another team. Ask us for an owner code for the new owner. They follow Join your team with it, and are in straight away as the owner of their own, empty team. It starts with no plan, and its owner starts the free week in the app (how).