How DSALTA integrates with Workable — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to Workable using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.DSALTA reads the members of your Workable recruiting account — including each member’s roles and active status — and compares them against your People directory to run access reviews.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Workable account.
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.
DSALTA reads the Workable user roster — names, emails and roles — which appears on your Access page. A member Workable reports as inactive is stored as Inactive, and the Access page’s Status column shows every synced account as Active regardless, so read who is deactivated from Workable itself.It calls these Workable endpoints:
/spi/v3/accounts
/spi/v3/members
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Workable environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the Workable card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Workable. This usually happens when the API access token was revoked or regenerated in Workable.
Data is not syncing
Confirm the API access token is still valid and the subdomain is correct, then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once. A token generated by a user who no longer has admin access may stop returning members.
Before you begin
An Admin account in Workable. Workable’s help centre is explicit: “To generate or revoke access tokens for your account, you must be an Admin user in Workable.” A recruiter or hiring-manager account will not see the API Access Tokens section.
1
Start in DSALTA
Open Integrations in the DSALTA sidebar, find Workable, and click Connect to open the connect panel.
2
Open Workable Integrations
In Workable as an Admin, click your profile icon and go to Settings → Integrations → Apps, then find the API access tokens section.
3
Generate an API access token
Click + Generate API token, name it, choose an expiry, and tick r_jobs — that single scope covers both endpoints DSALTA reads. Then copy the token and store it securely.
Copy the token before you close the dialog — Workable says “Your access token will not be visible after closing the modal. If you need it again, you should generate a new one.” You must also pick an expiry (30 days, 90 days, 6 months, 1 year or 2 years). Choose the longest your policy allows, and note the date: when a token lapses DSALTA drops to Disconnected and there is no Reconnect button. The one piece of good news is that Workable’s Renew button keeps the same token value — “all scripts or applications using this token will continue functioning normally” — so renewing in Workable before it expires keeps the DSALTA connection alive, whereas generating a replacement token forces a disconnect (which deletes the collected evidence and tests) and a fresh connect.
r_jobs is genuinely all DSALTA needs, and it is enough on its own: Workable’s API reference lists r_jobs as the required scope for both endpoints DSALTA calls — /spi/v3/members and /spi/v3/accounts. Leave r_candidates, r_employees, r_requisitions and r_timeoff unticked; DSALTA never reads candidate, employee or time-off data, and r_employees in particular exposes sensitive HR records.
4
Find your subdomain
Get your account subdomain from your Workable company profile settings — it is the {subdomain} in {subdomain}.workable.com.
5
Connect
In the next step, paste your API token and subdomain into the Workable connect window and click Connect.
Once connected, Workable appears on the Connected tab and the checks below begin reporting after the first sync.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
