Skip to main content
Connect Wrike with a permanent access token to sync internal team members, projects, and (on Enterprise plans) security-relevant audit events, and run access reviews. Read-only.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads your Wrike contacts — first and last name, email address, role, and whether the profile is active or deleted — which appear on your Access page; your Wrike Projects, which appear on your Inventory page; and a filtered slice of the audit log covering account, admin-rights, SSO and two-factor events, which appears on your Incidents page. Groups, Wrike’s Robot accounts, and External Users and Collaborators are left out of the Access page, and tasks, comments, attachments, time logs and file contents are never read. The Incidents page requires a Wrike Enterprise plan, with the amReadOnlyAuditLog scope and the “Create user activity reports” admin right.It calls these Wrike endpoints:
  • /account
  • /contacts — and again as /contacts?deleted=true
  • /folders?project=true
  • /workflows
  • /audit_log
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Wrike environment.

​
Troubleshooting

The Access page lists internal people only. Groups (including My Team), Robot accounts, and anyone holding an External User or Collaborator licence are not included — check the licence type in Wrike for anyone you expected to see.
Invalid, revoked or truncated permanent access token. Wrike shows the token exactly once when you generate it, so a partial copy is the common cause.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.