01
Gather the right information
Choose the issuing identity and record the agreed information.
Use cases
Share records your partners can inspect.
Give another organization more than a screenshot or an unsupported claim: give it a signed record and relevant evidence.
Business collaboration
Business collaboration: the decision behind the check
An organizational partner needs to know which version of an approval or credential they can rely on. Give them its issuer and status context, and a clear route back to the responsible organization if the record changes.
Use cases
Business collaboration workflow
02
Make the checks visible
Let the receiving team check signatures and supporting context.
03
Keep the next step clear
Track corrections, revocations, and follow-up actions.
Details and limitations
Business collaboration: practical requirements
Who uses which workspace
The issuing business manages its records in Console and decides what its partner may inspect. The recipient can review a public proof without joining the issuer's workspace. Agree which issuer is authorized to make the statement, which version applies and how corrections or revocations will be communicated.
A focused acceptance exercise
Use one shared approval with non-sensitive data. Have the receiving team inspect the original, an altered copy and a corrected version. Check whether it can understand the result without relying on a screenshot from the issuer. Confidential attachments should remain in the agreed access-controlled channel.