Access policies
Access policies are the TaruviBase policy engine's rules for deciding whether an authenticated caller may perform an action on a resource. Authentication proves who the caller is; authorization evaluates the caller, resource, action, and allow/deny decision.
Start with access decisions, then choose a
Console workflow for roles, policies, conditions, and decision testing. Check
access from code with the Python SDK (client.policy), the JavaScript SDK
(Policy), or the Refine accessControlProvider.
Choose a task#
| Task | Start here | Expected outcome |
|---|---|---|
| Test your first access decision | Verify an access decision | One allowed and one denied decision |
| Create a reusable role | Create app roles | A role ready for an access policy |
| Give a user a role | Assign user access | A site user receives the intended app membership |
| Verify automatic synchronization | Automatic policies | Both policy levels are present and tested |
| Change a policy definition | Manage policies in the Console | An updated policy |
| Restrict rows | Use Database policy filters | Server-side policy filtering |
| Validate decisions before release | Test decisions | Recorded ALLOW and DENY cases |
| Check a caller in code | Check access at runtime, the JavaScript Policy client, or Refine access control | A caller-bound decision |
| Resolve a failure | Troubleshooting | A reconciled policy or a stopped release |