POST
/
updatepermissions
curl --request POST \
  --url https://{domain}-be.glean.com/api/index/v1/updatepermissions \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "datasource": "<string>",
  "objectType": "<string>",
  "id": "<string>",
  "viewURL": "<string>",
  "permissions": {
    "allowedUsers": [
      {
        "email": "<string>",
        "datasourceUserId": "<string>",
        "name": "<string>"
      }
    ],
    "allowedGroups": [
      "<string>"
    ],
    "allowedGroupIntersections": [
      {
        "requiredGroups": [
          "<string>"
        ]
      }
    ],
    "allowAnonymousAccess": true,
    "allowAllDatasourceUsersAccess": true
  }
}'

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Describes the request body of the /updatepermissions API call

​
datasource
string
required
​
permissions
object
required

The permissions that define who can view this document in the search results. Please refer to this for more details.

​
objectType
string

The type of the document (Case, KnowledgeArticle for Salesforce for example). It cannot have spaces or _

​
id
string

The datasource specific id for the document. This field is case insensitive and should not be more than 200 characters in length.

​
viewURL
string

The permalink for viewing the document. Note: viewURL is a required field if id was not set when uploading the document.'

Response

200
_mintlify/placeholder

OK

Was this page helpful?

Suggest editsRaise issue