Skip to main content
A workspace is the top-level container in Zite. It ties together:
  • One database — the tables, fields, and records your system runs on.
  • Roles and permissions — defined once, on the database, and shared by everything in the workspace.
  • Many apps and workflows — each built on that same database.
This is the core idea: you model your data and access rules once, then build as many apps on top as you need.
A workspace has a single stable id. You’ll see the same id referred to as the workspace id, the base id (baseId), or the base public identifier depending on context — they’re the same thing. It addresses the workspace, its database, and its underlying code repository.

​
What’s in a workspace

The database

A single Zite database with tables, fields, and records. Every app reads and writes it through a typed client.

Apps

React apps built on the database. A workspace can have many — a customer portal, an internal admin tool, a dashboard — all sharing the same data.

Workflows

Backend workflows that run business logic: called from an app, on a schedule, or from an inbound webhook.

Roles & permissions

Roles and row-level rules defined on the database and enforced everywhere.
Under the hood, a workspace is a git-backed monorepo — one repository holding every app and workflow, plus the generated types and shared design system. You rarely touch this directly; agents build inside it. See Project structure for the layout.

​
Why one database, many apps

Because everything in a workspace shares one database:
  • Data stays consistent. An internal ops tool and a customer-facing portal read and write the same records.
  • Permissions are defined once. You set roles and row-level rules on the database, and every app inherits them.
  • Building is fast. New apps start with the schema, types, auth, and design system already in place.

​
Creating a workspace

You can create a workspace from the dashboard, or ask an agent to do it through the Zite MCP with create_workspace. A workspace can start as database-only (no apps yet) — apps are added later, in the same workspace.