Tech Tip: Tailor Your Recycle Bin to Suit Your Needs

September 24th, 2008 Comment on this article

The Laserfiche Recycle Bin offers administrators great flexibility, with many options for protecting against accidental deletions of documents and folders in the Laserfiche repository. The feature, new to Laserfiche 8, can be disabled entirely or customized to allow or restrict a broad range of access and capabilities for Laserfiche users. The two types of configurations are determining which users can see, purge and restore items and how the recycle bin will be cleaned out.

Who Can See and Purge Deleted Items
By default, users can only see the items they send to the recycle bin. In addition, unless you specify otherwise, users cannot permanently delete (i.e., purge) recycle bin items.

  • To enable a user to purge items they originally sent to the recycle bin, grant them the Purge Entries privilege.
  • To enable users to see, purge, or restore all items, regardless of who originally sent them to the recycle bin, grant the user the Manage Entry Access privilege.

Note: This privilege also grants users the ability to grant/deny entry access rights to all documents and folders in a repository.

Periodically Cleaning Out the Recycle Bin
There are two methods to cleaning out the recycle bin.

  • Configure Laserfiche to automatically purge items after they have been in the recycle bin for a certain number of days. To use this method, open your repository in the Administration Console, expand the Recycle Bin node, right-click on Settings, select Properties, and define an Age limit.Note: In a new repository, an age limit of 7 days is set as the default.
  • Rely on your administrators to manually clean out the recycle bin. This option is best if you want an administrator to manually review each item sent to the recycle bin before it is purged. To use this method, make sure the Age limit option in the Administration Console is cleared.

For more information about the recycle bin, see the Recycle Bin Overview in the Laserfiche Administration Console help files.

Tags: ,

2 responses to “Tech Tip: Tailor Your Recycle Bin to Suit Your Needs”

  1. Add more controls to Recycle Bin Says:

    I need to be able to assign more specific access privileges to Recycle Bin users.

    We have several departments. Each department has its own folder that only members of that group can access. Every Department is also its own volume.

    The department heads need their staffs to be able to send documents to the recycle bin, cannot allow them to purge their own documents.
    Instead, each department needs to be able to assign an Administrator that will be able to review all of the documents in the Recycle Bin (that belong only to their group/folder/volume) and purge them as necessary.

    We created a folder called TRASH and set it up in each department’s root folder. Group members could move documents into that folder, but only the Administrator for the group could delete.

    This configuration worked decently in version 7.26, but it had it drawbacks. Unfortunately, it has become more difficult to administer the TRASH folders in 8.01.

    We need to be able to implement the Recycle Bin, but until we can assign more specific access privileges… we will be unable to do so.

  2. Justin Pava Says:

    You are correct that currently the recycle bin is basically all-or-nothing – you can have rights to purge your own documents, everyone’s documents, or none. The request to make it more granular has come up already, the question is just whether we would be able to tie that into the current implementation of it without making it too unwieldy.

    For what its worth, there’s nothing preventing you from setting up your own TRASH folders in 8 like you had in 7 – you just couldn’t use the built-in recycle bin in that case. I realize it’s nice to be able to use the built-in system (and we strongly encourage it for people who’s needs it meets), but if it doesn’t quite meet your needs, there’s no reason you can’t use the same mechanism you were using before.

Comment on this article