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.

Where you see it

In the Explorer, the selector above the model list shows the active schema (SCHEMA) and how many models it holds. Click it to switch to another schema: the list groups them into my schemas, each organization's, and shared ones.

Ownership

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

  • You — the Personal option when you create it. Only you can change its 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.

Choose an organization for schemas that should outlive their creator or that several people need to administer; choose Personal for your own experiments.

You pick the owner when you create the schema. To change it later, open Organizations → Schemas (in the user menu): from there you can bring a personal schema into an organization, move it to another organization, or transfer it to yourself.

Languages

Every schema has a default language and a list of supported languages. Model and property names, and the translatable texts in the data, can be written in each of them. A new schema takes the application's language; you can add more at any time.

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 one a new schema starts with.
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

  1. Open the Explorer and click the Create button (the + sign) above the model list.
  2. Choose Create Schema.
  3. Type its Name, choose the Owner (Personal or one of your organizations), check the Languages and pick the Access.
  4. Click Create. The new schema becomes the Explorer's active one, ready for models from the same Create button.

Editing a schema

Hover over the Explorer's schema selector and click the pencil (Edit schema). You can change the name, the languages and the access, and save with Save. From here you can also delete it (Delete), provided you have the right to manage it.

Schemas themselves have no versions: the models inside them do. Every time you edit a model, Yellow creates a new version of it.