# Tooling and Access

Tools, workspaces, accounts and who stands behind each account, plus plans, seats and grants.

Tooling and Access - Pedro records the software the group uses: each tool, the workspaces configured in it, the accounts those workspaces issue and the person or membership behind each account. Other systems read it to tell who sent a Slack message, which seller owns a Cal.com booking calendar or which membership a mailbox serves. Shared people, organizations, memberships, teams, departments and tags come from Core.

The base also has tables for plans, seats, access principals, resources and permissions. They were empty on 2026-10-28, so the base does not yet describe what the group pays for or who may access what.

## Start here

| Your task | Guide |
| --- | --- |
| Register a tool, a workspace or an account | [Register a tool account](/systems/tooling/register-accounts) |
| Record who is behind an account, or close that record | [Bind an account to a person](/systems/tooling/bind-accounts) |
| Record a plan, a seat or a permission | [Record plans, seats and grants](/systems/tooling/record-access) |
| See which bases and workflows read this data | [Architecture and ownership](/systems/tooling/architecture) |
| Work on bot accounts or credentials | [Secrets and the Access Token column](/systems/tooling/secrets) |

## Choose the right surface

Open **Data** in Tooling and Access - Pedro and work in table views. The base has no grid intakes, no check formulas and no Airtable automations: a row is complete when the fields its entity reference asks for are filled. Airtable Interfaces are outside the operating model. [Data views](/systems/tooling/data-views) lists all 24 views.

[![Tool → External lists each product with its workspaces and accounts.](/systems/tooling/screens/tool-external.png)](/systems/tooling/screens/tool-external.png)

## What is verified

This reference covers the 15 tables, 213 fields and 24 views of the base on 2026-10-28, plus the known n8n workflows that read the base. Nine tables are native to Tooling; six are Core mirrors. Three tools are registered: Slack, Cal.com and Google Workspace.

Tool Account has an Access Token column that holds credentials in clear text, against the group rule that secrets are referenced and never stored. Read [Secrets](/systems/tooling/secrets) and [known gaps](/systems/tooling/known-gaps) before relying on bot accounts, seat counts or permissions.