Organization settings
Organisation-wide configuration. Found under Organization management → Settings.
Basics
Name
Your organisation's display name, shown throughout the platform.
Default user groups
Groups that new self-registered users are added to automatically. Only applies to people who did not already have an account.
Self-signup allowlist
Which e-mail addresses may register themselves. Wildcards are allowed, for example *@your-domain.com.
Allowed login methods
Which sign-in methods people in your organisation may use. At least one must be enabled.
Self-registration
The allowlist and default groups work together. The allowlist decides who may create an account; the default groups decide what they can do once they have.
Leave the allowlist empty if you would rather create accounts yourself. See Users.
Self-registration requires a custom domain for your organisation. Your account manager can arrange that.
Login methods
Choose which sign-in methods your organisation accepts. Restricting to a single method is the simplest way to ensure everyone arrives through your own identity controls.
A user who tries a method you have disabled is told the method is not allowed for this organisation.
Data retention
Controls how long conversation history and generated content are kept.
Automatically delete AI Assistant messages
Removes chat messages older than a set number of days. Runs daily.
Automatically delete AI Toolbox responses
Removes saved Toolbox output older than a set number of days.
Keep statistics when deleting
Redacts the content but keeps the counts, so reporting still works.
Both retention settings are off until you switch them on, and each asks for a number of days.
Keep statistics when deleting is worth leaving on. With it, you keep usage figures in Reports while the content itself is removed. Without it, the whole record goes and your historical reporting shrinks as retention runs.
Users cannot see or change retention. If someone asks why their old chats have disappeared, this is why.
Advanced settings
The Advanced settings panel holds external authentication configuration, for organisations that authenticate users through their own system before they reach the platform.
Authentication endpoint
Where the platform verifies a token.
ID response field
Where to find the user identifier in that response.
Token prefix
The prefix used in the authorisation header.
Filling in either of the last two makes the endpoint required. This is normally set up with your account manager rather than configured cold.
Saving
Save settings applies everything on the page.
Last updated
Was this helpful?