Your task queue

The “Tasks” area (subtitled “My queue”) gathers all your work in one place, across all studies and sites. There is no need to walk through hundreds of casebooks by hand: the system itself shows what is waiting specifically for you, and labels every row in human terms — the subject code, the form or field title, the study code, not raw identifiers. The counter next to the “Tasks” item in the top bar is the sum across all sources available to you.

0:000:00

One queue across every study: the monitor's Queries and SDV tabs.

The queue = your permissions

The queue is computed from your permissions: an item reaches you only if you have the corresponding permission in its scope. That is why tabs appear differently for different people and are always consistent with actual access — when permissions change, the queue rebuilds itself. The subtitle says exactly that: “Work items aggregated by your permissions.”

Queue tabs

“My queue” is split into tabs — each corresponds to a type of work and appears only when you have the necessary permission in at least one scope.

Tab	What is in it	Usually visible to
Queries	queries awaiting your response or closure	CRCCRAData Manager
Signatures	forms ready for electronic signature	Investigator / PI
SDV	fields awaiting source data verification	CRA

Modules can add their own source tabs to the queue (for example, a coding queue) — using the same mechanism as the core tabs.

Queries

The “Queries” tab holds all queries where you have the right to answer (query.answer) or close (query.close). The coordinator sees queries awaiting a response here; the monitor and data manager see answered queries awaiting review and closure. Items overdue against their SLA are highlighted. Clicking a row opens the form focused on the relevant field, where the query lives. Learn more about working with queries in Queries.

Queries assigned to you personally are pinned to the top of the list with an “assigned to me” label. Assignment (the query.assign permission, usually held by a monitor or data manager) is a hint for distributing work within the team: it sets priority but grants no rights. A query can be assigned only to someone who is already entitled to work on it (query.answer or query.close in its scope) — the queue is still built strictly from permissions, and assignment merely marks whose query it is first.

Signatures

The “Signatures” tab holds forms ready to sign, if you have the signature.apply permission (usually the investigator). The signature itself is applied on the form page: from the queue you open the form and apply the signature (the signature value + re-authentication). If signing is unavailable to you, the tab is either absent or explains: “the signature queue is visible only to signatories (PI).” See Signatures.

SDV

The “SDV” tab holds fields with a “pending” verification status, if you have the data.sdv.verify permission (usually the monitor). From here the monitor goes to verify values against source documents. The full-featured tool is the SDV Workbench inside the study; the tasks tab gives a cross-cutting slice across all available sites. See Data verification (SDV).

Tip

An empty queue is a good thing: the system will say “Your queue is empty” or “Queue is empty ✓.” It means there is no work of your type right now. If the queue is long, narrow it with a study filter — the server returns the first 50 items per section, and the rest load via the “Show more” button.

How working from the queue is structured

1. Open the “Tasks” area and choose a tab (Queries / Signatures / SDV).

2. If needed, filter the list — for example, by study or “overdue only.”

3. Click an item. The system opens the canonical screen — the form with the relevant field, where the action lives in full context (breadcrumbs, neighboring fields, the right-hand panel).

4. Perform the action in place: answer the query, sign the form, mark SDV. After that the item leaves the queue.

The queue is for triage, the form is for action

The task queue and query slices are working lists for triage: filters, sorting, bulk status operations. But the substantive action is always performed on the record’s canonical screen. One object — one editing screen; lists never duplicate the data-entry form.

Quick links /go/*

Links from notification emails, from module events, or from other people’s messages often point to a record by its short identifier rather than its full address. Such links are called /go/* resolvers:

• /go/su/{subject identifier} — open a subject;
• /go/fo/{form identifier} — open a specific form instance.

Following such a link, you will briefly see “Resolving link…”, after which the system redirects you to the object’s current canonical address. This is convenient if a subject, for example, has been moved to another site: the short link will always lead to the new path.

Caution

Quick links obey the same permissions as the rest of the interface. If you do not have access to an object, the resolver will not reveal its existence — you will get a neutral “Object not found or unavailable.”