Integrations

BYOAI (Bring Your Own AI)

Connect your workspace's OpenAI or Cloudflare account and choose when Sorena-managed credentials can be used.

BYOAI (Bring Your Own AI) lets your workspace use its own OpenAI or Cloudflare credentials. Credentials are the API keys and account details that give Sorena permission to use that provider on your behalf.

Open Workspace > Integrations and find AI providers. Check the selected workspace before changing anything. Ask your workspace owner or IT administrator for help if you do not manage your organization's provider account.

Required roles and licenses

The workspace needs the Platform and Enterprise BYOAI licenses. Workspace Readers and higher can read the available provider status. Workspace Admins and Owners can configure providers. Saved keys are not shown in the status view.

Your profile instructions describe your role and preferences. Research AI settings control a conversation's tools and responses. Neither chooses the workspace's provider credentials.

For service tier and data residency, follow OpenAI processing settings. Those preferences also apply when Sorena manages the API key and require the Platform license.

Manage workspace AI providers

Each provider card shows whether it uses System Default (Sorena-managed credentials) or Workspace Config (your workspace's credentials), and whether workspace keys have been provided. The available cards include OpenAI and Cloudflare.

AI provider cards for OpenAI Platform and Cloudflare AI showing System Default and Workspace Keys: Not Provided.
Check whether each AI provider uses workspace credentials or Sorena's default connection.

Configure and test credentials

  1. Select Edit on the intended provider.
  2. Complete the fields offered. OpenAI requires its API key. Cloudflare requires its API key and account ID.
  3. Select Test Connection and read the result. Resolve any reported problem before continuing.
  4. Select Save, then check the provider card.
  5. Select Enable Workspace Config when you are ready to use the saved credentials.

Enter credentials only in the credential form. Close hides the editor without saving. After a change, check the success message and Using badge to confirm which credentials are selected.

Activate, disable, or delete a configuration

ControlEffect
Enable Workspace ConfigActivates the workspace's saved configuration. Configure the provider first.
Disable Workspace ConfigStops using that workspace configuration after the deactivation dialog. Saved credentials remain until deleted.
Enable Fallback / Disable FallbackAllows or prevents use of Sorena-managed credentials when that provider's workspace configuration cannot be used.
Use System DefaultDisables workspace configuration and enables use of system credentials through the confirmation dialog.
Delete ConfigDeletes the saved workspace keys and configuration for that provider. You must supply them again to restore that configuration.

Activation and fallback buttons apply their changes immediately. Delete Config also deletes the saved configuration immediately. Check the workspace and provider before selecting these controls.

Use Sorena-managed credentials as fallback

Fallback lets Sorena use its own credentials for the selected provider when the workspace configuration cannot be used. It keeps the same provider: OpenAI fallback still uses OpenAI, and Cloudflare fallback still uses Cloudflare. Using: System Default means Sorena-managed credentials are selected; Using: Workspace Config means the workspace's active configuration is selected.

Before disabling fallback, save valid workspace credentials and activate the provider. Sorena rejects the change if credentials are missing or the configuration is inactive. With fallback disabled, the affected AI service can be unavailable if the workspace configuration cannot be used.

To return to Sorena-managed credentials, choose Use System Default, review the reason in the dialog, and select Save. This enables fallback and deactivates the workspace configuration. Use Delete Config separately when you intend to remove its saved credentials.

If a provider change fails

Read the message and verify the selected workspace, saved configuration, and your access before retrying. Ask a workspace owner if the provider section or editing controls are missing. If a connection test fails, check the credential fields with the person who manages the provider account.

Review available configuration changes in workspace activity. If the provider still cannot recover, contact support with the affected provider and time. Keep API keys and other credentials out of support messages and screenshots.

For GitHub or sign-in providers, see Integrations.

Screenshots show a demo workspace.

On this page