Staff request queue
/compliance-requests is available only to staff explicitly assigned to a request profile's restricted-handler perimeter. It is not a general CRM list: rows in this queue must not appear in ordinary search, feed, or exports. Open a request at /compliance-requests/:opportunityId.
The shell locale is not proof that the queue is fully localized: the current
frontend inherits Russian complianceStaffUi labels and actions for kk and
ky. Keep the three queue/recovery screenshot targets planned and source-gated
until native dictionaries and same-locale review pass. For checks, use only a
human-readable synthetic request recorded in the setup; do not present its name
as an already seeded record. No PII, secrets, or raw IDs.
Queue and profile
The page loads profiles you handle. Choose a profile when more than one is available. The table shows a safe request title, received date, lifecycle, and a due indicator. Each cursor page contains up to 50 rows; use Load more while another page is available. An empty queue means no rows are available in this perimeter, not that other profiles have no requests.
If a profile is unavailable or the handler capability is denied, retry or contact the profile owner. Do not bypass the restriction with a direct URL. A request ID is not a delivery secret and does not open its content by itself.
Request card
The card shows the profile, submitted fields, received time, lifecycle, and the due indicator. Some values can be empty; do not copy them into a shared chat. Work lists existing handoff tasks. Routing creates a normal task for a selected staff member with instructions and deadline context. Verify the assignment in the task after routing; the task must not expose the request outside its permitted perimeter.
The routing dialog requires a task title and assignee. The instruction is optional and capped at 8,000 characters; the deadline context is optional and capped at 500. Retrying the same handoff is safe: its idempotency key replays the already-created task instead of creating a duplicate.
Clock and lifecycle
The due indicator displays the lifecycle (received, routed, responded, or another profile state), timezone, and due date when present. List labels use calendar days rather than elapsed working hours: due today and overdue are distinct, dates within seven days are warned, and paused or completed (responded) requests have their own state. A handler can pause, resume, or extend the clock only with an approved reason and a reference to its grounds. Extension defaults to 14 days and must be at least one day. This changes operational tracking; it is not proof of a statutory deadline and does not replace a DPO or legal decision.
Protected response
Response shows the delivery decision, expiry, and one-time-secret status without exposing the secret itself. If recovery is allowed, the existing session's code is rotated: the previous code stops working immediately and no second response is minted. Recovery attempts are bounded; the control is unavailable when none remain. The new secret is shown once in the current tab, and the dialog must be acknowledged as saved before it can be closed. Never place it in a URL or screenshot. If a document is attached, legal hold can be enabled on a specific revision. Evidence export creates a package supported by the configured process; it is not automatically an audit or legal package.
Privacy and boundaries
The server checks the restricted perimeter on every request; do not work around a 403 by resubmitting. Use synthetic data for training and visual review. Never publish request IDs, applicant names, delivery codes, document contents, or currency data. The queue supports an internal process, but LadVen OS does not itself verify identity, guarantee a regulatory deadline, prove deletion, or turn a task into legal advice.
Related sections