ReferenceInspire
Namespaces
Define tenant scope once and let the runtime enforce it across reads, writes, and live queries.
Syntax
namespace Tenant {
scope: principal.organizationId,
entities: [Project, Invoice],
}Use namespaces for tenant isolation, regional partitions, or any other scope that should be applied automatically.
What It Affects
Once an entity is namespaced, that scope affects:
- reads
- writes
- includes
- live queries
Recommended Usage
Use namespaces when the correct answer is “this entity always belongs to the current tenant unless a privileged workflow says otherwise.”
Related guide: Multi-Tenancy