Deze pagina is nog niet in uw taal. U leest de Engelse tekst.
Knowledge base
See where you are signed in and end a session
What a line tells you
A line names the ARMANOS app with the computer name, a browser with its system, or a server signed in with an API key. Below it are the system and the app version, the IP address, when the sign-in happened and when the device was last active.
The country stands next to the IP only when our network provider reports it. Otherwise the line shows the IP alone, and we do not guess a city.
Your own device is first and marked This device. A device seen for the first time is marked New device for seven days.
End one session or all the others
Each line except your own has End session. Below the list, End all other sessions closes every line but yours. Both ask for your password, and for the code from the authenticator app if two-step sign-in is on.
- 1
Open the Account screen
Or your account page on the site.
- 2
Find the line under Where you are signed in
Press End session, or End all other sessions below the list.
- 3
Enter your password
And the code from the app, then press End session.
Team changes after a stolen sign-in
Right after End all other sessions and after a password change, the owner and the admins of a team see a review of the last 14 days: new people with who invited them and from which device and address, unaccepted invitations, role changes (what it was and what it is now), new API keys with whose key it is, its rights and when it was last used, and profiles opened to people in the team. In the app the review is on the Account screen under Where you are signed in, on the site it is on the account page.
Each line has a button: Remove from team, Revoke invitation, Revoke key or Close access. The review itself changes nothing: you decide.
A revoked key stops working right away. The review stays on the screen until you press Hide review.
It is there because a new password closes only the stolen sign-in. A person invited with that sign-in, and an API key they created with their own password, stay until you remove them here. So does an unaccepted invitation.
The review shows the team you are in now. If another of your teams also changed, the review names it in a separate line with how many changes of each kind it has. Switch to that team and check the people and invitations under Team and the keys under Team API keys on the site.
Managers, operators and members do not see the review. A server updated before this version does not give it, and the app and the site work as before.
What happens on that computer
The app there learns within a minute if profiles are open, and within five minutes if none are. It closes the open profiles without asking and shows You were signed out on this computer with the reason.
Profile data stays on that disk. The profiles open again only after someone signs in to the same account there, and the sync folder neither gets nor gives anything until then. After that sign-in, what waited in the profiles goes to the folder by itself.
The device seat of that computer is freed. A computer without a connection learns about the end only when it is back online. An earlier version of the app keeps open profiles running until someone closes them, but it can no longer save anything to your account.
Password change and two-step sign-in
Changing the password signs out every other device at once and revokes your API keys, and the device you changed it on stays signed in. In the app, Change password is under Change email on the Account screen.
Turning on two-step sign-in also signs out every other device, and profiles open there close. It does not revoke API keys: a key lives until you revoke it under API keys or change your password, as with large services. That is why a new key is issued only after you enter your password and the two-step code again, and the app on your other computers shows “An API key was created” in the bell.
A sign-in from a new device
The app on your other computers shows New sign-in to your account in the bell, with Show sessions. Once our mail service is on, each sign-in from a new device also sends an email to your address.
A browser in a private window from your usual address is not a new device. A new address together with a new browser is.
Sessions of team logins
The team owner sees and ends the sessions of logins that belong to the team, and an administrator those of logins with a lower role, with Sessions next to such a login. A person with their own account manages their sessions alone.
If the site is open on that computer too
Signing in to the app through the site does not ask for the password again. So end the line of the browser on that computer as well, or simply press End all other sessions.
What this does not do
- It does not show a city, and the country only when our network provider reports it.
- It does not erase profile data on the ended computer. The data stays and opens again after a sign-in to the same account.
- It does not end the API key itself. To close a server line for good, revoke the key under API.
- It does not remove webhooks: ending sessions, a password change and two-step sign-in leave them as they are, because a webhook belongs to the workspace. The list of webhooks is in the Dashboard on the API keys tab, and a new one is added only after you enter your password again.
Where this is decided
Each line is a file you can open.
- Sessions, ending one or all others, and the seat of the machine
- apps/server/src/auth/сеансы.service.ts · apps/server/test/сеансы.js
- The password change keeps this device, ends the others and revokes API keys
- apps/server/test/смена-пароля-выход-везде.js
- The ended computer closes profiles, holds the folder and opens after a sign-in
- apps/desktop/test/вход-завершён-с-другой-машины-живьём.js
- The list and the end of a session in the app and on the site
- apps/desktop/test/сеансы-в-окне-живьём.js · apps/web/test/сеансы-кабинет.js
- The review of team and key changes after End all other sessions and a password change, with its buttons
- apps/server/src/team/обзор-команды.ts · apps/desktop/test/новый-участник-и-обзор-в-окне-живьём.js · apps/web/test/ключи-команды-и-обзор-кабинет-живьём.js
- A sign-in code taken before an end, and a sign-in started with the old password, open no session afterwards
- apps/server/src/auth/auth.service.ts · apps/server/test/выданное-до-завершения.js
Questions
- Why does a line say Signed in before the server update?
- That sign-in was made before the server learned to keep sessions, so its time is unknown. Such lines appear when they next reach the server, and End all other sessions closes them too.
- I ended my own computer by mistake. Is my work lost?
- No. The profiles stay on the disk. Sign in there to the same account, and the profiles open again and what waited goes to the sync folder.
- Can someone with my password end my sessions?
- Yes, and that is why the line advises changing the password. A new password ends their session too, and a sign-in code it took before stops working with it. With two-step sign-in they also need your code.