Folders

Folders keep a growing account tidy — "Sales", "Ops", one per client — without ever splitting your data. A table in one folder relates to a table in another exactly as it would if they sat side by side. Folders, not separate workspaces Your account has one home for its data, and everything in it can relate to everything else. Folders are how you organise inside it — Sales, Ops, one per client — and they are deliberately not walls: a Deals table in one folder can link to a Companies table in another, follow lookups across it, and roll values up through it. That is the whole reason folders replaced separate workspaces. Every boundary between workspaces is a place where relationships stop, and relationships are the point. Folders appear when you need them A brand-new account shows a plain list of tables and no folder chrome at all. Folders appear once there are two of them: a template you add lands in a folder of its own, and the AI builder gives a business with several areas one folder per area (see below). Right-click anything in the table list to act on it. On a table: Rename table…, Change icon…, and the folders you can move it into. On a folder heading: Rename folder…, Change icon…, New folder… and Delete folder… — deleting a folder frees its tables to the top level and deletes no records. Every table row also carries a grip on its left, and every folder heading one on its right. Drag a grip to reorder tables and folders, drop a table onto a folder heading to file it inside, or drop it among the ungrouped tables at the top of the list to take it out of every folder. A line shows exactly where it will land; a folder tints when the table will go inside it. On a phone the grip is always visible, so all of this works by touch as well. You can also focus a grip and move it with the arrow keys. All of it needs Admin, and all of it is also a form in the table's own field editor — Name & icon and Folder — if you would rather use the keyboard. Renaming a table changes its label everywhere and nothing else: its API key and every field key stay exactly as they are, so saved views, automations and integrations keep working. The builder files tables by area Describe a business with several distinct areas, such as a fabrication shop with sales, production, purchasing and finance, and the builder shows you a plan before it builds anything. The plan has a folder for each area. The records every area uses, such as customers, staff and materials, sit at the top level, once, where every folder can link to them. Choose Build it all, or Start with the areas the plan puts first. You can also type what to change, and the builder redraws the plan. It then builds one folder at a time. If it finishes with areas still to build, Keep building the plan? offers exactly those, worked out from the tables that exist, so nothing you already have is offered twice. The workspace gets its report and dashboard once, not again with every area. A business with one area of work, such as a salon or a studio, gets no folders: a single folder holding everything would only add a heading above the same list. In Ask, a table the AI proposes can name a folder too. It uses an existing folder by name, and the card says when a folder will be new. Give someone a whole folder Open Permissions, pick a person, and set their access on the Folder access card. One setting covers every table in that folder — so “the contractor gets the Acme folder” is a single action rather than one grant per table. A table's own override always wins over its folder's, so a deliberate per-table decision is never quietly overruled by a broader one. Hide a folder completely Mark a folder hidden and it disappears for everyone without an explicit grant — not greyed out, not locked, gone. Its name goes too, which is usually the point: a “Cost Savings” folder sitting there locked still tells the room it exists. A folder is listed only when at least one table inside it is visible to you. Admins always see everything. Invite people and set roles Open the workspace's People page to see everyone with access. Each member card shows their role and a plain-English summary of what it allows. From most to least access: • Admin — full control: schema, members, automations, everything. • Editor — read, create, edit, and delete records; no schema or member control. • Contributor — read everything and create new records; cannot edit or delete records that already exist. • Viewer — read-only, for stakeholders who only need visibility. Only workspace Admins can manage membership. Use the role dropdown on a member's card to change their role, Remove to revoke their access, or + Invite to add someone with a starting role. The picker under Invite someone lists only people you already share a workspace with — if all of them are members already, the invite form doesn't appear. Transfer ownership To hand a workspace to someone else, open Settings and find Transfer workspace ownership in the Danger zone. Choose the member to promote and click Transfer: they become that workspace's Admin and you are moved to Editor there. You can only transfer a workspace you administer, and only when it has at least one other member. Leave, export, or wind down Removing a member — or being removed — only revokes access. The workspace and everything in it stays put for its remaining members, and there is no button for deleting a whole workspace. Before winding anything down, grab your data from Data export in Settings: Full workspace JSON covers schema and every record across all your workspaces, and CSV per table downloads a zip with one CSV for every table you can access. To close your account, type your email to confirm and click Delete account — your profile, memberships, and permission overrides are removed, shared workspaces remain for their other members, and it cannot be undone. Tips • Folders organise; they never isolate — link freely across them. • One folder holding everything renders flat, so there is no chrome until a second folder exists. • A template lands in a folder of its own. The AI builder files a business with several areas into one folder per area, with the shared tables at the top level. • Hidden folders vanish by name as well as contents — use them for anything whose existence is sensitive. • A table’s name and icon are edited from the rail — right-click it — or from Name & icon in its field editor. Renaming never changes the API key. Good to know • A table's own permission override beats its folder's — check both if access looks wrong. • Hiding a folder does not hide a table that has its own explicit grant. • There is no sub-folder level: use names like “Acme — Delivery” if you need a hierarchy. Who can do what • You can only open workspaces you're a member of — a brand-new account belongs to none and sees none until it creates one or is invited. • Creating a workspace automatically makes you its Admin. • Inviting members, changing roles, and removing members require the Admin role in that specific workspace — being a member is not enough. • Transferring ownership requires Admin in that workspace; after the transfer you become an Editor there. • Only workspace Admins see the + control for adding tables in the sidebar. • The invite picker only lists people you already share a workspace with — it never exposes the full user directory.