सामग्री पर जाएँ

यह पृष्ठ अभी आपकी भाषा में उपलब्ध नहीं है। आप अंग्रेज़ी पाठ पढ़ रहे हैं।

Knowledge base

Invite a teammate

An invite puts another person into your workspace with a role that decides what they may touch. The path is Members in the left column (under Team), then Invite member. You do this when work has to be handed over without handing over your own sign in.

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. If the person has no account, the Create a login button next to the invite makes a login that belongs to the team: you set and reset its password yourself.

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 Members screen is a list to read.

For Admin and Manager, confirm with your password.

  1. 1

    Open the Members screen

    Members in the left column, under Team.

  2. 2

    Press Invite member

    The button above the list of members.

  3. 3

    Type the address

    The Email field in the Invite a teammate window.

  4. 4

    Pick the role

    The Role picker in the same window.

  5. 5

    Press Send invite

    The button at the bottom of that window.

The members screen: the owner row with a role badge, the seat count and the invite button above the list
The invite starts from the button above the list. The seat count stands next to it: one of three is taken.

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: groups and the proxy library, to create, edit and delete.

  • Operator and Member

    The profiles they were given, at the access level you chose, and nothing shared.

Seats and what fills them

You can see how many of the plan's seats are taken, and the owner holds one of them. A seat is counted when the invite is issued, not only when it is accepted, so an unanswered invite cannot hand the same seat to a second person.

Acceptance is settled in one locked step, so two people cannot both take the last seat at the same moment.

Profiles a person created before joining stay theirs: the team's profile allowance does not count them, they count against the person's own plan. If there are more of them than that plan allows, the extra ones will not open until the person upgrades or deletes some of them.

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. A team login cannot leave on its own, and when removed it is closed for good: nobody can sign in with it again.

Profiles they created after joining move to you. The ones they take away lose the proxy from the shared library behind them, so your working addresses do not walk out of the door.

One person in several teams

Someone who already belongs to another team, or runs one with people, can still accept: their own workspace stays theirs, and in yours they work in the role you picked. Nobody joins one workspace twice, and a person has up to 50 workspaces, their own included.

In the app the account's workspaces sit in the corner menu under Workspaces of this account, marked your own and now. Picking another reopens the app in it, with that workspace's own list of profiles. Signing in without a choice opens the default one: the new team for someone joining their first team, otherwise the previous workspace.

In the dashboard the workspace is picked in the Workspace row under the title, and the Default workspace card sits in the account settings.

The Account screen of the app shows the Workspace ID row with a Copy button, for support or an API request. A person leaves the workspace open for them, never their own, and the app then shows the list of where they now work. Removed, or left from another computer: the app open in that workspace says it is no longer available and shows no profiles from other workspaces.

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
A profile created before joining counts against the person's own plan, not the team's
apps/server/test/пространство-профиля.js
One person in several teams: their own team stays, seats and leaving count per workspace, the limit is 50
apps/server/test/несколько-команд.js
In the app every workspace has its own list, is picked from the corner menu, its ID copies, someone who leaves from the app lands where they now work, and someone who left from another computer sees a lock, not profiles of another workspace
apps/desktop/test/пространства-в-программе-живьём.js
In the dashboard picking a workspace changes the sign in and the profile list, and the default is saved on the server and leads the next sign in
apps/web/test/переключатель-пространств.js
After removal a change for the old workspace is refused, not saved elsewhere
apps/server/test/пропуск-ушедшего-пространства.js · apps/desktop/test/пропуск-без-пространства-клиент.js

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.