Esta página aún no está en su idioma. Está leyendo el texto en inglés.
Knowledge base
Invite a teammate
Before you invite anyone
The person needs an ARMANOS account of their own, signed up with the address you are about to type. Nothing here can prove that an address belongs to somebody, so the account has to exist first.
You also need a free seat. Seats come with the plan, the owner takes one of them, and a plan without team seats refuses the invite and says so.
Send the invite
Only an owner or an admin sees these controls. For everyone else the team screen is a list to read.
- 1
Open the team screen
The Team tab in the left column.
- 2
Press Invite member
The button above the list of members.
- 3
Type the address
The Email field in the Invite a teammate window.
- 4
Pick the role
The Role picker in the same window.
- 5
Press Send invite
The button at the bottom of that window.
Pass on the link
What comes back is a link and a short code, either of which lets the person join. You hand it over yourself, through whatever channel you already use with them.
Invites you made on this computer sit in a list below, and each one drops off when that person joins. Taking one off the list does not stop the link working.
An invite lives seven days
Five roles and their reach
The role is chosen at the invite and can be changed afterwards from the member's row.
Owner
Everything, and cannot be removed from the workspace.
Admin
Billing, the team, the history log, other people's profiles and devices.
Manager
Shared working things as well: folders and the proxy pool, to create, edit and delete.
Operator and Member
The profiles they were given, and nothing shared.
Seats and what fills them
The screen says how many of the plan's seats are taken, and the owner is one of them. A seat is counted when the invite is issued, not only when it is accepted, so an unanswered invite does not quietly oversell the plan.
Acceptance is settled in one locked step, so two people cannot both take the last seat at the same moment.
When someone leaves
Removing a member and a member leaving on their own end the same way. Shared access disappears in both directions, their devices are dropped, and any outstanding invite to that address is burnt.
Profiles they created after joining move to you. The ones they take away lose the pool proxy behind them, so your working addresses do not walk out of the door.
What this does not do
- It does not create an account for the person you invite. They sign up first, and only then can be invited.
- It does not add a seat. An invite with no free seat is refused rather than squeezed in.
- It does not let a removed person back in on an old invite. Invites to that address end with the membership.
Where this is decided
Each claim above is one place in the code and one stand.
- An invited person really joins, seats are counted, and a dismissed one cannot return on a spare invite
- apps/server/test/team-money-seats.js
- Leaving on your own is a real request made with the member's own token
- apps/web/test/уход-из-команды.ts
- The seat ceiling, the code and the seven day life of an invite live in one place
- apps/server/src/team/team.service.ts
- The role needed for a team action is compared by rank rather than by name
- apps/server/src/common/roles/roles.guard.ts
Questions
- The invite says there is no such account.
- The person has not signed up with that address yet. Ask them to register, then send the invite again.
- Can I invite myself with a second address?
- An invite to your own account is refused. A second account of yours would still need its own seat.
- Who can change roles?
- An owner or an admin. The owner role itself is never handed out from this window: it belongs to whoever created the workspace.
- What happens to their profiles when they go?
- Profiles made after they joined move to you. Access to shared profiles ends both ways, and it is an end of access rather than a deletion.
Try it with one colleague
The free plan gives two profiles, with no time limit and no card.