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

​
About

When you connect Anthropic to DSALTA, the platform syncs your organization members using read-only API access. On every sync DSALTA matches each user with active Anthropic 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.
Listing Anthropic members requires an Admin API key (sk-ant-admin…). If the Access page is empty, reconnect with an Admin key — a standard inference key exposes no members.

​
Why This Matters

Offboarded employees must not retain access to your organization’s AI platform. 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. Timely access removal on termination is explicitly required by SOC 2, ISO 27001, and GDPR.

​
How to Fix

Before you begin
  • Ensure the Anthropic integration is connected with an Admin API key so DSALTA has the current list of members.
  • Identify offboarded employees by cross-referencing the DSALTA People module with active Anthropic members.
Remove access for offboarded users
  1. In the Anthropic Console, go to Settings → Organization → Members and remove members 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 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 Anthropic integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
Listing organization members requires an Admin API key (sk-ant-admin…). A standard inference key connects but exposes no members. Reconnect with an Admin key created from the Anthropic Admin keys page.
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 Anthropic.