Skip to main content
Connect Teamwork.com with a site owner’s API token and your site URL to sync site members with their two-factor status and projects, and run access and MFA reviews. Read-only. Data feeds into your Access accounts and Inventory pages.
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.
What you’ll see. The Access page lists the members of the Teamwork.com site whose URL you enter at connect time — the people the token’s owner can see, which is the whole site for a site owner’s or administrator’s token — with their name (falling back to their full name, username, then email address), their email, their site role (Site Owner, Administrator or Member) and the date they were added to the site (or the date of the sync when Teamwork.com reports none). Client users, collaborators and contacts, service accounts, observers, people whose invitation is still pending, and deleted people are left out. Because deleted people are not synced, every listed member is shown as Active. Teamwork.com does report per-user two-factor authentication, so the MFA column shows Yes or No, and is blank (a dash) for a member whose record carries no value.
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 the Teamwork.com site people roster — names, emails, site roles, two-factor flags and creation dates — which appears on your Access page; and your Teamwork.com projects, which appear on your Inventory page with their status (and sub-status), type, and whether they are one of Teamwork.com’s sample projects. Projects are read best-effort after the roster: a failure on that call leaves the Inventory page empty without failing the sync, and a site with no projects has nothing to list. Members’ last-login and last-active times and login counts are not synced, and tasks, files and messages are not read.It calls these Teamwork.com endpoints on your site URL (https://{site}.teamwork.com, or https://{site}.eu.teamwork.com for an EU-hosted site):
  • /me.json
  • /people.json?includeObservers=false
  • /projects/api/v3/projects.json
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Teamwork.com environment.

​
Troubleshooting

Teamwork.com API tokens are personal. A regular member’s token only sees the people who share a project with its owner, and DSALTA rejects it at connect time — use the site owner’s or an administrator’s token. A wrong site URL is rejected the same way as a bad token: an EU-hosted site must be entered as https://{site}.eu.teamwork.com. A Teamwork Desk, Spaces or CRM key does not work against the Projects site either.
Client users, external collaborators and contacts, service accounts, observers and people whose invitation has not been accepted are not site members and are left out on purpose. A member who was deleted from the site is left out as well. The token’s owner also has to be able to see the person: a token from the site owner or an administrator sees the whole site.
Projects are read best-effort after the roster: a failure on that call leaves the Inventory page empty without failing the sync, and a site that has not created a project yet has nothing to list. Click Sync from integrations on the Integrations page to retry.
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.