Authentication proves an identity
Signing in can establish that a request belongs to an account. It does not automatically authorize access to a particular organization, project, document or database row. Treat authorization as a separate decision on every protected operation.
Model organization membership
Maintain explicit organization memberships and roles on the server. Never infer permissions solely from UI state or untrusted user-editable profile fields. Where role changes must take effect immediately, account for cached or long-lived token claims.
Enforce access at every layer
A control plane should validate organization context for project lifecycle actions, while the data plane enforces tenant-specific database access. Storage downloads, websockets and background jobs need their own checks too.
Verify failure behavior
Test expired sessions, stale memberships, revoked access, cross-tenant resource IDs and privileged-role access. UnDataly's roadmap explicitly gates public mutation behind identity, RBAC and auditability.
Frequently asked questions
Are these UnDataly features available now?
Guides explain general architecture patterns. The linked UnDataly managed features are planned or in development unless otherwise marked.