هذه الصفحة غير متوفرة بلغتك بعد. أنت تقرأ النص الإنجليزي.
Solutions
Customer support
- 3 min, renewed while open
- Lock on an open profile
- 4 plus the owner
- Roles you hand out
- 3
- Tabs under Logs
- Pages opened
- What the daily counter measures
- 6 digits, 30 second step by default
- One-time code in the profile
One profile opens in one place
While you are signed in to ARMANOS and the server answers, it holds the lock on the profiles kept in that account. A second machine asking for such a profile is told the holder's machine name, since when, and whether it is your own other computer.
The lock runs for three minutes and is renewed while the window is open. A laptop that dies mid-shift therefore frees the profile by itself.
- 1
Close the window to hand over
Closing releases the lock at once, and the next operator opens the profile a second later.
- 2
Take it over on purpose
A takeover is a separate decision, and two takeovers racing each other cannot both win.
- 3
The previous holder is told
Their next renewal fails, their windows close and a notification names what happened.
The second step sits beside the sign-in
A profile can hold the one-time key of the account it signs into: the One-time code item in the profile menu.
The key stays on this computer and the digits are worked out here, so there is no phone in the middle and nothing to match by name among ten accounts that look alike.
No second device
The code appears where the profile lives, with the connection unplugged.
No hunting for the right entry
The key belongs to the profile, so the code on screen belongs to the account you are answering for.
A mark on the card
You see at a glance which client accounts no longer send anyone to a phone.
Who may open which client
Five roles exist and four of them are handed out. An operator works with the profiles given to them and changes nothing shared; a manager also keeps the proxy library and the groups; an admin gets billing, the team, the logs and other people's profiles.
Group access narrows what one person sees. The rule is read when profiles are listed and again when one is opened by its identifier, so knowing the number is not a way in.
| Role | Profiles given to them | Shared proxy library and groups | Billing, team and logs |
|---|---|---|---|
| Operator or member | نعم | – | – |
| Manager | نعم | نعم | – |
| Admin | نعم | نعم | نعم |
| Owner | نعم | نعم | نعم |
Invites
A person joins by an invite sent to an address that already has an account. The code is good for seven days and can be withdrawn while it is still unused.
The log answers the next morning
The Logs section has three tabs, in the dashboard and on the app's Members screen.
A row carries the email of the person who acted.
Only the owner and admins read it. For an operator the request is refused rather than merely hidden from the screen.
- Actions
- Every event in the workspace, newest first
- Profile sessions
- Browser starts and stops, with the profile named
- IP log
- The address, the country and the machine
- Every row carries
- The email of the person who acted
- One page
- 10 in the dashboard, 25 in the app
The three tabs, open to the owner and to admins.
What the counter on the card counts
Every profile card carries a daily Safe pace counter. It counts the pages opened in that profile today and sets them against a safe daily figure for its scenario.
In the grid view, in the Safe daily ceiling section, the scenario prints its own ceilings for the day beside it, buyer replies among them. Those are numbers to aim at, and the app neither sees a reply nor tallies one.
Measured
Pages opened in the profile today, per profile, cleared at midnight by this computer's clock.
Not measured
Buyer replies, listing edits, review requests and account switches.
At the top of the day
The bar turns amber and then red. Nothing closes and nothing is refused.
Where the numbers come from
The scenario record, ramped over the first seven days by profile age.
What this does not do
- It does not decide who may answer for a seller. The freelance platforms allow one active seller account per person and say who may act on it, and we will not sell a way around a written rule.
- A handover is closing the window rather than sharing a live session. A profile created before you signed in is not guarded by the server, and two machines will each open it locally. A failed lock renewal does not close the window.
- It does not tally buyer replies. The one thing measured is pages opened in the profile today, and the reply number beside it is guidance on a card.
- It does not move your response time. The platform scores that from the moment you actually answered.
How to check
Every claim above has a file behind it and a stand that fails when it stops being true.
- The second machine is told who holds the profile
- apps/server/src/profiles/profiles.service.ts · apps/server/test/profile-lock.js
- Groups decide what a member sees and what they may open
- apps/server/src/profiles/profiles.service.ts · apps/server/test/group-access.js
- The server refuses the log to an operator
- apps/server/src/logs/logs.controller.ts · apps/server/test/audit-filters.js
- The daily counter counts pages and stops nobody
- apps/desktop/src/lib/pace.js · apps/web/test/потолок-это-ориентир.js
- The one-time code matches the published vectors
- apps/desktop/src/lib/totp.js · apps/desktop/test/totp.js
Questions
- Can two operators sit in one account at once?
- Not while the profile is kept in the ARMANOS account, both machines are signed in and the server answers. The second machine is told who holds the profile and since when, instead of quietly opening a second session.
- What if a machine dies mid-shift?
- The lock expires by itself three minutes after the last renewal, and the next operator opens the profile with nobody unlocking it.
- Does the one-time key travel to a colleague?
- Not through us. It stays on the machine where it was pasted, and carrying it across is an export that asks first.
- Will our own support chat open inside a profile?
- Not if it is served from a host on the general tracker list, and one customer-messaging host is on it. Every profile loads that list.
- Who reads the workspace logs?
- The owner and admins. An operator is refused by the server, so the answer is the same whichever way they ask.
Three seats on Business
Business comes with three seats and five machines, and an extra seat is three dollars a month. Start free with two profiles and see how the lock fits your shift.