AmBot - administrator guide (coming soon)

Important

AmBot is coming soon: this guide describes a panel that will be introduced shortly.

Contents

  1. Switching it on
  2. Who can do what
  3. Agent access
  4. How messages are protected
  5. Files in the chat
  6. Log
  7. Check after switching on

User guide: AmBot.

Switching it on

Amphora switches AmBot on for an organisation. There is no setting for it in the Admin module - if you want to use AmBot, contact Amphora customer support.

When AmBot is on, every user of the organisation sees the AmBot button at the right of the top menu. Users of another organisation on the same server do not see it unless AmBot is switched on for them.

Who can do what

  • No separate right is needed to open AmBot and chat with it: every logged-in user of an organisation with AmBot on can do so. To chat with AmBot, the user connects their own Claude subscription.
  • To talk to other agents (bots), the user must be logged in with ID-card, Mobile-ID or Smart-ID; for messages to colleagues, GovSSO also works. Amphora takes the login method from the server's login record, never from the browser.
  • AmBot and the agents do only what the user's own rights allow. A user cannot give an agent a right they do not have.

Agent access

An agent acts on a user's behalf only when the user has given it access:

  • access is a selection of the user's own rights;
  • it lasts at most 90 days, and the user can revoke it at once at any time (Access -> Revoke);
  • Ask me before changes is on by default: every change comes to the user as a proposal first, and runs once, exactly as it was confirmed.

Which rights can be given to an agent is set by Amphora per right: some rights can never be given to an agent, some can, and some always go to the user as a proposal. This cannot be changed in the Admin module - contact Amphora customer support if needed.

Limits: up to 20 unconfirmed proposals per access; up to 5 unconfirmed access requests per agent and user.

How messages are protected

Messages to colleagues (People) Chats with AmBot and agents
In transit encrypted (TLS) encrypted (TLS)
End-to-end encrypted yes: encrypted and signed in the user's browser no (the agent has to read the message)
Stored in Amphora in encrypted form only as plain text
Signed by the sending device Amphora and the agent; a message that fails the check is marked
Kept 7 days until the user deletes them
Delete all People -> Delete all my messages the same button deletes their text too
Clear one conversation - Clear conversation deletes that conversation's messages; the log of the agent's actions stays

Amphora itself cannot read messages sent to colleagues. The sender's browser shows every new device of the recipient before the message is encrypted for it.

NB!

End-to-end encryption has limits worth knowing:

  • the server's administrator can add a device for a user; the sender sees it as a new device and the addition is tied to a login record, but it is not prevented;
  • if the server served changed page code, that code could read what the page decrypts;
  • the server sees who wrote to whom and when, but not the content.

Files in the chat

Files can be attached only in chats with AmBot, not to colleagues. Up to 5 files per message, each up to 10 MB; documents, images, signed containers and XML/AKT files. The file type is recognised by its content, not by its name.

Every file is checked for viruses. A file with malware, or one that could not be checked, is refused, and a file waiting for the check cannot be sent. Files that are not used are kept for 24 hours.

Log

Every action an agent takes on a user's behalf under an access is logged together with that access. The user sees these under the agent (What ... did).

Check after switching on

  1. A user of the organisation sees the AmBot button in the top menu.
  2. A user gives an agent "List tasks" and "Add tasks" for 1 hour and asks it to create a task: a proposal appears under Approvals, and no task is created until the user presses Confirm. After Revoke on that access, Amphora refuses the agent's requests on the user's behalf.
  3. Two users log in with ID-card, Mobile-ID or Smart-ID and open People -> each other's name: the chat header says "End-to-end encrypted". One writes: the panel shows the other's device, Send to these devices, and the other sees the message within seconds.
  4. A user logged in with a password sees "To write to colleagues, log in with ID-card, Mobile-ID or Smart-ID." in the People panel.
  5. A PDF attached in the chat first shows "Checking for viruses..." and then its size; the EICAR test file is refused.

Last modified: 13 October 2026, 15:49:15