Skip to main content

SharedCredentialingSections

The NSCP shared credentialing workflow's sections, aggregated across member tenants (internal).

📄️Upload a Supporting Document for the tenants named

Stores the file once and gives each named tenant's unlocked workflows a Supporting Documents row holding it, so the page shows one document whose one file covers every tenant. Locked workflows are skipped and reported; when every one is locked, nothing is stored. Needs credentialing-workflow:details:create, details:update, details:delete and details:supporting-documents:create on every member tenant. The file is checked as the tenant upload checks it.

📄️Attach a file to every copy of a record

Stores the file once and adds it to the attachments of every copy of the record held by a member workflow that is not locked, so the page shows one version for every tenant it reached. Locked workflows are skipped and reported; when every holder is locked, nothing is stored. Only the sections whose records carry attachments take one. Needs credentialing-workflow:details:create, details:update, details:delete and details:attachments:create on every member tenant. The file is checked as the tenant attachment upload checks it: PDF, JPG or PNG, within the size limit.

📄️Edit every copy of a record

Merges the changed fields into every copy the record has, in every member workflow that is not locked; a null clears a field. With targetTenantIds the save also sets the record's holders. Needs credentialing-workflow:details:update on every member tenant, and details:create or details:delete when coverage widens or narrows (a Supporting Document widens with the upload's four permissions, details:supporting-documents:create among them; a record with attachments, whose new copies carry them, with details:attachments:create too). The response carries the record's new credentialingDisplayGroupKey.

📄️Set which tenants hold a record

Adds a copy to each added, unlocked tenant and removes the copy from each removed one; locked tenants keep what they have. Widening a system-originated record needs coverageExpansionConfirmed. Needs credentialing-workflow:details:create (widening) and details:delete (narrowing) on every member tenant; widening a Supporting Document needs the upload's four permissions instead, details:supporting-documents:create among them, and a file that is its own workflow's upload or already shared with the run. The new copies of a record with attachments carry them, which needs details:attachments:create on every member tenant too, and files that are their holders' own uploads or already shared with the run. Removed copies take their attachments with them; no file is deleted.