- Overview
- How to connect
- Automated checks
- Useful links
Connect Grist with an API key to sync organization members, workspaces and documents, and run access reviews. Read-only; the key is held by Nango, and DSALTA keeps only a connection reference.
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 one Grist organization — a team site when the key can see one, otherwise the personal site — with their name, email and access level (owners, editors or viewers). Only people Grist marks as members of the organization are included; guests who were shared a single document or workspace are left out. Grist reports no account status, join date or MFA state, so every member is shown as Active with MFA 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 Grist organization member roster — names, emails and access levels — which appears on your Access page; and the organization’s workspaces, which appear on your Inventory page with a count and the names of the documents inside them. Document contents are never read.It calls these Grist endpoints, through Nango’s proxy, ondocs.getgrist.com:/api/orgs/api/orgs/{id}/access/api/orgs/{id}/workspaces
Troubleshooting
The Access page shows my personal site instead of the team
The Access page shows my personal site instead of the team
A Grist API key can see every site its owner belongs to. DSALTA prefers a team site over a personal one and, among several, takes the one with the lowest ID; there is no field to pin another. Connect with the key of a user who belongs only to the team site you want reviewed. Note that disconnecting permanently deletes the data already collected from Grist.
The connection is rejected
The connection is rejected
DSALTA checks the key as soon as Nango reports the connection, by listing the sites it can see. A mistyped or revoked key, or one whose owner belongs to no Grist site, is rejected there and the integration never reaches the Connected tab. If the card later reads Connection issues detected under Manage → Status, disconnect and connect again with a fresh key from Account settings → Developer.
How do I check whether the connection is healthy?
How do I check whether the connection is healthy?
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.
A check shows Failed and nothing changed on my side
A check shows Failed and nothing changed on my side
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.
Data looks out of date
Data looks out of date
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.
How do I repair a broken connection?
How do I repair a broken connection?
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Configure scope will not let me change anything
Configure scope will not let me change anything
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.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)