Skip to main content

​
What you’ll learn

This guide explains what Policies are and how to manage them in your workspace. For activity history and CSV export, see: Workspace Logs

​
Overview

Policies help validate automated write operations (agents, workflows, integrations) against your business rules before execution.

​
How a policy is selected (basic)

Each decision uses one policy. For a given Object Type / Action, Sanka selects a policy in this order:
  1. Principal-bound policy (if a binding exists for the principal)
  2. Workspace default policy (fallback)
  3. If neither exists, Sanka treats it as no policy found for that operation
A “principal” represents who/what is performing the action (UI user, API token, integration app, workflow, etc.).Notes (current state):
  • Policies are rolling out in a scope-limited way (some operations may not be covered yet).
  • Detailed rule building will be expanded in later phases.

​
Open Policies

  1. Open Sanka.
  2. From the left sidebar, open Workspace.
  3. Click Policy & Logs.
  4. Select the Policies tab.
If you do not have permission, you may see an access-denied screen. Typically, Workspace Admins manage Policies.

​
Create a Policy

  1. In the Policies tab, fill in the fields:
    • Policy Key: Unique identifier in the workspace (keep stable; it can be referenced by logs/automations. If you need to change it, create a new policy instead).
    • Name: Human-readable label.
    • Object Type and Action: What operation the policy applies to.
    • Priority: Lower numbers are evaluated first when multiple policies match.
  2. Click Create.
Current behavior:
  • New policies start with an empty rule set (allow by default).

​
Activate, deactivate, priority

  • Active: Can be used for validation.
  • Inactive: Ignored.
Priority:
  • When multiple candidates exist (for example multiple bindings), the one with the lowest priority number is selected first.

​
Default policy (workspace baseline)

The default policy is the baseline for an Object Type / Action and is used when no principal binding exists.To set it:
  1. Open the Policies tab.
  2. In the list, find the policy you want as default and click Set in the Default column.

​
Principal-specific bindings

Use bindings when you want a specific principal (UI user, API token, integration, workflow) to use a different policy than the workspace default.
  1. Open the Principals tab.
  2. Create the principal if needed.
  3. Create a binding between the principal and a policy.
  4. Use Preview to confirm which policy will apply for a principal + scope.

​
Tips

  • Start with a small number of high-value operations, then expand.
  • If you only need logs, use the Logs tab and the Workspace Logs guide.