Skip to main content
Checks that offboarded employees no longer have active PagerDuty access.

​
About

When you connect PagerDuty to DSALTA, the platform syncs your account users (email and role) using read-only API access. DSALTA matches each user with active PagerDuty access to your People directory by email. If a matched person is offboarded (terminated or in offboarding) but still has active access, the check flags it as a serious issue. DSALTA evaluates this control on every sync.

​
Why This Matters

When someone leaves and their access is not revoked, their credentials become an unmonitored door into your systems — a common cause of data theft and accidental damage. For an incident-management tool like PagerDuty, that can also mean lingering visibility into on-call schedules and services. Timely access removal on termination is explicitly required by SOC 2, ISO 27001, HIPAA, and GDPR.

​
How to Fix

Before you begin
  • Identify all offboarded employees by cross-referencing your HRMS (or the DSALTA People module) with active PagerDuty accounts.
  • Have admin or owner access to your PagerDuty account.
Remove access for offboarded users
  1. In PagerDuty, go to People → Users and remove any users who have been offboarded.
  2. In DSALTA, go to People and confirm offboarded employees are marked terminated.
  3. To automate this going forward, connect your HRMS to DSALTA so that an “Offboarded” status automatically flags any lingering access.
Once offboarded employees no longer have active PagerDuty access, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the PagerDuty integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in PagerDuty.