Integrationincident.io integrationAvailable

See who's carrying the duty.

See who is carrying the duty, not just who is on the team.

  • Map incident.io users to employees, automatically or by hand.
  • Effective on-call duties sync into the people workspace.
  • Incident response stays in incident.io; Perelan adds context.

Verified integration behavior only. External tools remain their own systems of record where applicable.

Book a demoSee the flow
Runtime path
  1. 01Connect credential
  2. 02Import users
  3. 03Map employees
  4. 04Sync duties

Operational flow

How the connection works in Perelan

Start with identity and setup, then follow the data direction, permission check, source record, and fallback state.

01

Connect with a controlled credential

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

Plan integration rollout
02

Map identities deliberately

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

03

Synchronize effective duties

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

04

Keep incident response in incident.io

This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.

Runtime path

  1. Connect credential
  2. Import users
  3. Map employees
  4. Sync duties
  5. Show duty context

Relevant product paths

Plan integration rolloutCore HRtechnologyit operationsSecurity

Controls and boundaries

Can Perelan import incident.io users?

Yes. The integration can read users for mapping when connected.

Can we map users manually?

Yes. Explicit mapping is supported for unresolved identities.

Does it replace incident.io?

No. Perelan surfaces people-context from incident.io; incident response remains in incident.io.

Who can configure the integration?

Configuration is an owner/admin-style integration setup path.

Does this bypass Perelan permissions?

No. The marketing examples are compressed, but the product path still checks the acting user, role, group scope, and domain permission before data is shown or changed.

Is the page showing real customer data?

No. The product demonstrations use fictional names, roles, dates, and values so the workflow is clear without exposing real people or companies.