Client approvals for Jira
Get client sign-off in Jira, without exposing Jira.
Package selected deliverables, share a secure review link, and collect traceable approvals or change requests, tied to the exact revision your client saw.
Approval shouldn’t live in an email thread.
Client sign-off often happens through scattered replies, screenshots, and calls. None of it stays connected to the work in Jira, so the details that matter most are the first ones to get lost.
- Unclear which version the client actually approved
- Approval comments separated from the work in Jira
- Too much internal detail shared, or too little context given
- Change requests missed, or read differently by each person
How it works
- 01
Package the work
Select the deliverables, acceptance criteria, and attachments your client actually needs to review.
- 02
Publish a revision
Create a clear checkpoint tied to the work in Jira, so every review points to a specific version.
- 03
Share securely
Send an expiring, revocable link with its separately shared review password.
- 04
Capture the decision
Get an explicit approval or an actionable change request, recorded against that revision.
Why teams use AcceptDeck
Share only what matters
The external page shows the package details and non-draft deliverables and attachments. Items marked as drafts are excluded.
Know exactly what was approved
Every decision is tied to a specific deliverable and revision, not a chat message.
Make reviewing easy for clients
A focused page with the context and actions needed to decide, not a Jira board to learn.
Keep the decision connected to Jira
Approvals and change requests flow back into the issue, so nothing gets lost in a separate thread.
Homepage redesign, final
Responsive homepage ready for client sign-off.
You approved this deliverable.
Style guide v3
Colors, type, and reusable components.
Please update the accent color used in section 3.
A review page clients can understand immediately.
Each deliverable shows its description, acceptance criteria, and attachments, along with the current decision state and which revision it belongs to.
The client approves it, or requests changes with a comment explaining what needs to happen next.
Prepare and track sign-off where the work already lives.
Build the package on the Jira issue: choose deliverables, write acceptance criteria, attach the right files, and mark each item public or draft.
Publish a revision, share a secure link with its own expiry, and watch decisions come in against the work you already track.
External review
Give clients a focused page to review and respond.
Expires Sep 13, 2026.
Set review password
Reviewers enter the separate password before opening this link.
Controlled sharing, from link creation to revocation.
Expiring, revocable review links
Choose how long a link stays active, and revoke it immediately if plans change.
Mandatory password protection
Verified against a salted scrypt hash. The plaintext password is never stored.
Explicit public and draft visibility
Deliverables and attachments marked as drafts are filtered out of the external review page.
Permission-checked access
In Jira and Jira Service Management, AcceptDeck checks the current user’s access before reading or changing package data. External pages are authorized by their expiring link credentials.
Built on Atlassian Forge
Server-side functions run on Atlassian Forge. Packages use Jira issue properties, while revisions, preferences, link secrets, and rate-limit records use Forge-hosted storage.
Frequently asked questions
Does a client need access to our Jira project?
No. AcceptDeck gives clients a focused external review page, so they don’t need access to your Jira project. Authenticated Jira Service Management customer reviews are also supported where that fits your setup.
What can a client see?
The external page includes the package details, non-draft deliverables, acceptance criteria, and non-draft attachments. Items marked as drafts are excluded.
What decisions can a client make?
A client can approve a deliverable, or request changes with a required comment explaining what needs to be addressed.
Can review links expire or be revoked?
Yes. You choose an expiry period when creating the link, and you can revoke it from Jira at any time before that.
Is a password required?
Yes. Every external review requires a separately shared password. AcceptDeck stores a salted verifier rather than the plaintext password and creates a short-lived signed browser session after unlock.
Where is data stored?
Packages are stored in Jira issue properties. Revisions, preferences, external-link secrets, and rate-limit records use Atlassian Forge-hosted storage. AcceptDeck does not operate a separate external application database.
Turn the next client handoff into a clear decision.
Keep delivery work in Jira. Give clients a focused place to review it. Keep the approval attached to the right revision.
Start your free 30-day trial30 days, full access.