Organisation settings¶

This page shows what you can set on your organisation's Settings screen, who may do it, which limits the organisation above sets, and what to do when a value is refused. You find the screen under Organization management, Settings. The organisation's look has its own screen: Brand identity.

Who may do what¶

Anyone who may manage the organisation can read and change the screen, so an org-admin of the organisation (Manage roles). You see the screen only if you may change the settings.

The settings belong to the organisation itself. The Limits section does not: an administrator of the organisation above sets it. See Limits from the organisation above.

General¶

Time zone. The time zone in which times in prompts are read. Enter a name from the list, for example Europe/Amsterdam. An organisation starts on UTC.

Data retention¶

The period for recordings applies to every recording still there. If you shorten it, OS deletes the recordings that are older within an hour. A member can always delete their own recording sooner (Record a meeting with the note taker).

The organisation's usage (how much it has consumed) is always kept, however short you set the rest. How long exactly is decided by OS's operator, not the organisation.

Choose Save settings to save the general settings and the data retention together.

Helper model¶

Helper model is the model that makes a draft when someone describes what they need under Describe what you need, for instance a tool's parameters in the AI Toolbox as a JSON Schema. Choose a model from the list, or choose Follow the default to use the installation's default. Under the field you see which model is in use now and whether the organisation chose it or it is the default. With no model in use, Describe what you need is off.

Every draft is a paid model call of the organisation. A draft is used only once someone takes it and saves. You save the helper model with Save settings. When the organisation's administrators may not manage keys (see Limits), a new choice is refused.

Costs¶

Who sees costs and token usage decides who sees, on a run in the AI Toolbox, how many tokens it used and what it cost in euro:

• Nobody. Nobody sees costs or token usage. Every organisation starts here.
• Only the organization's administrators. Whoever may change these settings sees them; the other members do not.
• Everyone in the organization. Every member sees the cost of their own runs.

Whoever may change the settings may change this field too, an administrator of the organisation above included. Save the choice with Save settings. Someone who may not see costs does not get them from OS at all: they are not merely hidden on the screen. Only with the token their own browser uses at Artific Core can someone still look up their own usage there; OS does not show it.

Assistant editors¶

Whoever holds the role assistant-editor changes assistants: all of them, unless you narrow it. To let HR's editors change only HR's assistants, pick an attribute, such as department, and give each assistant the values of it it is for:

curl -s -X PATCH "$OS/api/v1/organisations/$ORG/settings" -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" -d '{"assistant_editor_attribute": "department"}'
curl -s -X PATCH "$OS/api/v1/organisations/$ORG/assistants/$AGENT" \
    -H "Authorization: Bearer $TOKEN" -H "If-Match: $ETAG" \
    -H "Content-Type: application/json" -d '{"editor_scope": ["HR"]}'

An editor with department: HR then changes the assistants labelled HR and those labelled everyone, and no others; she gives an assistant only her own values or everyone. A new assistant gets everyone. any is not a value of the picked attribute: OS refuses it. Picking another attribute keeps the assistants' values; values nobody holds any more reach only administrators. null lifts the choice.

Working from AI apps¶

A member can connect an AI app such as Claude Code, Claude Desktop or Cursor to OS and work with it under their own rights: look up members, make an assistant, change a group. The member signs in from the app to do so (how). An AI app always works with the rights of the person who connected it, never more. Under What AI apps may do in this organisation you choose what such an app can do in this organisation:

• Off. AI apps can do nothing in this organisation. Every organisation starts like this.
• Read only. An AI app may view what the person may see, but change nothing.
• Read and change. An AI app may do everything the person may, including inviting, changing and deleting.

Save the choice with Save settings. It applies to this organisation only, not to the organisations below it. If you turn it Off, OS refuses the next call of every connected app at once. The connections stay; turn it back on and they work again.

What the app's provider sees: the provider, such as Anthropic or Cursor, sees what the app reads, just as it sees what someone pastes into it. What an app changes is in the audit trail with the names of the person and the app.

Which members use an AI app. Under User management, Members, the AI app column shows which app a member last used in this organisation, and the AI app filter shows members with or without an app. Choose Disconnect AI apps in a member's menu to see that member's apps and disconnect one. That applies in this organisation only: in the member's other organisations the app keeps working. Whoever may change members can do this.

Your own agent as a service account. A program that speaks MCP itself can work with OS as a service account. On the service account's General tab, Use over MCP gives the MCP address, the Token address and how the agent fetches a token with the client ID and the secret of a key. A service account too has every call refused while this setting is Off.

Limits from the organisation above¶

The Limits section holds what the organisation above decides for this organisation:

• Monthly cap (euro). The most the organisation may spend per calendar month. Empty means no cap of its own. A cap can never be higher than the cap of the organisation above.
• The cap counts. This organisation alone, or this organisation and every one below it.
• Keep counting what an erased organization used. What an organisation below this one used keeps counting towards the cap after that organisation is erased.
• Administrators of this organization may not. See the usage of the organisation, see the audit trail, manage keys. A checkmark takes that right away from the organisation's administrators.

For the organisation itself these fields are read-only, with a notice that the organisation above decides them. Only an administrator of the organisation above, with scope descendants (Manage roles), can change them, on the Settings screen of the organisation below it. The organisation at the top of the tree has none above it: OS's operator sets its limits. Choose Save limits to save the limits.

When a value is refused¶

A field that is not right gets a message at the field and nothing is saved. This happens, for example, with a time zone that does not exist, a number of days outside the allowed range, an amount that is not an amount. Correct the field and save again. If saving fails for another reason, you see the message that the settings could not be saved; try again.

Two administrators can change different fields at the same time: both keep their change. If they change the same field, the later one wins.

Every change is written to the audit trail, with who changed it and from which organisation, but without the value.