Această pagină nu este încă în limba dumneavoastră. Citiți textul în engleză.
Team
How to hand accounts to a contractor without the passwords
Echipa ARMANOS7 minUpdated

In short
A team seat instead of a password. The person signs in under their own name and sees only the profiles given to them.
A role and a group. The lowest role and one group cover three accounts.
Access ends in one step. It goes both ways, and the profile disappears from the contractor's app.
What a password really hands over
An account password is not one key but three.
It opens the account, for many people it opens the recovery mailbox too, and it keeps working after the work is over.
The platform sees you rather than your contractor, and there is nothing to explain the picture with.
Two logins to one account from two cities in a day are exactly the picture that sends an account for review.
- 1
The key to the account
A password opens the whole account, not the part the work needs.
- 2
The key to recovery
The same password often sits on the recovery mailbox, and then getting the account back leaves your hands.
- 3
A key with no expiry
A password you sent lives in the chat until you change it, and the change throws everyone out.
Your contractor signs in as themselves
Instead of a password you give the person a seat in your workspace.
They make their own account, arrive on an invite code, and sign in with their own email and password.
The owner always holds one seat, so count colleagues from yourself. A plan hands out seats as a bundle, and extra ones are counted one by one.
A seat beyond the plan costs $3 a month, an invite code lives 7 days, and you can revoke it before the person joins.
| Plan | Seats in the team |
|---|---|
| Free | 1 |
| Professional | 1 |
| Business | 3 |
| Enterprise | 20 |
An invitation works once
An invite code lives for seven days.
An expired code is refused the same way as an invented one, with one and the same answer.
An accepted code does not work a second time: an invitation carries an acceptance mark, and with it the invitation counts as used.
Only an unaccepted invitation can be revoked; an accepted one is undone by removing the person from the team.
One person can belong to several teams and keeps their own workspace.
Someone already on your team cannot join it a second time with a code, and the server says so outright.
What ARMANOS does for a contractor
A contractor signs in to the app under their own name and sees only the profiles handed to them.
You choose the role, the group and the access level, and you can end access in one step.
History shows who opened which profile and when, so fewer questions are left in dispute.
How to open access in ten minutes
Invite the person at their email address and pick the lowest role. The invitation code is valid for seven days and works once.
Tick one group with the right profiles and open those profiles to them.
Ask them to sign in and run "Test fingerprint": that way you confirm the profile's machine is the same on their side.
Five roles and what each one opens
A role is a step, not a list of ticks. A higher one opens everything a lower one opens.
A contractor on three accounts needs only the lowest step: it lets them work with the profiles handed over.
| Role | What it opens | Who it suits |
|---|---|---|
| Owner | The whole workspace: billing, team, history | You |
| Admin | Billing and plan, invitations, roles, group access, history | A team lead |
| Manager | Groups, the proxy library, scenarios, schedules, address change | The person running the work |
| Operator | Their own profiles and those handed to them | An assistant |
| Member | The same as an operator | A contractor on several accounts |
What each step adds
The two lowest roles, operator and member, are equal in rank: both work with the profiles handed over. A manager on top of that creates, edits and deletes shared working things: groups and the proxy library.
A contractor on three accounts does not need that step.
An admin adds billing, the team roster, history, other people's profiles and devices. The owner opens everything and is the only one who cannot be removed.
| Step | What it adds to the one below |
|---|---|
| Operator and member | work with the profiles given |
| Manager | groups and the proxy library |
| Admin | billing, team, history, other people's profiles and devices |
| Owner | everything, and cannot be removed |
Groups pin a person to one client
A role covers the whole workspace at once, so by itself it cannot say «this person runs client A only».
Groups do that: you tick the ones they may see, and their list shrinks to those.
The limit holds in two places at once, and there is no way around it through a request address.
A profile outside their groups is invisible in the list and by its id, and a profile with no group is hidden too.
The profile travels, the password stays
You open the profile itself to the contractor, and the machine goes with it: the fingerprint, the proxy and the settings.
The sign-in pair and the one-time code key stay on your computer and never reach the server.
Hand-picked values set in the app stay on that computer, while values sent through the API reach every computer.
So a platform sees the same computer from either side, keep one app version and one engine on both, and set no manual values on a shared profile.
- 1
The machine travels
Fingerprint, browser version, proxy and settings reach whoever you shared the profile with.
- 2
The sign-in stays with you
The login and password pair and the one-time code key stay on your computer.
- 3
Access comes back
Revoke the share and the profile leaves their app at the next sync.
One window per account
Two people opening one profile at once give a platform two live sessions of one account from two places, the worst thing you can show in a day.
So a profile carries one lock for everyone: while a window is open, the second computer sees that the profile is taken.
Time holds the lock: while the window is open, the app renews it every minute. If a computer switches off, the profile opens again after 3 minutes, with no call to an admin.
What is left after a parting
Every action worth arguing about leaves one row: who, what, when, and in whose workspace. There are 58 kinds of action, 6 of them about the team: invite, withdrawal, joining, role change, group access, departure.
The admin and the owner read these rows on the History screen.
A departure cuts access both ways at once.
The lock they held is lifted, the seat is freed by the same move, a second invite to the same address stops working, and the work profiles and your proxies stay with you.
Four roads and what each costs
There are four roads, and choosing between them is choosing what you risk. The table names the price of each in one line.
For three accounts and one person, take the second and third rows together: a seat, the lowest role, one group and access to the right profiles.
It takes ten minutes.
Keep the password-protected file for when a person needs an already open account, not a machine for it: such a file carries both the session and the sign-in pair.
| Road | What leaves your hands |
|---|---|
| A password in a chat | The whole account, for good |
| A seat, a role and a group | Exactly what you ticked |
| A shared profile | The machine and the settings, no login pair |
| A profile file with its session | A live session and the saved login pair |
Common questions
- Can I give access without making them an account?
- No. An invite goes to an address that already has an account, and that is the only barrier against a stranger holding the code.
- Will the contractor see my other accounts?
- Only if you have not ticked groups for them. An empty list means "no restriction": the window says so with the line "Nothing selected: the person sees all groups".
- How will they pass two-factor?
- The 2FA key from the One-time code window never reaches the server, so a shared profile does not carry it. The code is produced where the key sits: read it out yourself, or hand the profile over as a file.
- What happens to the accounts when we part?
- Access goes both ways at once, the lock is released, and a second invitation to the same address does not work. Cookies already written to their disk stay with them: change the account passwords.
- What does seating three contractors cost?
- Count from yourself: one seat always belongs to the owner. On a plan with three seats two colleagues join at no extra charge, and each one after costs $3 a month.
Keep reading
Give a contractor access
Invite the person, tick a group and pick a role: the passwords stay with you.