Find the HR documents stuck without a signature

The agent calls the HRlink API at your tenant address — portal.hr-link.ru by default — and reads the whole HR perimeter: documents and their printable forms, applications, employees, legal entities, departments and positions, document types, the register of local regulations and the vacation schedule. Out of those registers it assembles what people usually open them for: what is stuck without a signature, whose record has gaps and whose time off starts in the coming week.

In HR document flow the overall document status says little: signing is a route, and a delay is always personal. So the agent breaks a document down by participant and names the specific employee the wait sits with, instead of simply marking a batch as unsigned. Acknowledgement of local regulations works the same way: there is no separate acknowledged flag, there is a document on the employee's side, and the agent compares the register of regulations against document lists to find who was missed.

The agent does not write: the connection is read-only. It does not create documents, does not send them out for signing and does not sign on behalf of employees — that stays inside HRlink and with the people who hold the authority. Its output is a reconciled list: who is holding things up, what is missing from records, who still has to be caught up on the regulations, with links to the specific documents so an HR officer can close the matter in their own system.

HRlink hands its registers back in pages, and the agent reads a selection to the end: otherwise there would be exactly as many stuck documents as fitted into one response. Printable forms are pulled only for the documents actually asked about, rather than downloading the whole archive. The scope of what is visible is set by the token's owner — the agent works with the legal entities and departments open to them. It holds the request rate itself, and about missing permissions it says so directly instead of showing an empty table.