The tenant is the boundary
Every authorized operation runs in tenant context taken from the verified token, never inferred from a URL or a client-supplied value.
Product / Control access
Auth
Enforce identity, tenancy, and record-level authorization at the data layer instead of in the interface.
Permission policies can apply query-based record conditions and operation masks through user, role, group, position, and department assignments.Verified 2026-08-20 · owner GSB Core · evidence ↗
Row policies
Scope records with query-based conditions and operation masks assigned through users, roles, groups, positions, or departments.
Property permissions
Set default permissions across an entity's properties, then override individual fields for sensitive or public data.
One enforcement point
A browser, the CLI, and an authorized agent are callers of the same contract, so publishing a static frontend does not move authorization into client code.
Operations
Each entry links to its reference page, generated from the same documentation the CLI and the MCP server return.
querySearches and retrieves entities based on complex criteria.
getByIdRetrieves a single entity by its unique ID.
saveCreates new entities or updates existing ones.
Keep reading
The guide covers the working shape of this capability, including request payloads, limits, and failure handling.
Rest of the platform
Database ↗
Query and transactionally save related data through one permission-aware entity contract.
Functions ↗
Add tenant-resident logic and shared libraries where data operations are not enough.
Workflows ↗
Describe durable, inspectable processes instead of hiding state in glue code.
Documents ↗
Turn governed multilingual content into stored files, PDFs, and email sent under your own identity.
Assistant ↗
Give a coding agent the same contract as your team, bounded by the same permissions.