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

​
About

When you connect Slack to DSALTA, the platform syncs your workspace members and their access using read-only API access. On every sync DSALTA compares your Slack members against the People page and activates this check if anyone with active access has an employee record that is terminated or offboarding.

​
Why This Matters

When someone leaves and their access is not revoked, their account becomes an unmonitored door into your workspace — a common cause of data leakage and accidental damage. In Slack that can mean lingering access to private channels, files, and conversation history. 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 active Slack members.
  • Ensure you have Workspace Owner or Admin access in Slack.
Revoke access for offboarded users
  1. In Slack, go to Settings & administration → Manage members.
  2. Find each offboarded employee and Deactivate account — this immediately revokes their access while preserving message history for your records.
  3. Remove them from any shared connections (Slack Connect) or externally shared channels that do not revoke automatically.
  4. Revoke any personal tokens or app authorizations tied to that person.
  5. To keep this passing going forward, connect your HRMS to DSALTA so an Offboarded status automatically flags any lingering Slack access.
Once the offboarded users no longer have active 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 Slack 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 are deactivated, 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 Slack.