🗂️ Introducing Workspaces: for securely sharing financial data with your team, family or clients

Meet Workspaces: separate, self-contained Fintable environments under one login and one plan — designed for families, teams, and multi-client setups for accountants. And for the first time, your API tokens and AI assistants can work across all of them.

A Workspace keeps its bank connections, financial data, spreadsheets, and settings separate.

(If the concept sounds familiar: this feature was previously called Sub Accounts. It has been renamed and revamped — existing setups keep working unchanged, and every old link redirects.)

Designed for families, teams, and multi-client firms

Workspaces are how Fintable serves more than one set of books under one roof:

• Accountants and bookkeeping firms run a Workspace per client. Each client's banks sync to that client's own Airtable base or Google Sheet, the books never mix, and your whole practice is billed on one Office plan.
• Families might give each household member their own Workspace — or simply keep personal and business finances apart — with every Workspace syncing to its own spreadsheet.
• Teams and companies might give each entity, country, or department its own Workspace, then consolidate through the API into one reporting pipeline the finance team owns.
• Access without shared passwords. Each Workspace has its own login you can hand to a client or family member, while you manage everything from your primary Workspace with the Quick Switcher — no logging out, no juggling browser profiles.
• One plan, combined usage. Managed Workspaces inherit the primary Workspace's plan; transaction volume is combined under it, so adding a client or family member is an organizational decision, not a billing negotiation.

Your AI assistants and tools work securely across Workspaces

For a firm, that means one AI assistant that prepares month-end across every client — "categorize last month in Client A's Workspace, then do the same for Client B" — without sharing logins or copying tokens around. For a company, one integration that consolidates every entity. For developers building for teams, one token instead of one per client.

• Explicit, per-credential access. When you create a Personal Access Token or approve an OAuth/MCP app, you tick the Workspaces it may reach. Nothing is ever included silently — existing tokens and apps stay default-Workspace-only until you edit their Workspace access or reconnect them, and new Workspaces are never added to an existing credential automatically.
• Controls an enterprise can sign off on. Access is re-checked on every single request, editing grants requires a fresh password confirmation, revocation and plan changes take effect immediately, and every cross-Workspace call is attributed in our logs. A credential can never see a Workspace its owner didn't explicitly grant.

Getting started

Workspaces live in the renamed Workspaces page of your dashboard, available on the Office and Enterprise plans. The user guide covers creating and sharing Workspaces with clients and teammates, and the API docs cover Workspace selection for tokens and connected apps.