← Back to Support Center

Check workspace incident readiness

Review six evidence-backed setup signals and open the settings that own each gap.

GuideLast verified Open Markdown version
On this page

Before you start

Intended audience

Workspace administrators and settings managers preparing responders for the next incident.

Required permissions

You need workspace settings access.

Prerequisites

  • Access to a Tellagen workspace.
  • Access to the settings destinations that you need to update.

Procedure

Review readiness

  1. Step 1 of 8

    Open Incident readiness

    Open Settings. Select Incident readiness. On narrow screens, choose Readiness from the Settings navigation.

  2. Step 2 of 8

    Read the evidence boundary

    Read the note below the heading. Saved configuration is labelled Configured · not verified, separately from verified access, so a signal without current proof is never shown as ready.

  3. Step 3 of 8

    Review the six signals

    Review Slack and alert intake, Services and severity policy, Ownership and responder access, Local diagnosis tools, API-key access, and Customer-impact discovery.

    Workspace Incident readiness page with six setup cards, each with a status badge, a next step, and actions.
    These are example statuses. Your statuses change with the workspace evidence. Open full-size image(opens in a new tab)
  4. Step 4 of 8

    Interpret each status

    Use one decision tree. For Not configured, open the shown action and add the missing setup. For Configured · not verified, keep the saved setup and confirm it works in the tools your team uses; Tellagen has not proved it. For Verification unavailable, select View details and do not assume that the source works. Ready appears only when a source proves the signal works.

Resolve a gap

  1. Step 5 of 8

    Open the owning settings page

    Select the shown row action, such as Configure Slack, Open services, Review severity rules, Open members, Open teams, Open roles, Check local tools, Open API keys, or Configure customer impact.

  2. Step 6 of 8

    Inspect the evidence details

    Select View details. Review Known setup, Still to verify, Next action, and any Learn more link.

  3. Step 7 of 8

    Retry an unavailable signal

    When a row shows “Couldn’t load this signal. Other rows are still available.”, select Try again on that row.

  4. Step 8 of 8

    Handle a permission boundary

    When a row shows “You need workspace settings access to inspect this signal.”, ask a workspace settings administrator to review it.

You are done when…

You have six evidence-backed setup signals and a settings destination for each actionable gap. The page does not calculate a readiness score.

Troubleshooting

A configured provider still shows Configured · not verified.

Configuration alone does not prove OAuth scopes, live connectivity, or a successful customer lookup. Use the row's Still to verify note and exact settings action.

The page says Readiness signals couldn’t be loaded.

Select Try again. A partial failure keeps healthy rows available; a full error does not invent statuses until the sources load.

A row says No setup evidence is available yet.

Use the row's settings action to add the missing setup, then return to Incident readiness and review the updated source evidence.

The page shows no Open action for a row.

The source may be behind a permission boundary. Ask a workspace settings administrator to inspect that signal.

Related articles