Approval Desk – Bulk Approvals for JSM — Terms of service

1. Service

Approval Desk – Bulk Approvals for JSM is a Jira Cloud application that presents native Jira Service Management approvals assigned to the signed-in user and supports individual or confirmed bulk decisions. It is a focused workflow layer, not a replacement for JSM permissions, workflows or request history.

2. Authorised use

Install and use Approval Desk only in a Jira site you are authorised to access and only for legitimate service-management work. You are responsible for ensuring that an approver has the organisation's authority to make the decision.

3. Native approval boundary

Approval Desk sends approve and decline actions through the official JSM approval API in the signed-in user's context. It does not elevate permissions, change JSM workflows, modify request content or create a second approval record. Jira is the source of truth for the resulting decision.

4. Bulk safety and results

Bulk actions require an explicit, count-specific confirmation and are re-checked before execution. Safe Bulk policy evaluation fails closed when it cannot be verified. A bulk operation may produce a partial result when items have different outcomes; the app will distinguish successful decisions, approvals already completed elsewhere and technical failures.

5. Plans and billing

Approval Desk may provide Free and Pro entitlements. Current limits, features and prices are the ones shown on the Atlassian Marketplace listing. Atlassian Marketplace manages billing, taxes, subscription status and cancellation. NarrowForge does not ask for or store payment-card details.

6. Customer responsibility

You are responsible for reviewing the request context, confirming that the decision is appropriate and following your organisation's approval, privacy and retention policies. A request marked Individual review required may still be approvable one at a time; that message only means it was not safe to include in the selected batch.

7. Acceptable use

• Use the product for its documented purpose and within the limits of your plan.
• Do not attempt to access another Jira site or another customer's data.
• Do not probe, overload or bypass technical, security or commercial limits.
• Never send passwords, API tokens, credentials or unnecessary request content through support.

8. Availability and changes

The service depends on Jira Cloud, Atlassian Forge and JSM APIs. Permissions, rate limits, stale approvals and temporary platform failures can prevent an action from completing. Approval Desk should show that state rather than presenting an uncertain result as a success. Meaningful product changes are published in the changelog.

9. Privacy and contact

Data handling is described in the Approval Desk privacy policy. Questions: support@narrowforge.com.

Last updated: 2026-09-09.