Skip to main content

​
What this check does

DSALTA matches each user with active Wrike 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.
This check also runs on 82 other integrations — see Offboarded users should not have active access for the full list.
Passes when: No offboarded employee retains active Wrike access.

​
Why this matters

Offboarded employees must not retain access to the organization’s work management platform.

​
How to fix

Remove Wrike access for offboarded users
  1. Sign in to Wrike with an account that has the Admin or Account Owner role.
  2. Click your profile image in the sidebar, choose Settings, then under Account Management select Users.
  3. Find each offboarded employee in the Active users list — this test’s Source Data tab in DSALTA names the accounts that were flagged.
  4. Click the user to open their profile, then click Deactivate and confirm; they are signed out of every session immediately and keep their task history.
  5. If Deactivate is not offered on your plan (it requires Pinnacle or Apex), click Delete instead to remove the user from the account, and reassign their open tasks to a current employee.
  6. In DSALTA → People, confirm each offboarded employee is marked Terminated.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.