Bonus Admin Console Settings You Missed

By Kyle Knebel

April 2025 Consultants Corner

Laserfiche Administrators will love this month’s blog post. We’re going to dive into a couple of settings that you will find very useful. Let’s take a look!

Redaction Reasons

Exporting documents out of a Laserfiche repository is easy. However, sometimes, those documents contain sensitive information that you may want to obscure or hide by using redactions. Laserfiche image documents can be redacted using the built-in document editing in the Laserfiche Desktop client or Web client.

Note: Document editing within the Laserfiche document viewer is not available for electronic documents like PDF’s and MS Office documents, which need to be edited or redacted using their own editing tools outside of Laserfiche.

In addition, Laserfiche administrators can add redaction reasons to the system for end users to select when applying a redaction. Here’s how to setup Redaction Reasons.

In the Laserfiche Management console, navigate to the “Redaction Reason” tab under the General section to create a list of reasons. We’ve created a few examples here, but you can create your own.

Once created, they will be available in the Laserfiche client application when using the redaction tool.

Once the redaction is applied, a window immediately pops up with the Reason dialog box. Choose the reason, if needed.

If you double click on the applied redaction in the Client, it will show the Reason value in the Metadata tab, as seen below.

In the Desktop client, you can right-click and choose properties, as well as double clicking on the redaction.

Password Policy

Another bonus setting is the Repository Password Policy. This is found in either the Windows Administration Console or the Web Management page, depending on your preference.

For repository only users, not LFDS or Windows users, you could enable a password policy. This allows you to enforce periodic password changes, password complexity levels or a password history rule.

Work carefully here, though, since requiring a repository user to change passwords on a periodic basis will affect all of them. For example, the “Admin” user and possibly other “service” accounts you have in place, like a workflow trustee, will need to have the password changed. And for the Workflow service trustee, it can stop workflows from running if you update the password, requiring editing of all workflows that use the account.

Below is a screenshot of the dialog box in the Windows Administration console.

The safest use of these settings would be to enforce Password history and complexity, but to leave the enforcement of periodic password changes off. This would be due to the possible issue, as already mentioned, of stopping your workflows because they are possibly using a repository only account.

If you have a corporate policy on security, the complexity levels allow for preset options, or you can customize the password requirements as needed.

These same settings are available on the Web Management page.

Navigate to the Users section, then click on the “key” icon for Password Policy settings at the top right of the page.

Bonus> Bonus:

Did you know that a repository only user can manually change their own password?

They can open the Options dialog box under Tools>Options from the file menu, then navigate to the “Password” section to change their current password.