Configure projects, request types and context

Configure in this order

1. Service projects — enable the JSM projects whose approvals belong in the inbox.
2. Request types — choose the request types that should be available in each enabled project.
3. Context columns — choose the fields approvers need to decide without opening every request.
4. Safe Bulk policy — on Pro, add rules that must pass before a request can join a bulk decision.

Save after each change and reopen the portal inbox to verify what an approver will see.

Choose useful context

Prefer fields that answer the decision in a few seconds. Examples include:

• Hardware: employee, device, cost and department.
• Purchase: supplier, amount, cost centre and reason.
• Access: person, system, role, duration and business justification.

The app still respects the signed-in user's JSM authorisation. A configured field is not a way to expose data that user cannot access in JSM.

Plan limits

Free includes one service project and three context columns. Pro includes unlimited configured service projects and eight context columns. Free bulk operations support up to five items and ten bulk decisions per month; Pro supports up to 50 items per operation with fair-use limits.

The live Marketplace listing is the source of truth for current entitlement and price.

Configuration safety

Disabling a project or request type stops it being presented as an actionable Approval Desk item. It does not delete or change the underlying JSM request or approval workflow.