Skip to main content
Checks that offboarded employees no longer retain active Heroku access.

​
About

When you connect Heroku to DSALTA, the platform syncs your Heroku access using read-only API access. On every sync DSALTA compares your Heroku account owner, team members, and app collaborators against your People page and flags anyone with active access whose employee record is terminated or offboarding.

​
Why This Matters

When someone leaves and their access is not revoked, their account becomes an unmonitored door into your systems — a common cause of data leakage and accidental damage. Timely access removal on termination is explicitly required by SOC 2, ISO 27001, and GDPR.

​
How to Fix

Before you begin
  • Identify offboarded employees by cross-referencing your HRMS (or the DSALTA People module) with everyone who has active Heroku access.
Revoke access for offboarded users
  1. In Heroku, go to Dashboard → Team → Members, remove offboarded employees, and revoke their app collaborations.
  2. In DSALTA, open People and confirm offboarded employees are marked terminated.
Once no offboarded employee retains active Heroku 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 Heroku 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 offboarded accounts no longer have access, 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 Heroku.