AI assistant administration
Add your Anthropic API key, grant people access to the assistant, and set the token and daily interaction limits.
The AI assistant needs two things before a person can use it: an API key for the workspace, and an allowance for that person. This page tells you how to supply both.
You must be a workspace administrator. Open Administration, then open the AI Assistant tab.
Add the API key
The assistant uses your own Anthropic API key. Orkyo does not supply one.
- Get an API key from your Anthropic account.
- Put the key into the Anthropic API key field.
- Select Save.
- Select Test connection.
Test connection speaks to Anthropic and uses no tokens. It tells you if the key is wrong or if the network is unavailable.
Orkyo encrypts the key before it stores it. The encryption is specific to your workspace, so the stored value cannot be read in a different workspace. After you save the key, Orkyo shows only the last four characters. Nobody can read the key back out of Orkyo, and it never goes to a browser.
To use a different key, put the new key into the field and select Save. The new key replaces the old one.
Remove the API key
Select Remove. The assistant stops immediately for every person in the workspace. This is the fastest way to stop all assistant use.
Give a person access
Only administrators can use the assistant without an allowance. Every other person must get one.
- Find the person in the Who can use it list.
- Put a number into the token field, or leave the field empty for no limit.
- Select Grant.
The list shows every person in the workspace. A person without an allowance shows No access.
Set a monthly token limit
The number in the token field is the maximum tokens that the person can use in one calendar month. Anthropic bills these tokens to your key.
| Value | Result |
|---|---|
A number, for example 50000 |
The person can use up to that many tokens each month |
| Empty | The person has no limit |
0 |
The person cannot use the assistant, but keeps the allowance |
Use 0 to stop one person for a short time. Use Remove access to end their access
completely.
The count returns to zero at the start of each calendar month. Orkyo does not carry unused tokens into the next month.
Set the daily limits
The Daily limits section holds two limits. They count interactions, and not tokens, which makes them different from the token allowance.
| Limit | What it counts |
|---|---|
| Interactions per person each day | The interactions of one person |
| Interactions for the whole workspace each day | The interactions of everybody together |
- Put a number into a field, or leave the field empty for no limit.
- Select Save limits.
The smallest value is 1. The 0 that stops one person in the token table above is not
permitted here. To stop a person completely, remove their access.
These limits apply to administrators too. The token allowance does not, because an administrator can replace the key that the tokens are billed to.
A new workspace has no daily limit. Most workspaces need none, because the token allowance is enough when each person signs in with their own account.
These limits are useful when many people use the same account, for example a demonstration workspace. Orkyo counts each session separately on that kind of account, so one visitor cannot use the interactions of the next.
Set both limits on an account that many people use. A person who signs in again gets a new session, and with it a new count. The limit for each person therefore makes a shared account slower, but does not stop it. The limit for the whole workspace is the limit that holds.
The counts start again at the start of each day, in UTC. When a person reaches the personal limit, the assistant stops for that person, and the other people keep their own counts. When the workspace reaches the second limit, the assistant stops for everybody until the next day.
The assistant panel shows the limit that stops the person first, and it says when that limit is the workspace limit. Each person can therefore see how many interactions are left before the assistant stops.
Read the usage
Each row shows the tokens that the person used this month, and how many conversations they had. Use these numbers to set a limit that matches how people work.
A conversation can use many tokens, because the assistant reads workspace data to answer. Start with a limit that is generous, then reduce it when you know the usual usage.
Data that goes to Anthropic
When a person uses the assistant, these things go to Anthropic:
- The messages that the person writes
- The workspace data that the assistant reads to answer, for example request names, times, and conflict messages
This happens under your own agreement with Anthropic, because the key is yours.
Tell your people what the assistant sends before you give them access.
Security
- The assistant reads data. It cannot change data.
- A change happens only when a person approves it, and Orkyo then applies it with that person’s own permissions.
- The assistant reads only what the person can already see.
- The assistant can open a page for the person. This changes the screen, and not the data. The page itself keeps its own permission checks.
- Orkyo saves the conversations of each person separately. One person cannot read the conversations of a different person. Orkyo keeps the 20 most recent for each person.
- Orkyo records in the audit log when an administrator changes the key, an allowance, or the daily limits. The log never contains the key.