Browse Password, Document Permissions, and List Sorting Guide

Use this guide to understand three practical control tools in QBM: browse password, document-level permissions, and sorting or list layout behavior.

Overview

QBM includes several small control tools that help administrators and users protect information and work faster. These tools are not a replacement for security groups, but they support daily work by controlling access to specific documents, requiring a browse password where configured, and allowing users to sort lists in a useful order.

Browse Password

Typical path: Options > Browse Password or the related button in the Options window.

The browse password is a company-level password used by workflows that require additional confirmation before browsing or accessing protected information. The reset dialog asks for a new browse password and confirmation.

Field / ActionWhat It MeansUser Guidance
New Browse PasswordThe password to be stored for browse security.Use a password known only to authorized users.
Confirm PasswordRepeats the new password.Must match exactly before QBM saves the password.
Blank passwordClears the browse password where allowed.Use only if the company no longer wants this extra protection.
Important: Browse password is not the same as the user's login password. User access should still be controlled from Users and Security Groups.

Document Permissions

Some QBM forms support a toolbar button called Permissions. When visible, it allows authorized users to set document-level read, edit, and delete permissions for selected users.

ColumnWhat It MeansHow To Use It
UserThe QBM login user receiving document-level access.Select the user who needs specific access to this document.
EmployeeThe employee linked to the selected user, where available.Use it to confirm that the correct person is selected.
ReadAllows the user to view the document.Enable when the user needs visibility but not editing.
EditAllows the user to change the document where business rules permit.Enable only for users responsible for maintaining the document.
DeleteAllows the user to delete the document where QBM permits deletion.Use rarely and only for trusted users.
Before permissions can be saved: The document must already be saved, and the current user must be allowed to change document permissions.

List Sorting

Many QBM lists and reports allow sorting by clicking column headers. Some reports also provide a Sort dialog with up to four sort levels.

Sorting AreaWhat It DoesWhen To Use It
Column header sortSorts the grid by the selected column.Use for quick one-column sorting such as date, name, amount, or reference.
Sort dialog - level 1 to 4Allows multi-level sorting with ascending or descending direction.Use when a report must be sorted by more than one value, such as customer then date then amount.
AscendingSorts A to Z, oldest to newest, or smallest to largest.Use for normal chronological or alphabetical review.
DescendingSorts Z to A, newest to oldest, or largest to smallest.Use to bring latest dates or highest amounts to the top.
Clear AllRemoves selected sort criteria.Use when the list order is no longer helpful.
Saved grid settingsSome lists remember layout or sorting.If the grid looks unusual, reset or adjust the layout before reporting an issue.

Recommended Workflow

  1. Use security groups first for normal access control.
  2. Use document permissions only when a specific document needs more targeted access.
  3. Set browse password only if the business has a clear reason for an additional browse-level password.
  4. Use sorting and filters before exporting or printing list results.
  5. If a user cannot see a document, check the security group, document permissions, and whether the document was saved first.

Best Practice

  • Do not share administrator login credentials to bypass permissions.
  • Give Delete permission only to users who understand the correction process.
  • Review document permissions when users move roles or leave the company.
  • Use saved list layouts carefully, because a hidden column or unusual sort can make a list look incomplete.
  • For sensitive access questions, support should check both group permission and document-level permission.