RRAQOZ
Sign in

Roles guidance

Requester guide

Describe the business need clearly and submit a complete request without deciding the supplier or approving yourself.

FOR
Requester
OUTCOME
Use RAQOZ to describe the business need clearly and submit a complete request without deciding the supplier or approving yourself.

Before you begin

  • An active membership in the intended organisation.
  • The role described in this article, or administrator access for review.

Guidance

  1. 1

    State what is needed, why it is needed, quantity, timing, location and department.

  2. 2

    Attach the specification and supporting context required by your organisation's policy.

  3. 3

    Submit the request for independent approval and respond to recorded questions or returns.

  4. 4

    Track progress from the requisition record rather than creating a second request.

Evidence RAQOZ retains

  • Requisition lines and business purpose
  • Attachments
  • Submission and change history

Common issues

A screen or action is missing.

Check the active organisation, assigned role and record-specific assignment. Navigation is role-filtered, but the server-side permission check is the security boundary.

A person needs broader access for one task.

Use the narrowest supported role or governed exception. Do not share accounts or leave elevated access in place.

Related articles

Organisation administrator guideConfigure the tenant, access, controls and operating structure without becoming the default operator for every purchase.Approver guideMake attributable decisions within assigned authority and record enough reasoning for later review.

Last reviewed 2 September 2026. Review against the current production release before relying on exact screen behavior.