Users and systems should have the fewest privileges needed to complete their required tasks:

Only create the roles you need when you need them.

Fauna evaluates roles and privileges at query time. This lets you create or change roles as needed. Changes to roles and privileges take effect immediately and affect existing secrets.

For the best performance and lower costs, only use role-related predicates when needed.

Role-related predicates are evaluated for every applicable query. Predicate evaluations consume Transactional Read and Transactional Compute Operations.

Avoid using role-related predicates to filter collections or large sets of documents. Instead, use indexes.

When possible, set a ttl (time-to-live) timestamp for Fauna keys and tokens. To limit the impact of stolen credentials, use the shortest feasible ttl for your use case.

Similarly, JWTs created by an access provider should include the soonest exp timestamp possible for your use case.

Use predicates with environmental attributes, such as date or time, and identity-based attributes to limit access if credentials are stolen. For example, you can only grant access to users connecting from specific locations or IP addresses or during specific hours.

If you use tokens, use membership predicates rather than privilege predicates to check environmental attributes, such as date or time, or identity attributes. This avoids duplicating the predicate across multiple privileges.

If you use tokens, you can update identity documents in real time to dynamically control access with role-related predicates.

For example, you can use a membership predicate to control access based on the badgedIn field in Employee identity documents. Fauna checks the predicate at query time for every query.

If you use membership predicates to assign multiple roles to tokens, structure the predicates to return as early as possible. This ensures Fauna spends less time evaluating the predicate. See Membership for multiple roles.

Use collection privilege predicates to validate the input and output of document operations.

For example, you can use a write privilege predicate to ensure users can’t read or update specific document fields. This limits the surface area for attacks.

Use function privilege predicates to validate the arguments passed to a UDF call.

For example, you can ensure users can’t call a function with data unrelated to their tasks or scope. This limits the surface area for attacks.

Connect your client application directly to Fauna to limit the surface area for attacks.

Roles are scoped to a single database and don’t apply to its peer or child databases.

If you have a multitenant application, you can copy and deploy roles across databases using FSL and a CI/CD pipeline. See Manage schemas with a CI/CD pipeline.