Bind Users to Roles documentgenerator.role.fillaccesses
Scope:
documentgeneratorWho can execute the method: a user with permission to modify document generator settings
The method documentgenerator.role.fillaccesses completely overwrites the mapping of roles to access codes.
The method fully overwrites the settings.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
accesses |
An array of role bindings to access codes (detailed description) |
Array Element accesses
|
Name |
Description |
|
roleId* |
Role identifier. You can obtain the identifier after creating a role or by using the get list of roles method |
|
accessCode* |
Access code for a user, group, or department. Possible values:
|
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"accesses": [
{
"roleId": 9,
"accessCode": "U1"
},
{
"roleId": 9,
"accessCode": "D1"
},
{
"roleId": 9,
"accessCode": "UA"
}
]
}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/documentgenerator.role.fillaccesses
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"accesses": [
{
"roleId": 9,
"accessCode": "U1"
},
{
"roleId": 9,
"accessCode": "D1"
},
{
"roleId": 9,
"accessCode": "UA"
}
],
"auth": "**put_access_token_here**"
}' \
https://**put_your_bitrix24_address**/rest/documentgenerator.role.fillaccesses
try
{
const response = await $b24.callMethod(
'documentgenerator.role.fillaccesses',
{
accesses: [
{
roleId: 9,
accessCode: 'U1'
},
{
roleId: 9,
accessCode: 'D1'
},
{
roleId: 9,
accessCode: 'UA'
}
]
}
);
const result = response.getData().result;
console.log(result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service->core->call(
'documentgenerator.role.fillaccesses',
[
'accesses' => [
[
'roleId' => 9,
'accessCode' => 'U1',
],
[
'roleId' => 9,
'accessCode' => 'D1',
],
[
'roleId' => 9,
'accessCode' => 'UA',
],
],
]
);
$result = $response->getResponseData()->getResult();
var_dump($result);
} catch (Throwable $e) {
echo $e->getMessage();
}
BX24.callMethod(
'documentgenerator.role.fillaccesses',
{
accesses: [
{
roleId: 9,
accessCode: 'U1'
},
{
roleId: 9,
accessCode: 'D1'
},
{
roleId: 9,
accessCode: 'UA'
}
]
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'documentgenerator.role.fillaccesses',
[
'accesses' => [
[
'roleId' => 9,
'accessCode' => 'U1',
],
[
'roleId' => 9,
'accessCode' => 'D1',
],
[
'roleId' => 9,
'accessCode' => 'UA',
],
],
]
);
print_r($result);
Response Handling
HTTP Status: 200
{
"result": null,
"time": {
"start": 1773914210,
"finish": 1773914211.747039,
"duration": 1.7470390796661377,
"processing": 1,
"date_start": "2026-03-19T12:56:50+02:00",
"date_finish": "2026-03-19T12:56:51+02:00",
"operating_reset_at": 1773914810,
"operating": 1.222714900970459
}
}
Returned Data
|
Name |
Description |
|
result |
The method applies the new bindings and returns Also returns
|
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400, 403
{
"error": "0",
"error_description": "You do not have permissions to modify settings"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Status |
Code |
Description |
Value |
|
|
|
Required field "ROLE_ID" is not filled |
In one of the |
|
|
|
Required field "ACCESS_CODE" is not filled |
In one of the |
|
|
|
You do not have permissions to modify settings |
Insufficient rights to modify document generator settings |
|
|
|
Your plan does not support this operation |
The plan does not allow for permission differentiation for the document generator |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Add Role documentgenerator.role.add
- Change Role documentgenerator.role.update
- Get Role by ID documentgenerator.role.get
- Get the list of roles documentgenerator.role.list
- Delete Role documentgenerator.role.delete