An evidence permission lets a named OrderRun site ask for one exact CheckStation source context. It does not inspect or release a unit, and it does not give an Owner ordinary production-record access. Obtain the references from the responsible production or despatch team.
Enter the supplied source context
At the real site, open Team and stations and the evidence-permissions link. You need current Owner authority. Saving and withdrawing require recent Accounts verification.
Under Allow an exact evidence read, enter the intended OrderRun Receiving site ID. The organisation and production or practice environment stay the same as the source site.
Enter Source namespace, Unit reference and Source revision exactly. Each is required text of at most 80 Unicode characters without ASCII control characters. Enter the exact Context hash as 64 lower-case hexadecimal characters. These values identify the registered context, not an attempt number, a display title or an independently typed replacement revision.
The unit and current source context must exist here. Its source revision and retained context hash must match. A source update can therefore make an old proposed permission invalid before it is saved.
Save and verify the record
Give a non-blank Reason for permission of at most 1,000 Unicode characters. Choose Save read permission and inspect Permission history: Permission ID, receiving product/site, exact context, reason, recorded time and source recovery generation.
Hand the recorded permission identity and agreed source references to the receiving team through your approved process. If Evidence exchange is currently switched off, the permission does not enable that connection. Ask the responsible Owner or support to resolve the separately configured connection.
A permission authorises a question about that exact subject. Current inspection outcome, source context, holds, release and disclosure requirements are still checked when the receiving product reads evidence. Saving a permission is not a passed inspection or authority to despatch.
Withdraw a permission deliberately
Open its history entry and check the exact recipient and context. Choose Withdraw this permission, supply a Withdrawal reason and Confirm withdrawal. Inspect the retained withdrawn entry afterwards.
Withdrawal stops future reads under that permission and preserves its original history. It does not erase measurements or recall a previously downloaded copy. After a restore, a permission from an earlier recovery generation must not be assumed current; arrange the reviewed current permission and receiving configuration.
Resolve a refused or missing answer
Stay on the page when the answer is missing and use Check original receipt. Retry the same request is offered only when the original receipt is reported missing. Other permission changes remain blocked while unresolved; the private request details are held in page memory rather than browser storage.
For a definite refusal, ask the production team to confirm namespace, unit, current revision and exact context hash. Do not alter the hash or register another unit to make the permission fit. Use unit context for a genuine source correction and the OrderRun handbook for its separate operational readiness decision.