A schema is a logical grouping of related models. Think of it as a namespace or a "module" of your application.

Examples

  • A CRM schema with Customer, Contact, Opportunity and Account models.
  • An Inventory schema with Product, Warehouse, Stock and Supplier models.
  • A Project management schema with Project, Task, Milestone and TimeEntry models.

Why split into schemas?

  • Independent evolution — one team can iterate on the CRM schema while another works on Inventory.
  • Access control — roles can grant access to whole schemas at once.
  • Clarity — finding the right model is easier when they're grouped by purpose.

Ownership

Every schema has an owner. The owner can be either:

  • A user — typically you, when you create the schema. Personal schemas behave this way: only that user can change the schema's settings, add models to it, or transfer it.
  • An organization — the schema belongs to a team. Any owner member of that organization can manage it, not just the person who created it.

You pick the owner type when creating the schema, and the owner can be transferred later by anyone who currently has management rights. Choose organization for schemas that should outlive their original creator or that several people need to administer; choose user for personal experiments.

Access

Apart from ownership, every schema has an access setting that decides who in the tenant can see and use it. There are three modes:

Mode What it means
Private Only actors with an explicitly assigned role can access the schema. This is the strictest mode and the default for sensitive data.
Shared Any actor in the tenant has full access (read, write, delete) without needing an explicit role assignment.
Own only Any actor can see the schema and create instances in it, but each one only sees and edits the rows they created themselves.

Use Private when you need fine-grained control through roles, Shared for tenant-wide reference data, and Own only for use cases like personal tasks, private notes, or per-user submissions where every user works on their own data.

Creating a schema

Open the Explorer, click + New schema in the sidebar, give it a name and a short description. Then choose the owner (user or organization) and the access mode. Save, and start adding models to it.

Both the access mode and the owner can be edited later from the schema's update screen, provided you have the right to manage the schema.