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
Keep identity, tenancy, and deep permission policies enforced in the backend, not 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 ↗
Give AI-assisted teams a governed data model, query layer, and transactional save path instead of a hand-built backend.
Functions ↗
Run business logic inside the tenant runtime without deploying an application server or server farm.
Workflows ↗
Compose durable, inspectable business processes instead of asking generated glue code to hold state.
Documents ↗
Manage documents, PDFs, messages, files, and multilingual content as governed backend capabilities.
Assistant ↗
Let coding agents work through CLI and MCP against the same governed backend contract your team controls.