How to use these runbooks

Use these pages as step-by-step browser runbooks, not engineering notes.

Before you change anything

1. Confirm the customer name and organization.
2. Confirm the request came from an authorized customer contact.
3. Open the relevant Jericho admin page in a browser.
4. Read the whole runbook once before making changes.
5. Stop if the page you see does not match the screenshot or expected labels.

Page pattern

Most runbooks use this structure:

1. When to use this — the support scenario.
2. Before you begin — required access and facts.
3. Steps — exact browser actions.
4. Expected result — how to verify success.
5. If this fails — common fixes.
6. Escalate when — handoff criteria.

What not to do

• Do not guess between similar customer tenants.
• Do not copy settings from one customer into another customer.
• Do not expose API tokens in screenshots or tickets.
• Do not use browser devtools, console commands, terminal commands, GitHub, logs, database access, feature flag tooling, or code inspection. If a task needs those, escalate to Jericho engineering.