Ask the local knowledge assistant
NSIPA knowledge library
Task guidance for each service and workflow stage. Local guides describe NSIPA; upstream references may describe other releases. Your account determines available actions.
531 published entries across 18 services · 64 source-linked guides
4 matching entries · Page 1 of 1
Access to Data Imports · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Check the Registry role assigned to your account.
What to do
- Sign in with the account assigned for this work.
- Ask the Registry administrator to confirm whether your account should be a Field Agent, First Reviewer or Registry Administrator.
What you need
Data Imports uses native Registry permissions for transfer.
Next step
Return to the Registry dashboard for your assigned tasks.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Data Imports access · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Understand the Registry roles that control this workspace.
What to do
- Field agents operate their own batches.
- First reviewers approve or return submitted batches.
- Administrators manage mappings and monitor transfers. Native intake edit access is required to transfer.
What you need
Manage account assignments through the authorised Registry staff controls.
Next step
Check current account assignment when an expected tab or action is absent.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Data Imports administration · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Monitor batches and manage versioned source mappings.
What to do
- Use Transfers to inspect batch status and receipts.
- Use Sources and mappings to review the active source configuration.
- Open Access to check which Registry roles can operate the module.
What you need
An administrator needs native intake edit permission to transfer approved files.
Next step
Check the source and mapping version recorded on a batch when investigating a transfer.
Published version 1 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Resolve a connected CSV fetch error · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Recover when the connection is unavailable or Data Imports cannot read the response.
What to do
- Note the selected source, error and time. Use the same Registry login and select the same source under New import. Use Fetch and validate to reopen a saved batch whose response was lost. This works from another browser, including when both browsers retry together. If the workspace asks you to choose a match, open Transfers. Select Refresh history and use the batch reference because connected batches can share a filename.
- When the batch is reopened, continue from its current status. Use Fetch a new CSV only when you intend to start a separate import from that source. Repeat that action from the same earlier batch to find its separate import. To resume the original, open it by reference in Transfers.
- If the fetch never saved a batch, use the same action again once the source is available. Ask the integration administrator to verify the endpoint, credentials and CSV response if the error persists.
What you need
The endpoint requires HTTPS and a CSV response. Integration administrators check any server-side access credential.
Next step
Continue from the existing batch’s current status. Review a draft in Reconcile records. For a batch already sent to the Registry, check or refresh its receipt in Transfers.
Published version 9 · public guidanceOpen this guide · Download plain text
Was this guide helpful?