Permission – Baack docs
Permission
Representation of a permission grant. Permissions are fail closed so if an object requires a permission it must be present for the subject with the given label.Permissions represent directed edges granting a subject(type) [label] to object(type). When applied to an object the permissions will be checked for an exists style relationship from the subject scope.
Endpoints
GET/n/v1/permission/{urn}
Endpoint for managing permission grants on the platform.
Parameters
urn(path, required)- String representation of a Unique Resource Name. Typically a UUID with 36 characters.
Responses
- 200 OK
- returns Permission
READ_SUCCESS - 404 Not found
- returns Error
NOT_FOUND
curl -H "Authorization: Bearer $BAACK_API_TOKEN" \ https://api.baack.co/n/v1/permission/{urn}
Fields
| Field | Type | Description |
|---|---|---|
| urn | string (uuid) | |
| owner | Company | Required on create. |
| subjectScope | string | One of: |
| objectUrn | string (uuid) | Required on create. |
| fromTimestamp | string (date-time) | |
| subjectUrn | string (uuid) | Required on create. |
| objectScope | string | One of: |
| label | string | One of: Up to 255 characters. |
| toTimestamp | string (date-time) |