Skip to main content
Connect Qase with an API token to sync workspace users and projects, 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.
What you’ll see. The Access page lists every user of your Qase workspace with their name, email and the job title Qase stores for them, which appears in the role column. Qase’s own status is respected — a user Qase reports as inactive is shown as Inactive. Qase reports no join date or MFA state, so the MFA column shows Unknown and each row is stamped with the date of the sync.
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 Qase workspace user roster — names, emails, titles and status — which appears on your Access page; and your Qase projects, which appear on your Inventory page with their counts of test cases, suites, runs and defects. Test cases and results themselves are not read.It calls these Qase endpoints:
  • /v1/user
  • /v1/project
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Qase environment.

​
Troubleshooting

The token is invalid or was revoked, or it belongs to a user whose role cannot list workspace users — DSALTA refuses to connect when Qase returns no users at all. Create a token as a workspace owner or admin and connect again.
Qase’s users endpoint returns each person’s title, not their workspace role, so DSALTA shows the title. Check the actual role under the workspace’s Users settings when you review.
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.