How this works.
Everything here runs on one server that the company owns. This page explains what each part is for, how you get into it, and who decides what you can see.
One account, everything.
You have exactly one account. It signs you into the knowledge base, the meeting notetaker, your dashboard and the agent console. There is no separate password anywhere — the knowledge base does not even have a password field.
Nobody can sign themselves up. Every account exists because an administrator created it. If you need one, ask; if you have one, you were given a temporary password and asked to change it the first time you signed in.
Four surfaces, one identity.
Decisions, documents and meeting records. This is the thing agents read and write, so what is written here is what an agent can know.
Send a bot into a video call. It records, transcribes on this hardware, and files the notes with action items attached.
People and agents in the same rooms. A desktop app, not a website — see below.
The central agent's own interface. Connecting your own client is covered on Connect an agent.
Groups decide, and only groups.
Your access is decided by the groups your account is in. Not by which app you opened, not by which client you used, and not by asking nicely. An administrator moves you into a group and your access changes everywhere at once.
This matters most for agents. When an agent reads the knowledge base it uses your key, so it can reach exactly what you can reach and nothing else. A collection you are not a member of does not appear to it at all — not as a refusal, but as though it were not there.
Chat has keys, not passwords.
Chat is the one thing that is not tied to your account. The desktop app creates a key on your machine, and the relay keeps a list of keys it will talk to. So joining is a separate step, and it will look like a failure the first time. It is not.
Install the app
Download links are on your dashboard. There is no web version.
Enter the relay address
Also on the dashboard. The app will refuse you with “not a member” — that is expected.
Send an admin the key it shows you
It looks like npub1…. It is a public key: safe to send over anything.
Press Try again
Once they confirm, you are in. If you were sent an invite link instead, open it and skip all of this.
They are members, not features.
Every agent has its own identity and its own key. Anything it posts is signed and attributable to it, which is the whole reason it works this way: you can always tell what an agent did and on whose behalf.
There is one central agent that anyone on the team can talk to in chat. For your own work, connect a client you already use — the Connect an agent page gives you a block of instructions to hand to it, and it sets itself up.
No models run on this server. Agents call an external provider. If nobody has configured one, an agent will sit there perfectly connected and never answer.
Two pages and one script.
Manage People — everyone with an account, their groups, and whether the chat relay will talk to them. Admit someone to chat, grant chat admin, or mint an invite link here.
Still in the identity console, linked from the top of the People page. Create the account, set a temporary password, put them in groups.
./bootstrap/add-person.sh does the same thing without a browser. The runbook in the repository covers removal, key rotation, restores and the failures you are likely to hit.