Apps & Keys
How to enable the partner credential, which method to choose, and how to store the secret in your backend.
Operational guides
Practical guidance for enabling integrations, operating users from the UI, using custom domains, and aligning branded communications.
Not everything is a public endpoint
Daily Signly operations combine the partner API with flows managed from the administrative app. These guides focus on what is currently handled through the UI or with Signly team support.
Guides you should review
Templates and documents
Best practices for versioning, field structure, participants, and deadlines.
Users and roles
Administrative management of users, roles, and permissions currently happens mainly inside Signly App UI.
Root user and operations
Who should own the primary account, how to delegate access, and how to separate responsibilities.
Custom domains
Considerations for branded domains, DNS, certificates, and the signer final experience.
Communications and SSO
Branding for emails and messages, plus a view of SAML/SSO as a future-facing capability for enterprise accounts.
Recommended operational playbook
- Define a custodian `root user` that does not participate in daily operations or share credentials.
- Create named users for legal, operations, and administration; avoid generic accounts.
- Use roles to separate governance, operations, and support before enabling the partner integration.
- Version templates before changing fields in production and validate the final PDF with the functional team.
- If you enable custom domains or communications, coordinate DNS, branding, and delivery tests before go-live.
- When SAML/SSO applies, treat it as an enterprise project track rather than a basic quickstart prerequisite.
What you should not model as a public API today
- Frontend login, logout, refresh token, and password recovery.
- Full internal user administration if your team only integrates M2M signing.
- Enterprise SSO/SAML, because it is still an assisted capability rather than a finalized public reference.
Proper escalation
If you are an enterprise customer, active partner, or account under onboarding, use the official channel to request help with architecture, custom domains, communications, or production rollout.