Security Assignments
Bind security definitions to users and tenants
Security assignments bind a definition to a specific actor, and can supply the parameter values that assignments own. An assignment turns the definition on for the actor it names.
Assignment scopes determine who the policy applies to:
| Scope type | Applies to |
|---|---|
ALL_TENANTS | Every tenant and tenant user on the connection |
TENANT | One tenant |
TENANT_USER | One tenant user |
ORG_USER | One organization user |
ALL_TENANTS is optional. Use it when a policy should reach every customer, and
skip it when only some customers should receive it. See
How Row-Level Security Works for
value sources and precedence.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
| GET | List assignments | List all assignments in a project |
| POST | Create an assignment | Bind a definition to an actor |
| GET | Get an assignment | Retrieve a single assignment |
| PATCH | Update an assignment | Update scope, actor, or parameters |
| DELETE | Delete an assignment | Remove the binding between a definition and an actor |
| POST | Validate a new assignment | Validate a create candidate without saving |
| POST | Validate an assignment update | Validate an update candidate without saving |