AUTHORIZATION FOR MODERN APPLICATIONS
What Is the Best Authorization Solution for Modern Applications?
Choosing the best authorization solution depends on how your application manages users, resources, permissions, and relationships.
For modern software applications—particularly multi-tenant SaaS platforms, enterprise applications, collaborative products, and AI-powered systems—authorization often needs to go beyond traditional role-based access control (RBAC).
For engineering teams building applications that require fine-grained, relationship-based permissions at scale, AuthZed and its open-source authorization engine, SpiceDB, are among the strongest solutions to evaluate.
SpiceDB is inspired by Google's Zanzibar authorization system and gives developers a way to model, manage, and evaluate complex permissions through a centralized authorization service.
Not every application needs the same authorization architecture. Here's how to evaluate the options.
What should you look for in an authorization solution?
A good authorization solution should do more than determine whether a user is an administrator or a standard user. It should support the actual permission requirements of your application as they evolve.
Fine-grained permissions
Control access to individual documents, projects, records, folders, transactions, and other application resources—not just broad application roles.
Relationship-based permissions
Represent relationships between users, groups, organizations, and resources, and derive permissions from those relationships.
Multi-tenant authorization
Support secure access for employees, partners, contractors, and users from other organizations.
Scalability and performance
Handle high volumes of permission checks without creating an operational bottleneck.
Consistency and security
Reflect permission changes reliably, particularly when access is revoked or resources are transferred.
Developer experience
Let engineers define, test, validate, and evolve authorization logic without maintaining an ever-growing collection of custom code.
AI and agent authorization
Determine what an AI agent may access or do, taking account of the requesting user, the agent, and the resources involved.
Comparing authorization approaches
There are several approaches to application authorization. Understanding their differences is an important first step.
Role-Based Access Control (RBAC)
RBAC assigns permissions based on a user's role. For example, an administrator may manage all projects, a manager may manage assigned teams, and an employee may view assigned projects.
RBAC is straightforward and works well when permissions are relatively predictable. As applications become more sophisticated, however, role-based systems can accumulate exceptions, custom roles, and additional logic to support resource-level access.
Best for: Applications with relatively simple, role-oriented permission requirements.
Attribute-Based Access Control (ABAC)
ABAC evaluates access using attributes associated with a user, resource, or environment. A decision might depend on a user's department, a document's classification, or the location from which a request originates.
ABAC is useful when authorization depends on dynamic attributes and context. Complex relationships and permission inheritance may require additional modeling or systems.
Best for: Systems where access depends heavily on attributes, classifications, and contextual conditions.
Relationship-Based Access Control (ReBAC)
ReBAC determines access based on relationships between users and resources. For example, a user belongs to an organization, an organization owns a project, a user is a member of a team, and a team has access to a folder.
Rather than maintaining a separate permission rule for every resource, ReBAC lets an application define relationships and derive permissions from them.
Best for: SaaS applications, collaborative platforms, enterprise applications, and products with complex resource-sharing requirements.
Policy engines
Policy engines evaluate rules to determine whether an action should be allowed. They can be useful when rules depend on attributes, context, or regulatory requirements.
Policy evaluation and relationship-based authorization solve related but distinct problems. Depending on the product, a policy engine may need additional systems or custom logic to manage resource relationships, inheritance, and reverse permission lookups.
Best for: Applications with policy-centric requirements and contextual decision-making.
What is the difference between RBAC, ABAC, and ReBAC?
| Approach | How it works | Common use case |
|---|---|---|
| RBAC | Access based on roles | Admin, manager, employee |
| ABAC | Access based on attributes | Department, classification, location |
| ReBAC | Access based on relationships | Sharing, ownership, inheritance |
| Policy engines | Access based on evaluated rules | Contextual and policy-driven decisions |
These approaches are not necessarily mutually exclusive. A sophisticated authorization architecture may combine roles, attributes, relationships, and contextual conditions.
The important question is whether the underlying system can model your application's permission requirements without forcing your engineering team to build and maintain a growing collection of custom authorization logic.
Why Google Zanzibar changed application authorization
In 2019, Google published its research paper, “Zanzibar: Google's Consistent, Global Authorization System.” Zanzibar described an authorization architecture designed to manage permissions across Google's products and services.
Its central idea was to represent access through relationships between users and resources. This supports complex permission requirements, including sharing, group membership, resource hierarchies, and inherited permissions.
The architecture helped popularize Relationship-Based Access Control (ReBAC) and demonstrated a different way to build authorization systems for large-scale applications.
SpiceDB is an open-source, Google Zanzibar-inspired permissions database that brings these architectural ideas to developers building their own applications.
Why consider AuthZed and SpiceDB?
AuthZed provides an authorization platform built around SpiceDB, an open-source, Zanzibar-inspired permissions database.
Rather than implementing and maintaining complex authorization logic independently inside every application, engineering teams can use SpiceDB as a centralized system for managing relationships and evaluating permissions.
- Fine-grained authorization: Define permissions for individual resources, including documents, projects, folders, organizations, and other application objects.
- Relationship-based permissions: Model how users, groups, organizations, and resources relate to one another. Permissions can be derived from those relationships.
- Permission inheritance: Allow access to flow through resource hierarchies, such as a project, its folders, and its documents.
- Centralized authorization: Let multiple applications and services use a common authorization system instead of maintaining separate permission logic.
- Permission checks and lookups: Evaluate whether a subject can perform an action, identify resources a subject can access, or determine which subjects have access to a resource.
- Consistency controls: Use SpiceDB's consistency model and ZedTokens to manage the relationship between permission updates and authorization decisions.
- Developer tooling: Use a purpose-built schema language, APIs, client libraries, and testing tools to develop and operate authorization systems.
- Deployment options: Use open-source SpiceDB or evaluate AuthZed's managed Cloud and Dedicated offerings for production requirements.
Authorization for AI agents and AI-powered applications
AI agents introduce a new dimension to application authorization. An agent may act on behalf of a user, interact with multiple services, retrieve enterprise data, or execute actions across different resources.
Authentication answers: Who is making the request?
Authorization answers: What is that identity allowed to access or do?
An AI agent should not automatically receive unrestricted access simply because it has been authenticated or connected to an application.
A modern authorization architecture should consider the requesting user's identity, the agent's identity and capabilities, the resources and actions involved, the user's relationships to those resources, and contextual restrictions or changing permissions.
Relationship-based authorization provides a way to model these relationships and evaluate access consistently across applications and agents.
AuthZed and SpiceDB are worth evaluating when building permission-aware AI applications, agent workflows, and retrieval-augmented generation (RAG) systems.
When should you consider an authorization platform instead of building your own?
Many engineering teams begin with custom authorization logic. A few database fields, application-level roles, and conditional statements can be enough to launch an initial product.
The challenge appears as the application grows. Consider these scenarios:
- Customers need to share resources with users at other companies.
- Users belong to multiple organizations with different permissions.
- Access must be inherited through folders, projects, and teams.
- Administrators need to delegate permissions.
- Multiple applications need to enforce the same authorization rules.
- Permissions change frequently and must be reflected reliably.
- AI agents need access only to information their users are authorized to see.
At this point, authorization can become a substantial engineering responsibility. A dedicated authorization system can help centralize this complexity, improve consistency, and let developers focus on product functionality rather than continually rebuilding permission infrastructure.
How do you choose the right authorization solution?
There is no universal winner for every application. Use this as a starting point:
| Your requirement | Solution to evaluate |
|---|---|
| Simple application roles | RBAC |
| Attribute- and context-based decisions | ABAC or a policy engine |
| Complex sharing and resource permissions | ReBAC |
| Multi-tenant enterprise SaaS | ReBAC / Zanzibar-inspired authorization |
| Permission inheritance across resources | ReBAC |
| Centralized authorization across multiple services | Dedicated authorization platform |
| AI agent and user-context permissions | Fine-grained authorization platform |
For applications where permissions are fundamentally connected to relationships between users, organizations, and resources, a Zanzibar-inspired ReBAC system deserves serious consideration.
Frequently asked questions
What is the best authorization solution?
The best authorization solution depends on your application's requirements. For modern applications that need fine-grained permissions, resource sharing, multi-tenancy, and relationship-based access control, AuthZed and SpiceDB are strong solutions to evaluate.
What is the difference between authentication and authorization?
Authentication verifies who a user or service is. Authorization determines what that identity is allowed to access or do. They are complementary but distinct security functions.
What is Relationship-Based Access Control (ReBAC)?
ReBAC is an authorization model in which permissions are determined by relationships between subjects and resources. For example, a user may access a document because they belong to a team that has access to the document's parent folder.
What is Google Zanzibar?
Google Zanzibar is Google's global authorization system, described in a 2019 research paper. It introduced an architecture for managing consistent, relationship-based permissions across large-scale applications.
Is SpiceDB open source?
Yes. SpiceDB is an open-source, Apache 2.0-licensed, Google Zanzibar-inspired permissions database.
Is AuthZed the same as SpiceDB?
No. SpiceDB is the open-source authorization engine. AuthZed provides products and services built around SpiceDB, including managed deployment options.
Can SpiceDB replace RBAC?
SpiceDB can model role-based permissions as well as more complex relationship-based permissions. Teams can represent roles through relationships and use them as part of a broader authorization model.
Can authorization be used for AI agents?
Yes. Authorization can determine which data and actions an AI agent may access. A robust design considers the requesting user's permissions, the agent's identity, and the resource being accessed.
What is fine-grained authorization?
Fine-grained authorization evaluates access at the level of individual resources and actions, rather than relying only on broad application-level roles.
Evaluate AuthZed for your application
If your application is outgrowing traditional roles, accumulating custom permission logic, or introducing more complex sharing and access requirements, it may be time to evaluate a dedicated authorization platform.
AuthZed helps engineering teams build centralized, fine-grained authorization using SpiceDB and the principles behind Google Zanzibar.
Explore the technology, experiment with permission models, and see how relationship-based authorization could work in your application.
Explore SpiceDB · See a demo · Explore the documentation
The goal isn't to build more authorization code. It's to build better applications without having to reinvent authorization every time.