Back to features
Feature deep dive

Digital Credentials

Sign, stamp and request credentials on documents

Sign or stamp PDF, DOC and DOCX documents directly, or send secure signing and stamping requests to recipients with placeholders, access codes, signing order, tags and audit tracking.

Ofisync dashboard preview for Digital Credentials
ofisync.app / digital-credentials

Credential vault

Signing packet ready

3 documents merged
Strict order enabled
Recipient fields placed

Live business context

Sign or stamp PDF, DOC and DOCX documents directly, or send secure signing and stamping requests to recipients with placeholders, access codes, signing order, tags and audit tracking.

Sign
Stamp
Send

Why it matters

Every signature and stamp is placed where the document needs it.

Digital Credentials in Ofisync supports two practical flows: Sign/Stamp Documents for users who need to place their own stamps or signatures, and Get Signatures/Stamps for documents that must be completed by recipients. Documents can be uploaded, merged, prepared with drag-and-drop fields, previewed, shared, downloaded and audited through the full credential process.

Legal teamsFinance teamsOperations teamsApprovers

Let users place stamps and signatures on documents quickly, then preview, download or share the finished file.

Collect signatures and stamps from as many recipients as needed with secure access and optional sequential signing.

Keep every credential request searchable, tagged, entity-linked and backed by a detailed activity audit.

Guided workflow

From setup to daily execution.

1

Choose the credential flow

Start with Sign/Stamp Documents for direct placement, or Get Signatures/Stamps when recipients need to complete the document.

2

Upload and place fields

Upload one or more PDF, DOC or DOCX files, merge them into one document when needed and drag signatures, stamps or recipient placeholders into the exact positions.

3

Preview, send and track

Preview the prepared document, download or share it directly, or send it to recipients with secure access, signing order and audit tracking.

Credential flow fit

Built around direct signing and recipient-driven completion.

A user may need to stamp a document immediately, or send a multi-page packet to several people for signatures in a strict order. The document must show exactly where each person should sign or stamp, protect recipient access, notify each signer at the right time and keep an audit of every action.

Users lose time printing, scanning or manually editing documents just to add stamps and signatures.
Multi-document signing packets are difficult to manage when every file is handled separately.
Recipients need clear signing positions, secure access and private instructions without exposing the wrong information.
Sequential signing becomes hard to control when the next recipient should only receive the document after the previous person has completed their action.
User story

How Digital Credentials works in practice.

1

Scenario 1

The user chooses between two credential flows

Digital Credentials starts with either Sign/Stamp Documents or Get Signatures/Stamps. The first flow is for users placing their own stamps or signatures directly. The second flow is for collecting signatures, stamps or other required actions from recipients.

2

Scenario 2

Direct signing starts with uploaded files

For Sign/Stamp Documents, the user uploads a PDF, DOC or DOCX file. If there are multiple files, Ofisync can merge them into one document so the user works on a single signing packet.

3

Scenario 3

Stamps and signatures are placed visually

The user drags and drops stamps or signatures directly onto the document. Placement is explicit, so the signed output shows the credential exactly where the user intended it to appear.

4

Scenario 4

The signed document can be previewed, downloaded or shared

After placement, the user can preview the signed document, download it or share it. If something is wrong, the user can correct the document, replacing the relevant fields based on the original uploaded file or files.

5

Scenario 5

Requesting signatures starts with recipients

For Get Signatures/Stamps, the user uploads the document or documents, merges them when needed and then adds recipients. Each recipient can have a name, email, optional phone number, required action, access code and private message.

6

Scenario 6

Recipient actions define what each person must do

A recipient can be marked as Needs to sign, In-Person Signer, Receives a copy or Needs to View. This lets the sender include signers, viewers and copy recipients in the same credential process.

7

Scenario 7

Fields are placed for the correct recipient

The user places the relevant signature, stamp or input placeholders for each recipient on the document. This tells every recipient exactly where to add the required signature, stamp or action.

8

Scenario 8

Strict signing order controls the sequence

When strict signing order is enabled, recipients receive the document sequentially. The second recipient only gets access after the first recipient completes their action, and the process continues until the packet is complete.

9

Scenario 9

Secure messages and access protect the request

Recipients receive an email or message with encrypted access credentials. An optional access code adds another layer of security, and private messages let the sender give recipient-specific instructions.

10

Scenario 10

The credential packet remains searchable and auditable

Credential documents can be tagged, associated with entities and searched quickly. Ofisync keeps an audit of signing activity, field placement, recipient actions, status changes and completion events until the document reaches complete status.

Credential scenarios

Where signatures and stamps move without printing.

Credential scenario 1

Direct sign and stamp

A user uploads a PDF, DOC or DOCX file, places signatures or stamps by drag and drop, previews the signed result, then downloads or shares the completed document.

Credential scenario 2

Multi-recipient signing packet

A user uploads one or more documents, merges them into a single packet, adds recipients, places each recipient's fields and sends the packet for completion.

Credential scenario 3

Strict signing order

When signing must happen hierarchically, recipients receive the document sequentially so the second signer only receives it after the first signer has completed their action.

Recipient actions can include Needs to sign, In-Person Signer, Receives a copy or Needs to View.
Recipients can have a name, email, optional phone number, access code and private message.
Credential packets can be linked to entities such as clients, files, projects, users and other records.
Users can duplicate a document packet and adjust passed parameters instead of starting again.

Inside the credential workspace

A secure workspace for preparing and completing signed documents.

The credential workspace keeps uploaded documents, merged packets, placed fields, recipients, access codes, private messages, entity links, tags, status, previews and audit activity connected to one signature process.

Document senders

Uploaded files, merged packets, recipient setup, field placement and send status

Recipients

Secure access, required actions, private messages, signing fields and completion

Approvers

Strict signing order, status changes, audit trail and completed credential packets

Credential records

What stays attached to each signing packet

Uploaded PDF, DOC and DOCX files merged into signing packets
Placed signatures, stamps, recipient fields and other required inputs
Recipients, required actions, emails, optional phone numbers and access codes
Private recipient messages, strict signing order and packet title or message
Entity links, tags, search metadata, preview state, downloads, shares and completion status
Audit events for field placement, recipient access, actions, corrections and completion

Signing movement

Actions Ofisync can prepare during credential completion

Merge multiple uploaded documents into one signing packet
Send recipient emails based on strict signing order when enabled
Hold later recipients until previous required signers have completed their action
Update document status to complete after all required actions are finished
Keep corrected documents aligned with the original uploaded file fields
Duplicate an existing credential packet so users can adjust parameters and resend faster

Credential view

Credential packet status

Track draft, sent, waiting, in-progress and complete packets across direct signing and recipient-driven signing flows.

Credential view

Recipient action trail

Review who received the document, what action was required, when they accessed it and when they signed, stamped, viewed or received a copy.

Credential view

Credential search

Find signed and pending credential documents by title, tag, entity, recipient, status and other available signing metadata.

Ready to see it live?

Walk through Digital Credentials with an Ofisync specialist.

We will map the demo around your business workflow, show the connected modules and help you identify the fastest path to rollout.

Request Demo