For AI agents: markdown of this page — /docs-content-en/workday/time-control-users.md documentation index — /llms.txt
Time-control employees
GET /v1/workday/time-control/users?departmentId=1 calls timeman.timecontrol.reports.users.get with DEPARTMENT_ID. A positive departmentId is required. Response: { success: true, data: [...] }, with camelCase user keys. Bitrix24 decides which employees are visible. Every response triggers a department.get lookup: a nonexistent department yields 404 ENTITY_NOT_FOUND; an existing department with no visible employees yields an empty list. The upstream credential must allow department reads for this check; an access error is never treated as a missing department.
Access and errors
Key scope: timeman. Bitrix24 enforces user permissions. 400 INVALID_PARAMS means invalid input; 403 means missing scope or Bitrix24 permissions; writes with a READONLY key return 403 WRITE_BLOCKED_READONLY_KEY; 409 TIMEMAN_MODULE_NOT_ENABLED means unavailable Time Management; 422 BITRIX_ERROR forwards a Bitrix24 business refusal with its text. Webhook credentials are scrubbed from responses.