How app requests work

What you get

Software bought on purpose instead of on a card — the thing that stops next year's shadow IT before it starts.

Two kinds of request

Access — someone wants a licence for a tool the organisation already has.

Procurement — someone wants a tool the organisation does not have yet.

Both arrive in one queue, on separate tabs, and both leave a record: who asked, who approved, and when.

The employee's side

Apps Catalog is the employee-facing place to find available software and request access. Use Recommended to start with the apps surfaced first, All Apps to search the catalogue, and the request-status view to track what you have asked for. Request Access on an app starts the access-request process.

Apps Catalog with recommended apps and Request Access

The approver's side

App Request holds the queue — App Requests for access, Procurement Requests for new tools — with approve and reject inline.

Why it matters for spend

Every request leaves a structured record of what was requested, who asked and how it was resolved. That gives the reviewer a clear place to check whether the organisation already owns something that does the same job before approving another purchase.

What you've unlocked

Next: Submit a request