This release contains the following changes:

• Added the ability to schedule reports. This feature allows reports to be automatically generated and emailed to a list of recipients. More information is available in the user manual.
• The report naming scheme has been revised to ensure they are consistent and give a good idea as to what they will look

This release contains the following changes:

• Fixed problem with database upgrade that would occur if upgrading from a version prior to 7.1 (Build 4550).

This release contains the following changes:

• Added a printer filter to deny print jobs based on the number of copies.
• Fixed an issue where some common errors such as network timeouts or corrupt print jobs would be reported many times. This could cause a delay in the processing of print jobs, and in some situations crash the application server.
• Greatly improved memory usage when running PaperCut with PostgreSQL. This was a workaround

This release contains the following changes:

• Added multi-domain support for Active Directory. PaperCut can now import users from multiple AD domains without the need for workarounds, such as the use of 'nested groups'. [read more]
• Improved the reliability and performance of tracking print jobs during intermittent

This release contains the following changes:

• Added support hierarchical shared accounts (e.g. parent and sub-accounts).
• New optional advanced user client that provides enhanced functionality for selecting account. e.g. search for account, select preferred accounts, enter print job comments, etc.
• Various reporting improvements and additional shared account reports.
• Added a "Template Shared Account" that is used to define

This release contains the following changes:

• In the popup client, display information about whether the print job is color or grayscale.
• Significantly improved performance for for group-based "Bulk User Operations" (including quota allocations). The group operations now perform about 10 times faster for groups containing 2000 users.
• Provide an option to allow/disallow releasing jobs from the release station using the end-user web