Skip to main content

AI Settings

The AI screen lets page admins choose which AI provider StatiBeat should use for assisted workflows.

AI settings are page-specific. One status page can use AI while another keeps it disabled, and each page can use its own provider configuration when needed.

When you need this page​

Configure AI settings when you want to use features such as:

  • Slack incident drafting
  • Beat AI Info investigations
  • AI-assisted Beat creation
  • AI-assisted hierarchy creation

AI-assisted create flows are confirmation-first. StatiBeat shows a preview, asks for confirmation, and only writes after a human approves the plan.

Provider options​

The AI screen can include these provider choices:

  • Platform Provided
  • Anthropic
  • OpenAI
  • OpenAI-Compatible

Choose Platform Provided when your workspace offers StatiBeat-managed AI and you do not want to store your own provider key on the page.

Choose a bring-your-own-key provider when your team needs its own provider account, billing boundary, or model policy.

For OpenAI-Compatible, provide the base URL for your compatible endpoint. For the other providers, StatiBeat uses the standard provider endpoint unless your workspace is configured differently.

Saving and rotating keys​

Use the AI settings form to:

  1. enable StatiBeat-managed AI, when available
  2. save or rotate a bring-your-own-key provider
  3. clear the saved AI configuration

The saved API key is not shown again after it is stored. If you leave the key field blank while editing existing settings, StatiBeat keeps the saved key. When changing providers, rotate the key at the same time unless you have a clear reason not to.

How AI settings relate to Slack​

Slack connection settings and AI provider settings are separate.

  • The Slack App page controls connection, channels, reminders, and Slack workflow behavior.
  • The AI page controls the provider used by assisted workflows.

That means you can connect Slack without enabling AI, or enable AI for non-Slack workflows.

Practical guidance​

Good defaults usually look like this:

  1. Use Platform Provided when your workspace offers it and you want the simplest setup.
  2. Use a bring-your-own-key provider when your organization needs direct provider ownership.
  3. Start with the provider default model unless your team has a tested reason to override it.
  4. Document who owns the key and when it should be rotated.