Signings guide

A signing in Krebit Sign is a coordinated package that groups one or more documents with the people who must review or approve them. Each package tracks routing rules, notifications, reminders, and completion history so you can orchestrate legally binding agreements from a single control surface.

How signings are structured

Every signing stores:

• Identity – A human-friendly name, language preference (English or Swedish), and an optional message that explains the purpose of the package.
• Routing rules – A parallel or sequential signing order that determines how invitations are delivered, plus optional approver-only steps.
• Audit state – Draft, in-progress, completed, and cancelled timestamps that tell you exactly where a package sits in its lifecycle.
• Relationships – Linked recipients and documents, including the order in which each recipient participates and the documents they can access.

Krebit Sign keeps these pieces synchronized so that everyone sees the latest version of the signing, whether you are managing it from an internal tool or programmatically.

Lifecycle overview

1. Draft – Assemble documents, craft the message, and add recipients. Drafts are fully editable until you decide to send them.
2. Sent – Invitations go out instantly. Parallel signings notify everyone (approvers first when present), while sequential signings invite one person at a time.
3. In progress – The platform records each view, decision, and reminder so operators can step in when someone stalls.
4. Completed or cancelled – Finished packages unlock sealed PDFs for download. Cancelled signings freeze activity but retain their audit trail for compliance.

Reminders can be issued in bulk or per recipient and respect the 14-day invitation window. Cancelling a package immediately revokes active links and notifies anyone who already received an email or BankID request.

Recipient experience

Recipients—signers, approvers, or viewers—are identified by UUID and include rich contact information. You can:

• Choose signing methods such as BankID, email, or approval-only acknowledgement.
• Capture optional attributes like phone numbers or national identifiers when specific signing methods require them.
• Control ordering with numeric positions to model sequential flows or prioritize approvers before signers.
• Monitor activity counts to understand who has viewed, approved, or declined a document.

Sequential flows advance automatically after each recipient completes their step; parallel flows allow everyone to act as soon as they receive an invitation.

Document handling

Documents remain central to each signing:

• Upload rules – Only PDF files under 10 MB are accepted, and they must not be password protected or previously signed. Uploads use multipart form data with the selected_file field.
• Version safety – Drafts allow you to add, reorder, or remove documents without impacting recipients. Once sent, documents are locked to preserve the audit trail.
• Download options – Originals remain available throughout the lifecycle. Sealed PDFs appear once every required decision is captured; until then, requests for signed versions return 404.

Operational controls

Krebit Sign surfaces clear signals that help your teams run reliable signing operations:

• Status fields (is_draft, is_completed, cancelled_at) show whether action is required.
• Cancellation metadata captures the reason and timestamp so you can communicate clearly with stakeholders.
• Reminder endpoints return contextual messages when a recipient cannot be reminded (for example, already completed or never invited).
• Pagination metadata lets you build dashboards that highlight active, overdue, or recently finished signings.

Working with the API reference

The generated API reference in the sidebar documents every request and response schema for signings, recipients, and documents. Combine the conceptual guidance in this page with those endpoint details to implement integrations that are both intuitive for operators and resilient in production.