Password Maintenance

This comes up a lot with legacy / VMS‑era systems, and the key to a good user guide is to rename the concept without renaming the program. You acknowledge the misleading name once, then teach users how access actually works.

Below is language you can lift almost directly into a user guide.

What “Password Maintenance” Really Does

Despite its name, Password Maintenance is not used to create or change passwords.

Instead, this program controls what menus and programs a user is allowed to access within the system. The name comes from older VMS architecture, where security and menu access were tied to user credentials, but today its purpose is menu‑level security management.

In this guide, “Password Maintenance” refers to user access and menu security, not passwords.

How Access Is Structured

User access is managed in two layers:

1. Group Menus (High‑Level Access)

Each user is assigned one or more group menus, such as:

• Human Resources (HR)

• Payroll

• Finance

• Student / Operations (etc.)

Group menus determine which major functional areas a user can enter.

Assigning a group menu does not automatically give access to everything inside it.

2. Menu and Program Security (Detailed Access)

Within each group menu, access is further controlled at the menu option and program level.

For each menu or program, you can define access using one of three security models:

Security Models Explained

Password Maintenance controls what users can see and what they are allowed to do. These are related, but not always the same.

There are three security modes: Allow, Disallow, and Tailored Menu. Each behaves differently.

✅ Allow — Explicit Allow List (Opt‑In Access)

How Allow works

• The system starts with no access

• The user is allowed to access only the menu options explicitly listed

• Any option not listed is denied

Menu visibility

• The user sees the entire menu structure

• Access is enforced only when an option is selected

Behavior summary

Key rule

Allow is an opt‑in model: nothing is allowed unless it is listed.

When to use Allow

• When access should be tightly controlled but menus should remain visible

• When it is easier to list what a user may do than what they may not

• Common for inquiry‑only or limited‑role users

🚫 Disallow — Explicit Deny List (Opt‑Out Access)

How Disallow works

• The system starts with full access

• The user is denied access only to the menu options explicitly listed

• Any option not listed remains accessible

Menu visibility

• The user sees the entire menu structure

• Access is enforced only when an option is selected

Behavior summary

Key rule

Disallow is an opt‑out model: everything is allowed unless it is listed.

When to use Disallow

• Power users or administrators

• When most access should be available, with only a few sensitive exceptions

• Situations where “block the dangerous stuff” is clearer than “allow everything else”

🎯 Tailored Menu (Custom Access)

How Tailored Menus work

• The user sees only the menu options explicitly assigned

• All visible options are accessible

• Anything not assigned is invisible and inaccessible

Behavior summary

Key rule

Tailored Menus control both what the user sees and what they can access.

When to use Tailored Menus

• Clerical or occasional users

• High‑risk areas (Payroll, Finance)

• When simplicity and error prevention are critical

Comparison Table

Putting It All Together

1. Users are first placed into group menus (HR, Payroll, Finance).

2. Within those group menus, menu security defines exactly what they can do.

3. Security is controlled using Allow, Disallow, or Tailored Menu rules.

4. Password Maintenance is where all of this access is configured.