How team sharing works
Multime shares profiles without a vendor cloud. The owner's computer hosts the team workspace: an encrypted HTTPS server that runs inside Multime on your machine. VAs connect to it over your local network or a private network such as Tailscale. There is no Multime server in between.
Setting it up takes four steps:
- Turn on hosting. On the Team page, switch on the workspace host. Multime lists the addresses VAs can use, with the Tailscale address first when you have one.
- Create an account for each VA. Enter their name and email, set a password, then choose which profiles they see and what they can do.
- Send them the address. For example
https://100.64.1.2:7799. The first time a VA connects, their app shows the workspace's certificate fingerprint. They check that it matches the one on your screen, so they know they're connecting to your computer and nobody else's. - They sign in from their own computer. VAs install Multime and sign in with the email and password you set. They see only the Team workspace and only the profiles you allowed.
By default the workspace accepts connections only from private addresses: your local network or Tailscale. Accepting connections from the public internet is a separate switch that stays off unless you turn it on.
Two workspaces: yours and the team's
Multime keeps two workspaces on the owner's computer. My workspace is private. VAs and admins never see it, not even in a list. Team holds the profiles you share. Your personal accounts stay in one, client work goes in the other, and you switch between them in the app.
Permissions per VA
Each VA gets a scope (which groups they see, plus any extra single profiles) and a set of permissions. Everything is enforced on your computer, not just hidden in the VA's app.
| Permission | What it allows |
|---|---|
| Open profiles | Start the browser for the profiles they can see |
| Create profiles | Add new profiles to the Team workspace |
| Edit profiles | Change name, notes, tags, fingerprint settings and start pages |
| Delete and restore profiles | Move profiles to the trash and back |
| Create and import profiles in bulk | Use bulk create and spreadsheet import |
| Export profile lists | Export profiles to Excel or JSON |
| Copy and export cookies | See and save a profile's cookies |
| Import cookies | Add cookies to a profile |
| See account passwords and 2FA keys | Read the saved logins of a profile |
| See proxy details | Without it they only see "Proxy set" |
| Add and change proxies | Edit the saved proxy list |
| Create, rename and delete groups | Manage groups |
| Manage extensions | Add or remove extensions |
| Run RPA automations | Use the no-code automation flows |
| Use the synchronizer | Mirror actions across windows |
| Use the local API | Drive profiles from scripts |
Three presets get you started: Open only, Daily work (open, create, edit, import cookies, synchronizer and RPA) and Everything. You can also make a trusted manager an admin, who can manage VAs and see the dashboard. Each active VA or admin account uses one seat; accounts you disable don't use one.
An example setup
An agency manages 40 client pages with four VAs. The owner puts each client in its own group. Sara handles clients 1 to 10, so her account sees only those ten groups, with Daily work permissions but no cookie export and no access to passwords. A senior VA who sets up new clients also gets bulk import and proxy editing. The owner's own ad accounts stay in My workspace, where no VA can see them.
One person per profile
A profile can be open for only one person at a time. When a VA opens a profile, Multime locks it. Anyone else who tries sees who has it open. The same person on a second computer is refused too, so one profile never runs in two places at once.
If a VA's app stops checking in while a profile is open, for example because the laptop went to sleep or the connection dropped, your computer releases the lock after about two minutes and writes that to the activity log. You can also close a VA's profile yourself from the dashboard. Their work is saved back to the workspace when it closes.
The owner dashboard and activity log
The dashboard shows who is online, which profile each VA has open and since when, how many profiles are open across the team, and how many opens each person has made today.
The activity log records every action: each profile opened and closed (with the computer it ran on and how long it stayed open), edits, deletions, cookie imports and exports, 2FA codes viewed, proxy changes, and changes to member accounts. You can filter it by person, action, text and date range. When a client asks who changed something on their page last Tuesday, you can answer.
Where profile data goes
When a VA opens a team profile, their app downloads that profile's data from your computer and starts the browser locally. When they close it, the cookies and the browser data you chose go back to your computer. By default that's cookies, local storage, IndexedDB and extension data; bookmarks and history can be added per profile. Then Multime deletes the profile's folder from the VA's computer. Nothing of a team profile stays there between sessions.
If your computer can't be reached at the moment a VA closes a profile, their app keeps that session encrypted and sends it automatically when the workspace is back.
Use Multime's saved logins for passwords. The browser's own password store is tied to each computer's keychain and doesn't travel between computers.
Honest limits
- While a VA has a profile open, the VA's computer holds the session. The logged-in browser is running in front of them. Permissions control what Multime lets them do, but they can't control everything a person does inside an open browser. Share profiles only with people you trust with those accounts.
- Your computer has to be on. Multime must be running on the owner's computer and reachable for VAs to sign in and open profiles. If your VAs work while you sleep, host the workspace on a desktop that stays on.
- The proxy runs from the VA's computer. While a VA works, the profile's proxy connection starts on their machine. Proxies with a username and password work from anywhere. Proxies that only allow listed IP addresses need each VA's IP added.
- Mixed Mac and Windows teams. Mac profiles use the Chrome 152 engine and Windows profiles use Chrome 150. Leave a team profile's engine on "Auto" so it opens on both.
Plans with VA seats
| Plan | Monthly | Yearly | Profiles | VA seats | Computers per license |
|---|---|---|---|---|---|
| Team | $49 | $490 | 300 | 5 | 3 |
| Agency | $129 | $1,290 | 1,000 | 20 | 5 |
The Free and Solo plans don't include VA seats. If you move to a plan with fewer seats than you have active VA and admin accounts, the most recently added accounts beyond the seat count can't sign in until a seat is free. Paid plans are billed by Stripe. See pricing for all plans, or how agencies set this up on the social media agencies page.