Skip to main content

AI Settings

The page-admin AI screen stores the page-scoped provider configuration used for assisted workflows.

This is separate from Slack app credentials and separate from organization-wide admin authentication.

This guide is based on application/frontend/src/pages/admin/AISettings.jsx.

What the AI screen manages

The current screen is intentionally narrow. It manages:

  • which provider the page uses
  • an optional model override
  • an optional base URL for compatible providers
  • the encrypted API key for that page

The configuration is page-scoped, so different status pages can use different AI providers or keep AI disabled entirely.

Supported providers

The current provider choices are:

  • Anthropic
  • OpenAI
  • OpenAI-Compatible

When OpenAI-Compatible is selected, the Base URL field becomes required.

For other providers, the base URL field is hidden and the default provider endpoint is used.

Save, rotate, and clear behavior

The current form supports three common workflows:

  1. create a new AI configuration
  2. rotate only the API key
  3. clear the saved AI configuration entirely

A few details matter operationally:

  • the API key is never re-shown after save
  • leaving the API-key field blank keeps the existing saved key
  • changing providers should normally be paired with a new API key
  • stored keys are described in the UI as encrypted at rest

Where AI is used today

The current screen describes AI as being used for assisted workflows, and the page text calls out Slack incident drafting specifically.

That means the AI provider lives here, while the Slack page still controls things such as:

  • app connection
  • channel behavior
  • reminder settings
  • workflow confirmation mode for AI-thread initiated actions

Practical guidance

Good defaults usually mean:

  1. keep the provider page-scoped so experiments do not affect every workspace
  2. use the provider default model first unless you have a specific reason to override it
  3. document which page owns the API key and when it should be rotated
note

The current AI screen is a provider-configuration surface, not a full prompt-management workspace. It enables assisted workflows that exist elsewhere in the product.