Request confirmation
Preview one exact project scope, deliver it to the right recipient, and avoid duplicate requests.
Open People, choose Request confirmation, and inspect the preview before it leaves your control.
Check the complete request
Verify the preview shows the correct:
- Person, project, client, and proposed use
- Deliverables, channels, platforms, territory, dates, and languages
- Product category and paid or organic treatment
- AI actions and restrictions for this person
- Compensation and exclusivity treatment
- Final-approval requirement
- Revocation and takedown path
If the recipient cannot understand the request without the graph, revise the intended-use brief first.
Choose a delivery path
| Delivery | How it works |
|---|---|
| Enter the recipient, expected role, and optional message, then send the request | |
| Secure link | Copy the link and deliver it through a channel you control |
The recipient states their own role and authority basis. Their name and the role you expect them to hold do not determine authority.
Recipient outcomes
For this exact scope, the recipient can:
- Confirm
- Confirm with caveat
- Request changes
- Decline
- Report Not my authority
- Ask to be excluded from the project
The response is evidence about the presented request. It is not a signature on an unseen contract, a general release for unrelated work, or an internal production approval.
Avoid duplicate requests
Some writes can take several seconds. Wait for a definitive success or error before retrying. If delivery is pending or ambiguous, do not create a second request. Retry or reconcile the same stable request ID.
If the request dialog is lost, refresh the canonical project state and reconcile the existing request before creating another one. See Troubleshooting and the release notes for the current retry limitation.
After the recipient responds, read the three statuses separately.