NF / Support / Atlassian
Approval Desk support
Practical help for the native JSM approval inbox: install it, configure the context your approvers need and process decisions without losing sight of what Jira recorded.
Support actions
What we support
A shorter path to a confident decision.
- Installing Approval Desk from Atlassian Marketplace
- Selecting service projects, request types and context columns
- Reading request context in the JSM customer portal
- Individual approve and decline actions through native JSM
- Bulk confirmation, Safe Bulk checks and partial results
- Free and Pro entitlement boundaries
Decision boundary
What Approval Desk does not do.
It does not replace native JSM workflows, elevate a user's permissions or invent a second approval record. A decision is sent through the signed-in user's native JSM approval access.
Bulk checks fail closed when the approval or policy cannot be verified. A request that says Individual review required may still be approvable one at a time; the batch was simply not safe to include.
Help topics
Find the answer you need.
Install and understand permissions
Install from Marketplace and see why Approval Desk uses the signed-in JSM user's context.
Read guideConfigure decision context
Choose service projects, request types and the fields approvers need before deciding.
Read guideReview one approval
Read the inbox, open the native JSM request and complete an individual decision safely.
Read guideProcess a batch
Select compatible requests, confirm the exact consequence and interpret every result.
Read guideUnderstand Safe Bulk
Learn why a request may need individual review and how fail-closed checks protect decisions.
Read guideFree and Pro
Compare project, context-column and bulk-decision limits before you choose a plan.
Read guideTroubleshoot a decision
Resolve stale approvals, missing requests, JSM links, limits and partial results.
Read guidePrivacy and security
Read the exact data boundary, storage model and native-permission guardrails.
Read guideBilling and uninstalling
Understand Marketplace billing, deletion and what remains in native JSM after uninstall.
Read guideReference index
Every article, in one place.
- Getting started
Install Approval Desk and make your first native JSM approval decision with confidence.
- Installation and permissions
Install from Atlassian Marketplace and understand the permissions Approval Desk uses.
- Configure projects, request types and context
Set the scope of the inbox and show approvers the fields needed for a decision.
- Reviewing an approval
Read the inbox, open request context and complete one decision through native JSM.
- Bulk approvals and results
Select several compatible approvals, confirm the exact consequence and understand every result.
- Safe Bulk policy
Understand eligible, blocked and uncertain requests before processing a batch.
- Free and Pro
Compare the approval inbox, configuration and bulk decision limits in each plan.
- Troubleshooting
Resolve loading, permission, stale approval, link, limit and partial-result problems safely.
- Privacy and security boundary
See what Approval Desk reads, stores and never changes in Jira Service Management.
- Billing and entitlement
Understand Free and Pro billing, limits and where subscription questions are handled.
- Uninstalling and deletion
Remove Approval Desk from a Jira site and understand what happens to app data.
FAQ
Questions, answered plainly.
Does Approval Desk replace native JSM approvals?
No. It presents pending native Jira Service Management approvals in a focused inbox and sends the decision through the signed-in user's existing JSM approval permission.
Approval Desk – Bulk Approvals for JSMWhat can an approver see before deciding?
The request title, type, requester, age and the fields the administrator configured for that request type — for example cost, department, supplier or reason — subject to what the signed-in user is authorised to see in JSM.
Approval Desk – Bulk Approvals for JSMWhat happens when a bulk operation is only partly successful?
Approval Desk keeps the result split into successful decisions, approvals already completed elsewhere and technical failures. The remaining items stay actionable for individual review or retry.
Approval Desk – Bulk Approvals for JSMCan an administrator control where the inbox looks?
Yes. Administrators choose service projects, request types and the context columns shown to approvers. Pro also includes Safe Bulk rules that fail closed when a rule blocks or cannot be evaluated.
Approval Desk – Bulk Approvals for JSMDoes it change Jira permissions or request data?
No. It does not change JSM permissions, workflows or request content. Approvals are answered through the native JSM API, and the app stores only tenant configuration and minimal bulk-operation metadata.
Approval Desk – Bulk Approvals for JSMWhat is included in Free and Pro?
Free includes the inbox, one service project, three context columns, individual approvals and up to five items per bulk operation within the monthly limit. Pro adds broader configuration, eight columns, up to 50 items per operation and Safe Bulk controls. See the live Marketplace listing for current limits and prices.
Approval Desk – Bulk Approvals for JSMTrust and privacy
Know the boundary before you install.
Approval Desk runs on Atlassian Forge, keeps tenant configuration isolated and uses the signed-in user's JSM permissions for request context and approval decisions.
NF / Direct support
Still need a hand?
Tell us the Jira site, Approval Desk version, request key or operation id, approximate time and exact message. Never send passwords, API keys, access tokens or full request exports.