# Check workspace incident readiness

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

## 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

<a id="phase-review-readiness"></a>

### Review readiness

<a id="step-open-incident-readiness"></a>

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

<a id="step-read-the-evidence-boundary"></a>

2. **Read the evidence boundary.** Read the note below the heading. A signal without current proof stays Unknown / Unavailable.

<a id="step-review-the-six-signals"></a>

3. **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 evidence-backed setup rows, status badges, and settings actions.](https://tellagen.com/help/assets/incident-readiness-register.webp)

These are example statuses. Your statuses change with the workspace evidence.

<a id="step-interpret-each-status"></a>

4. **Interpret each status.** Use one decision tree. For Ready, keep the current setup and review its evidence. For Needs attention, open the shown action and resolve the failed requirement. For Unknown / Unavailable, select View details and do not assume that the source works.

<a id="phase-resolve-a-gap"></a>

### Resolve a gap

<a id="step-open-the-owning-settings-page"></a>

5. **Open the owning settings page.** Select the shown row action, such as Open integrations, Open services, Open severity index, Open members, Open teams, Open roles, Open investigation tools, or Open API keys.

<a id="step-inspect-the-evidence-details"></a>

6. **Inspect the evidence details.** Select View details. Review Observed, Not proved, Next action, and any Learn more link.

<a id="step-retry-an-unavailable-signal"></a>

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

<a id="step-handle-a-permission-boundary"></a>

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 id="troubleshooting-a-configured-provider-is-still-unknown-unavailable"></a>

### A configured provider is still Unknown / Unavailable.

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

<a id="troubleshooting-the-page-says-readiness-signals-couldn-t-be-loaded"></a>

### 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 id="troubleshooting-a-row-says-no-setup-evidence-is-available-yet"></a>

### 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.

<a id="troubleshooting-the-page-shows-no-open-action-for-a-row"></a>

### 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

- **Recommended next task:** [Manage workspace API keys](https://tellagen.com/help/manage-api-keys)
- [Configure a supported integration](https://tellagen.com/help/configure-integrations)
- [Run a local Diagnosis for an incident](https://tellagen.com/help/run-local-diagnosis)
- [Assess customer impact for an incident](https://tellagen.com/help/assess-customer-impact)


## Continue through the incident lifecycle

- **Previous task:** [Configure a supported integration](https://tellagen.com/help/configure-integrations)
- **Next task:** [Use the public API reference](https://tellagen.com/help/use-public-api-reference)
- [Back to Support Center](https://tellagen.com/help#help-search)

## Last verified date

2026-08-29