
Only admins can submit orders and complete payment
Before this change, any org member who could access the service request flow could also complete payment and create an invoice — with no check on whether they had the authority to do so.

Before this change, any org member who could access the service request flow could also complete payment and create an invoice — with no check on whether they had the authority to do so.
Non-admin members can still browse the full service request flow: configure a project, select deliverables, and review pricing. At the payment step, they now see an Admin Approval Required message in place of the payment form, along with guidance to contact their org admin to complete the order.
Only members with an Admin or Super Admin role on the org can submit an order and finalize payment. If you are an admin, the flow works exactly as before — review the order summary and complete payment at step 4. If you are unsure of your role, an admin on your account can check and update it from the Members tab in your org settings.
This control applies at both the interface and the system level. Even if a non-admin member reaches the payment step through an unexpected path, the order submission is blocked and returns an access error. No invoice is created.