User Requests
Where
Sidebar
›
Client Management
›
User Requests
An approval inbox. A client's admin can ask for a new login for their own store; the request lands here, and nothing happens until you approve it. Final authority over who reaches a client's books stays with the firm.
First
Approving is not a notification you are acknowledging — it
creates the account there and then, the same account you would have created
yourself in Users by Client, with the same email
invitation.
Approve a request
-
Read the row: which client it is for, who asked, and what role they want.
-
Click Approve and confirm.
-
Quillix creates the sign-in and emails the person a link to set their own password.
Note
Approval is checked before it acts. If the username is already taken, the request has no
email address, or Quillix cannot reach the server, it refuses and tells you which of those it
was. Nothing half-creates.
Reject a request
Declines the request and records why. Nothing is created and no email is sent.
-
Click Reject on the row.
-
Type a reason if you want one — it is optional, and it is kept on the history row.
Worth writing
The reason is the only record of why the answer was no, and it stays visible
in the history below. Skipping it costs nothing today and everything in six months.
Request history
Every request that has been approved or rejected, newest first, with the date it was raised, the date you reviewed it, and the rejection reason where there is one.
-
Scroll to Request History below the pending queue.
-
Use it to check whether a login was ever asked for, and what was decided.
Scope
Approving here does not assign clients or change anyone's reach beyond the
client the request was raised for. To adjust access afterwards, use
Users by Client.
Last updated