Document Acknowledgment Rate
Per RequiresAcknowledgment DocumentShare in the trailing 90 days: recipients, downloaded count, acknowledged count, percent acknowledged. Surfaces shares not landing with the right audience.
Document publishing to acknowledgment
Make a protected project document available to the intended client audience and record explicit acknowledgment.
3 stages · 0 approvals
Roles and responsibilities
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Confirm the project
Portal Manager picks which internal Projects (read from Project Management) to expose on each PortalSite via the PortalProjects line items: snapshots the ProjectName, sets DisplayOrder, marks Status: Active. A Project hidden mid-engagement flips to Status: Hidden rather than being deleted, so historical DocumentShares, ApprovalRequests, and ClientActivities keep their referential anchor for audit.
Publish the share
Project Manager publishes a document to the portal: creates a DocumentShares row pointing at the source document store FileURL (workflow-dms, Project Billing Invoices, or a Project Management deliverable), picks the PortalSite + PortalProject, sets Category (Deliverable / Invoice / Contract / Report / Reference / Other) and RequiresAcknowledgment. Once the share is published, the system identifies every ClientUser with PortalUserAccess to the PortalProject, creates an ActivityFeed row plus per-recipient MagicLinks rows with Purpose: DocumentView, and the notification service notifies each recipient with the branded template and the magic-link deep-link. ClientUsers click through, the magic-link auth handler resolves to the document viewer, the streamed download writes a DocumentDownloads row plus a ClientActivities row with ActivityType: DocumentDownloaded, and (when RequiresAcknowledgment = true) the client confirms via an in-portal action that flips DocumentDownloads.Acknowledged: true.
Protect link access
Send a recipient-bound link for the intended document and project. Store only its one-way token hash, with its purpose and expiry. The server checks current client membership and target access each time the protected document is opened. Redeem the link once and record the access event; a forwarded, expired or revoked link cannot grant access. Expired links stay in history. If another link is needed, Portal Manager issues a new one. Opening or downloading the document does not acknowledge it: the client must explicitly confirm that action.
Approvals and controls
0 approvals required in this process
- Keep the storage source private; issue authorized short-lived downloads.
- Opening a link or receiving email is not acknowledgment.
- Enforce archiveWithdrawal and access revocation through direct links.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Confirm the project | PortalProjectsPortalUserAccess | Resolve the active audience |
| 2 Publish the share | DocumentSharesDocumentDownloads | Make the permitted version available and capture client actions |
| 3 Protect link access | MagicLinksClientActivities | Redeem only valid scoped links |
Process reports
All reports
Run by an agent
Agent support
Proto cannot impersonate a client, decide a request on their behalf, disclose private source files or claim a callback succeeded without its receipt. Branding does not establish identity, authorization or regulatory certification.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› document publishing to acknowledgment · confirm the project on PortalProjects, PortalUserAccess
✓ Portal Manager picks which internal Projects (read from Project Management) to expose on each PortalSite via the PortalProjects line items: snapshots the ProjectName, sets DisplayOrder, marks Status: Active.
› document publishing to acknowledgment · publish the share on DocumentShares, DocumentDownloads
✓ Project Manager publishes a document to the portal: creates a DocumentShares row pointing at the source document store FileURL (workflow-dms, Project Billing Invoices, or a Project Management deliverable), picks the PortalSite + PortalProject, sets Category (Deliverable / Invoice / Contract / Report / Reference / Other) and RequiresAcknowledgment.
› document publishing to acknowledgment · protect link access on MagicLinks, ClientActivities
✓ Send a recipient-bound link for the intended document and project.
Other processes
3 morePortal setup to client access
Give clients a branded entry point and the specific project access their work requires.
3 stages · 1 approval
Approval request to source update
Capture the named client’s decision and reconcile the result with the originating application.
3 stages · 1 approval
Project update to client follow-up
Keep project communications relevant and follow up using permitted engagement evidence.
4 stages · 0 approvals