Skip to main content
POST
cURL
The same declarative bulk upsert as the other two axes, applied to the Semantic Layer. Each assignment is a cross product of recipients and resources, and permission_level: null revokes.

Request body

Each object in assignments:
Unlike Assign Permissions on the Catalog axis, notify_members on this endpoint does send email. If you are provisioning in bulk and do not want to flood inboxes, leave it at its default of false.

The three resource levels

catalogs, folders, and documents are the same hierarchy the Semantic Layer shows in the app, from coarsest to finest. A grant on the catalog root reaches everything; a grant on a folder reaches the documents inside it. Prefer the coarsest resource that expresses the intent — it survives documents being added later. Resource ids come from Read the Semantic Layer.

Grant a group access to one folder

Open the whole Semantic Layer to a group

Response

Errors

Authorizations

x-api-key
string
header
required

API Key authentication. Format: 'x-api-key: api_key'

Body

One request handles a whole share modal.

Every recipient x every resource inside an assignment gets that level, and permission_level: null revokes. The frontend sends the diff as ONE call.

assignments
object[]
required
write-only
notify_members
boolean
default:false
write-only
message
string
write-only

Response

201 - application/json

One request handles a whole share modal.

Every recipient x every resource inside an assignment gets that level, and permission_level: null revokes. The frontend sends the diff as ONE call.

created
object[]
required
read-only
updated
object[]
required
read-only
revoked
object[]
required
read-only