Skip to main content

​
What this check does

DSALTA lists the team’s members with the connected Account-Token and reads each member’s two-factor flag. A member whose flag is not reported as enabled counts as not enabled. How many members the team requires to set up two-factor authentication is recorded as supporting evidence.
This check also runs on 25 other integrations — see MFA should be enabled for all users for the full list.
This check reads the live team member list on every run, not the Access page, and every team member counts — including members the team administration has marked inactive. A member whose two-factor flag is missing counts as not enabled. The number of members the team requires to set up two-factor authentication is recorded alongside the result as evidence, but a member who is required to set it up and has not yet done so still counts as not enabled. If SeaTable returns no members at all — which cannot happen on a working token, because the token’s own user is always a team member — the run ends in an error rather than a pass, so a broken credential is never mistaken for full two-factor coverage.
Passes when: Every member of the SeaTable team has two-factor authentication enabled. A member without a readable flag counts as not enabled, and the check needs at least one member to evaluate.

​
Why this matters

SeaTable team members can read and export every base shared with them and create API tokens for those bases. Two-factor authentication on every member keeps a stolen password from being used to reach that data.

​
How to fix

Enforce two-factor authentication in SeaTable
  1. Ask each flagged member to sign in to SeaTable, open Settings → Two-factor authentication, and set it up.
  2. As a team administrator, open Team administration → Users and require two-factor authentication for the members, so that no member can leave it off.
  3. Remove from the team any member who will not enrol — a member the team administration has marked inactive still counts until removed.
  4. Run the check again from Compliance → Tests, or wait for the next scheduled run, and confirm no member is still reported without two-factor authentication.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Compliance → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Compliance → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.