Use Response Hub to find, handle and review responses

Open Response Hub → Responses to work with a library's deployed service responses. Choose QA or Production first, then the service. User view/Prototype responses are not part of this workspace.

Check access and choose the workspace

A library administrator enables Response Hub in Security settings. Production follows the library's Live data access boundary. A missing link can reflect the library setting, entitlement, permissions or environment.

Area	Use it for
Summary	Submitted-response totals, activity and selected field summaries.
Responses	Search/filter/sort submitted responses, choose answer columns and saved views, and select work to inspect or export.
Awaiting payment	Accepted unpaid answers for payment-enabled services. These have not been submitted; see payment recovery and casework.

The service list includes services with no submitted responses so unpaid-only work can still be reached. Disabling a service's payment setting hides its Awaiting payment link but does not complete existing unpaid responses.

Find and organise work

Use search, submitted-date and processing filters, sort order and selected answer columns. Save useful views for recurring work. Team handling provides owners, operational statuses, tags and internal notes for submitted versions; it is unavailable for accepted unpaid answers.

An operational status or owner helps the team organise work. It does not change the respondent's answers or establish that an external integration succeeded.

Inspect answers, history and files

Open a response to view answers using the form revision saved with that submission. Response history preserves submitted versions and amendment evidence. Choose the intended revision when inspecting files or Bulk Data artifacts; current draft data can differ.

Integration results → View action results opens the authorised audit view for the chosen environment and response. Detailed results can expire, and history may cover several submissions. Processed means automated processing finished, not that the destination accepted the request. Check the result and destination separately.

Review and return for changes

For services requiring review, staff claim responses, add shared correction instructions/issues, accept or return them. Internal notes remain staff content. Enable this through Response review settings; a workflow Review action is a separate feature.

Export the intended responses

Export selected responses or the current filtered set. Larger exports run as jobs; keep the chosen filters and version scope clear. Recent exports shows up to ten jobs, with completed downloads available for 24 hours. Expiry of a download does not itself delete the response evidence.

Exports remain subject to environment access and the library's live-data export setting. Submitted-data APIs exclude accepted unpaid responses until receipt, a recorded outside payment or a waiver submits them. Respondent Excel/CSV answer downloads have separate settings.

For expected organisations, assignments, reporting periods and deadlines use Collection programmes. For performance investigation use Analytics, Audit log and User data view.