Access-Controlled Recipient Delivery
Know exactly who saw your document and when.
Delivers a specific artefact to named recipients via a permissioned link or portal, then tracks who viewed, downloaded, or forwarded it. Expiry and revocation are built in — you stay in control after sending, replacing email-and-attachment with visible, revocable delivery.
Shape
Operational dimensions
Each output waits on a human decision.
Fires when an upstream condition occurs.
Light state; replaceable any time.
Emits to external systems; does not read them.
Inputs
- artefact (document, deck, video, file, dataset)
- named recipient list with permission level
- expiry and revocation policy
- optional watermarking or download restrictions
Outputs
- recipient-scoped access grant (link / portal page)
- per-recipient view / read / download event stream
- revocation and expiry state
- delivery audit log
Mechanism
Delivers a specific artefact to specific named recipients via an access-controlled link / portal, with permission, view/read tracking, expiry, and revocation — the delivery+access primitive distinct from publishing a surface.
Why this is a primitive
Cannot be decomposed — the operation is one act of point-to-named-recipient delivery with access control: identify recipients, grant scoped access (link / share / portal), track view / read / download events, expire and revoke. Strip access control and you have a public publishing surface; strip recipient targeting and you have a broadcast list; strip view tracking and you have a file dropbox. The combination of named-recipient + permissioned + tracked is what the buyer pays for.
Where it shows up
Related primitives
Tags
See where it fits.
Primitives are configured into named solution shapes for each client’s domain. The fastest next step is a conversation about which shape fits your problem.
Start a conversation