Does the recipient need an account?
No for standard recipient journeys. The invitation opens the action that the person must complete.
FREQUENTLY ASKED QUESTIONS
Straight answers about SignCloud.
This overview clarifies which product to use, what evidence is produced, how recipients access a journey and which functions are publicly available.
Use the control that matches the real need. Keep the result understandable and exportable.
Signature, Identity and Mail remain separate products and connect when the workflow requires it.
WHAT YOU CAN DO
The questions teams ask before starting
Choose the capabilities that match your workflow and keep every step easy to understand.
Can products work separately?
Yes. Signature, Identity and Mail can be used independently and connected later through the same account.
Is every feature a qualified service?
No. SignCloud states the actual control and identifies qualified third-party services only when they are explicitly used.
FROM ACTION TO EVIDENCE
A clear result for every step.
Compare the product used, the control applied and the result returned at each step.
| Need | Availability or product | Control | Output |
|---|---|---|---|
| Which identity method? | Choose NFC, camera or let the person choose | Identity | One verification result |
| Can I sign face to face? | Yes | Signature and supported apps | Session and signature evidence |
| Can I prove an acknowledgement? | Yes | Acknowledgement report | |
| Are iOS and macOS public? | Not available | No public access | No download available |
Need a precise scope? We map the expected result, controls and evidence before deployment.Talk to SignCloud →
READY FOR A REAL WORKFLOW
Start with the outcome you need.
We will identify the right SignCloud product, recipient journey and evidence level for your use case.