Configures RBAC user permissions for the individual iModel. Specified permissions are assigned to the provided user.
Individual iModel permissions allow to have more granular permissions than assigned at iTwin level. This either broadens or shrinks the set of permission the user has at iTwin level. That is, once at least one user permission is configured on the given iModel, then this configuration takes precedence over permissions configured at iTwin level.
Role and User permissions are mutually exclusive and cannot be configured for an iModel at the same time.
Please refer to Access Control API to learn more about Role Based Access Control principles in general.
iModel permissions that could be assigned to the provided user:
imodels_webview - allows to view iModel in web browser, but does not allow to get its local copy and view in desktop app.
imodels_read - allows to open and view an iModel only in read-only state.
imodels_write - allows to make changes to an iModel. Allows to create and modify named versions. Allows to create mapping between PW connection and iModel to facilitate bridges.
imodels_manage - allows to manage locks, codes or local copies for the entire iModel.
User must have imodels_manage permission assigned at the iModel level. If iModel Role permissions at the iModel level are configured, then user must additionally have at least imodels_webview permission assigned at the iTwin level. If permissions at the iModel level are not configured, then user must have imodels_manage permission assigned at the iTwin level.
Alternatively the user should be an Organization Administrator for the Organization that owns a given iTwin the iModel belongs to.
For more information please refer to Account Administrator documentation section on Access Control API documentation page.
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
json
HeaderNotFound
{"error":{"code":"HeaderNotFound","message":"Header Authorization was not found in the request. Access denied."}}
The 422 (Unprocessable Entity) status code indicates that the request cannot be processed by the server due to a client error (e.g. malformed request syntax)
json
InvalidiModelsRequest
{"error":{"code":"InvalidiModelsRequest","message":"Cannot update User permissions.","details":[{"code":"MissingRequiredProperty","message":"Required property is missing.","target":"userPermissions"},{"code":"InvalidRequestBody","message":"Failed to parse request body. Make sure it is a valid JSON."}]}}
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.