Known gaps
Separate the base's current behavior from its descriptions, open defects and planned work.
These findings describe the base on 2026-10-28.
Secrets
- Tool Account → Access Token stores bot credentials in clear text, against the rule “Secrets are referenced, never stored”. Its description tells people to paste the token. Work Item: “Move the Tool Account Access Token out of Airtable”.
- Every Tool Account view shows the column, and the sync view feeding CRM carries it to the CRM copy.
- Bot Secret Ref values reportedly point to the Access Token cell rather than a vault. See Secrets.
Schema and descriptions
- The calculated Name fields on Tool Workspace, Tool Account and Identity Binding have descriptions written for typed or running-number fields.
- Fields without descriptions: Tool url and App url; Tool Workspace Company, Created by, created at, Workspace URL, Tool URL and App URL; Tool Account Workspace: Company, Created by and Created at; Identity Binding Account: Name and Member. Four of the six Core mirrors have no table description.
- Descriptions refer to fields that do not exist: company-side controller, owner and payer links, Seat Allocation Shared With and Responsible, and Identity Binding evidence.
- Bound Person and Bound Membership claim to travel with the mirror; the CRM sync view does not include them and the Communication mirror is not built yet.
- The Team mirror is named Grid view, and a Tool Account view is named By Kynd. Tags (mirror) has an unexplained self-link pair, Tags / From field: Tags.
- The four Identity Binding lookups added for Cal.com routing are unused (Work Item “Finish Cal.com session config cleanup”).
Integrity not enforced
Rules such as one tool per workspace, one workspace per account, one open binding per account, one principal and one resource per grant, matching tools across workspace, subscription and seat, and seats within Seat Count exist only in descriptions. Pickers allow several records and no formula or automation checks them. The Slack resolver does not check Valid From.
Empty structures and personal data
Subscription, Seat Allocation, Access Principal, Resource and Access Grant hold no rows, so the base does not record spend, licenses or effective permissions. Person (mirror) copies personal fields such as Date of Birth*, National ID and Address that no Tooling table uses.
Documentation boundaries
These pages cover all tables, fields, views and the Airtable automation list. Sync source views are inferred from field sets; check sync settings, Airtable sharing permissions and n8n execution history before relying on them. No Tool Account or Identity Binding screen is captured, because those views show credentials or login addresses.