Set up your first workspace

This walkthrough uses a production database service as an example. Use your own service and agent names.

1. Choose your organisation timezoneCopy Anchor Link

1. Open your profile menu and choose Settings.
2. Open Organization as an organisation administrator.
3. Select the timezone your team uses, for example Europe/Vienna.
4. Save the change.

Displayed dates, vacation days, schedule inputs, and report day boundaries use the organisation timezone. Set it before planning coverage. See Settings.

2. Add respondersCopy Anchor Link

Open Agents, create the people who will respond, and enter their names and email addresses. Creation opens the agent’s edit page. You do not choose an initial password in this form.

Record planned vacation on the agent’s detail page before building a rotation. See Agents and Vacations and overrides.

3. Create an on-call scheduleCopy Anchor Link

Open Schedules → Overview, choose Create schedule, and enter:

• A recognisable name, such as Platform primary.
• A rotation start date and local handoff time.
• A handoff frequency, for example weekly.
• The agents, in the order they should rotate.

Review the coverage preview and save. A schedule that starts in the future is not yet covering the current time. See Schedules.

4. Define an escalation policyCopy Anchor Link

Create a policy with your schedule in the first level and a backup agent or schedule in a later level. Set the response window and any repeats, then save. See Escalation policies.

These settings describe the intended routing. They do not start sending notifications while the notification engine is pending.

5. Create the monitored serviceCopy Anchor Link

Open Services, create Production database, and select the policy. Enable deduplication and choose a window appropriate for your monitoring frequency, for example 120 seconds.

Save and copy the permanent public service ID from the edit page. See Services.

6. Connect a monitoring checkCopy Anchor Link

An organisation administrator creates credentials in Settings → Organization, in the API credentials section. Store the secret when it is shown.

Follow the first API request using those credentials and the service’s public ID. Do not send a numeric service ID.

7. Verify the complete resultCopy Anchor Link

1. Confirm that the API returned an INC-... identifier.
2. Open Incidents and find the new incident.
3. Repeat the request within the deduplication window and check that it adds an alert to the same incident.
4. Acknowledge the incident, add an investigation comment, and resolve it.
5. Check the timeline and Reports.

This verifies ingestion and the incident workflow. It does not verify outgoing notifications, which are not active yet.