Rejecting a Request and Giving a Reason
Reject when the change should not go ahead. On the list, declined items show status Rejected (red) and can include a Review note.
Why the Rejection Note Matters
The note is how Daniel Murphy knows what to do next. It also stays on the card for later review.
A useful note:
- Says why you declined
- Says what to change on a new request
- Avoids the same mistake twice
Good:
Rejected because the requested credit is too high. Please submit a request for up to 100.
Avoid:
No.
The current screenshot shows Review note on a rejected Wallet Credits card.
Workflow — Reject
Step 1 — Open the pending request
Open Approvals → Permission Requests → Pending.
Step 2 — Review
Read the action and reason.
Step 3 — Reject
Use Reject if Fitnez Studio shows it.
Step 4 — Enter a clear review note
Explain the decline in language the requester can use.
Step 5 — Confirm
Complete any confirmation.
There is no screenshot of the Reject control. Whether a note is required is not confirmed. Cards can show Review note after the decision.
What Happens Next?
The requester should see Rejected and the Review note. The original change should not apply. They can submit a new request if still needed. See Tracking Your Requests.
Do not bypass a rejection by editing the wallet another way unless your role allows a direct change and studio policy agrees.