Give a department a random limit and they will fight it. Give them a limit built from their own measured usage, a balance they can check any time, and a small overdraft for emergencies - and the argument mostly disappears. This guide sets up PaperCut quotas the way that survives office politics.
A quota in PaperCut is simple machinery: each user carries a balance, every print job deducts its cost, and a scheduled allocation tops the balance up again - weekly, monthly, on the schedule you choose. The machinery is easy. The hard part is choosing numbers and settings people accept as fair. Work through this guide in order: fix the page costs first, allocate by group, set restriction with a buffer, and keep the evidence.
PaperCut does not count a quota in pages; it counts in balance. A user's Rs 300 monthly allowance buys 300 black and white pages at Rs 1, or only 60 colour pages at Rs 5. That is deliberate - it lets one number cover different printers and job types fairly. But it also means a careless page cost destroys the whole system: price colour too cheap and the quota never bites; price it too high and normal work becomes impossible. Before touching quotas, open each printer's cost profile and set simple per-page costs from your real paper and toner bills. Then print three test jobs - mono, colour, duplex - and confirm the charged amounts look sane in the job log.
Open Groups, pick a group such as Accounts, and configure its quota allocation: the amount, and the schedule - for most offices, a fixed sum added on the 1st of every month works best because it matches salary and billing cycles. Group allocation means a new joiner inherits the right limit automatically from the directory sync, and when management agrees to raise one department's allowance, you change one number, not forty accounts. Set the allocation to top up to a maximum rather than endlessly accumulating, otherwise a quiet user's balance grows for a year and then funds a month of careless printing.
On the user or group settings, set Account restriction: Restricted. A restricted user whose balance reaches zero cannot release further jobs - the job waits and the user is told why. Then add the setting that prevents most quota disasters: a modest overdraft, enough for roughly one urgent job (Rs 20 to 50 is typical). Without an overdraft, someone printing a client's urgent document at 6 pm gets blocked mid-work and the quota system gets blamed. With too large an overdraft, the limit means nothing. Keep managers and the print room itself unrestricted unless politics demand otherwise - and note that even unrestricted users are fully logged.
Arguments about quotas die when the numbers are not secret. PaperCut gives every user a personal web page (and an optional small client popup) showing their balance, their recent jobs and what each job cost. Tell staff where it is on day one. A user who can watch their own balance fall prints differently - the system becomes self-correcting instead of a police tool. It also kills the common dispute "the system charged me wrongly": the job log entry, with document name, pages and cost, is right there on their own screen.
After the first full month, open the user printing summary report and look at three things: who hit zero early, who never came close, and what the average actually is. If half the office hit zero, the allowance was set by guesswork - raise it to a level based on the measured average plus sensible headroom, and say so openly. If three people used five times the average, that is a conversation with those three people, not a reason to cut everyone. Quotas tuned once from real data and then left stable are respected; quotas changed silently every month are treated as a game.
Watch the video to see the quota allocation and restriction settings applied live on a real user group.
▶️ Watch Full VideoPaperCut works in money balance, and that is the better design: one allowance automatically covers mono, colour, A3 and duplex at their true relative costs. If you tried to run separate page limits for each type, staff would need a manual to understand their own allowance. Set honest per-page prices once, and a single balance does the rest.
For a restricted account, PaperCut stops it. With normal queues the job is denied and the user is notified; with secure release queues the job can be submitted but cannot be released until the balance is topped up. The attempt is still recorded in the log, which is useful when someone claims the printer is broken.
Three clean routes exist: the overdraft you configured absorbs small emergencies, a manager can approve a one-time balance top-up for that user in seconds from the admin console, or the job can be charged to a department shared account. What you should not do is raise everyone's quota because of one emergency - that quietly removes the limit for the whole office.