For Organisation Administrators: licensed Collaborators with the relevant organisation-wide permissions.
What you will achieve
Choose how the organisation uses AI, configure the available provider and separately set the route for Advisory Reports.
A successful connection check confirms a connection at that moment. It does not approve the provider for sensitive information or establish the quality of an analysis.
Before you start
Agree the permitted data, provider, budget and responsible owner. Obtain any API key through your approved secret-sharing process, not a ticket or shared document. Confirm you are in the correct organisation.
Review the current settings before changing them. Test Connection can save unsaved settings before testing, so treat it as a potentially organisation-wide change.
Choose the AI mode
- Open Settings > Organisation > AI.
- Review AI Mode: - Disabled turns the general AI mode off. - Bring Your Own Key uses your organisation's provider configuration and provider billing. - Platform Credits uses Backstory's metered credit pool.
- For Bring Your Own Key, choose a provider from the available list. Enter the required key privately. For Azure, also supply the Azure Endpoint and Deployment Name; use your actual approved deployment, not the example placeholder.
- Complete any other fields shown for the chosen provider. Ollama refers to the platform-configured server; this form is not a way to register any arbitrary local endpoint.
- Review the feature switches. Enable only the AI uses approved for this organisation.
Set the Advisory Report route
- Review Advisory report AI route separately from the general mode.
- Choose Platform AI credits, eligible Organisation BYOK, or Disabled.
- Organisation BYOK for Advisory Reports requires OpenAI or Azure OpenAI in the reviewed interface. A different provider working for another feature does not make it eligible for reports.
- Check that both the general mode and the report route express your intention. Do not assume changing one automatically disables the other.
Check it worked
Select Save AI Settings, wait for a successful result and reload the page. Confirm the saved mode, provider, feature switches and report route before selecting Test Connection where available.
Do not interpret the masked saved-key indicator as an editable copy of the secret. Leaving a key field empty is not a documented key-revocation procedure.
After the connection succeeds, run one approved, non-sensitive sample task. Review its result and, where relevant, credit usage. Purchasing credits or enabling automatic purchases is a separate financial decision.
If something goes wrong
| Problem | Next action |
|---|---|
| Connection fails | Check saved provider configuration and the returned error; do not paste the key into support |
| Advisory BYOK is unavailable | Check the selected provider and mode |
| Analysis is blocked despite connectivity | Check feature availability, task permissions, input requirements and credit state |
| An unwanted setting was saved during testing | Restore the agreed setting, save and reload; assess whether any work ran meanwhile |
Human judgement matters
AI output is a proposal to review against its sources. Provider configuration is not approval to send every document to that provider. Never include credential fields in screenshots.
What next?
For the wider context, see Configure security, data and AI settings.
Ask a licensed Collaborator to try the approved policy-analysis task and confirm that the route and review expectations are understood.
Get help
Contact your organisation's support route with this guide reference, the affected page and a sanitised error. Do not include passwords, keys or session details.