Platform module

Authorization

Model permissions as relationships — who owns what, who can read it, and who can change it — without hardcoding rules in every route.

What you can build

Key capabilities for authorization — explore the docs for setup and examples.

Define what can be protected and how ownership and membership connect.

Let teams own documents and inherit permissions naturally.

Ask the platform who can do what — keep authorization logic centralized.

Modules teams often enable alongside authorization.

Sign-in flows your users expect — email, social logins, magic links, 2FA, and team management.

Flexible data models on MongoDB or PostgreSQL — CRUD, relationships, and powerful queries in one interface.

Explore the full module catalog or jump into the docs.