IMDTouchKnowledge BaseShop main store

Explainer

Why one HMI password opens buttons at two security levels

HMI and touchscreens Published 6 min read

Short answer

On a Delta DOP-B, security is one hierarchy from level 0 to level 7: a password registered at level 5 authorizes elements at level 5 and every level below it, including level 3. Two momentary buttons on this panel therefore cannot carry mutually exclusive passwords. Keep the ladder when a senior operator may press both buttons; move to a platform that assigns permissions per user when credentials must be exclusive.

On this page
  1. The ladder is the whole security model
  2. What a level-5 login actually reaches
  3. Two requirements that only look alike
  4. Worked example: what each password reaches with buttons at level 3 and level 5
  5. Check what is really running before you blame the levels
  6. Getting exclusivity means leaving the ladder
  7. Questions asked

On a Delta DOP-B panel, two momentary buttons cannot carry mutually exclusive passwords, and no setting in DOPSoft changes that. The panel's security is a single hierarchy: levels 0 through 7, with a password table hung on that one ladder, and a login at any level authorizes every element at that level and below. The password registered at level 5 therefore opens a button assigned to level 3 just as readily as one assigned to level 5. Swapping password strings, spreading the levels further apart, or re-downloading the project leaves that relationship intact. If the requirement is that a senior operator may press both buttons, the standard configuration already does the job. If the requirement is that neither credential can operate the other's button, the level system is the wrong tool, and the platform has to change. The count below proves it.

The ladder is the whole security model #

In DOPSoft 2.00.07, credentials live in one dialog: open Options → Configuration → Security Level and Password and enter the "Highest security password" there. The DOP-B User Manual defines the mechanism as a password-table setup over a fixed range — level 7 the highest, level 0 the lowest — so the project carries one ladder of eight rungs and one table of passwords attached to it.

Each protected object, a momentary button or a numeric input, holds a security-level property taken from that range. Passwords attach to levels, never to individual elements. That is the root of the behavior: because no button ever owns a password of its own, two buttons can never own two unrelated passwords.

What a level-5 login actually reaches #

The operating rule is hierarchical: a login made with the password registered at level N authorizes every element whose own level is N or lower. Put button A at level 3 and button B at level 5. The operator holding the level-3 password can press button A; button B stays closed to them. The operator holding the level-5 password can press button B and button A.

That is not a fault, a version bug, or a setting someone missed — it is the documented reach of the level system. The design is the industry norm rather than one maker's quirk; InTouch security, for comparison, runs the same kind of ladder with access levels from 0 to 9999.

Two requirements that only look alike #

Decide which policy you actually have before touching the project. Restricting means the second button is reserved for a more privileged role, and that role keeps the first button too. Excluding means two people each own one operation and must be locked out of each other's. The ladder expresses restricting exactly. It cannot express excluding at all.

Configuration on a DOP-B Access effect Requirement it serves
Button A at level 3, button B at level 5 Level-5 password opens both; level-3 password opens A only A senior role may use both buttons
Different password strings on those levels The credentials differ, the reach does not Rotating a compromised password
Credential A barred from button B, credential B barred from button A Not expressible in levels Exclusive operations

Worked example: what each password reaches with buttons at level 3 and level 5 #

Inputs. The ladder runs from level 0 to level 7 — eight values, per the DOP-B User Manual's password-table setup. Button A is assigned level 3 and button B level 5, the two momentary buttons in the project. The reach rule is the one demonstrated above: a login at level N authorizes levels 0 through N.

Rule in words. Count how many of the eight levels each credential reaches, and how many of those the two credentials share. Two exclusive passwords require the shared count to be zero.

Arithmetic. The level-5 login reaches levels 0, 1, 2, 3, 4 and 5 — that is 5 − 0 + 1 = 6 of the 8 levels. The level-3 login reaches levels 0, 1, 2 and 3 — that is 3 − 0 + 1 = 4 of the 8. Every one of those 4 levels also lies inside the level-5 reach, so the overlap is min(3, 5) + 1 = 4 levels, and button A's level 3 sits inside it.

Result. Both credentials operate button A. Generalizing the count: for any two distinct levels N and M with N below M, the overlap is N + 1, and since the lowest level is 0, that is always at least 1. Zero overlap is unreachable for every pair the ladder offers. Eight rungs buy nesting depth, never separation.

Decision. If the policy allows the level-5 operator both buttons, assign the restricted operation to the higher level and keep the panel as configured — the behavior is correct. If either credential must be barred from the other's button, no level assignment on this panel will deliver it.

Check what is really running before you blame the levels #

Read the security-level property of each button in DOPSoft and record the number; the button caption and the text shown in the prompt prove nothing about the assignment. Confirm the panel is running the project revision you edited.

Test each credential from a logged-out panel. An earlier login stays active until the project's logout function clears it, and a press inside that session inherits the level instead of prompting again. Test on the panel itself rather than trusting the simulator, because HMI user management that works in simulation but not on the panel is a failure mode of its own.

If the wrong output moves when a button is pressed, suspect binding before security. Security decides who may press; the write address decides what changes. Two buttons aimed at one address produce the same machine action whatever their levels, so compare the addresses and watch them in the controller before changing any password.

Getting exclusivity means leaving the ladder #

Write the policy as a matrix first: every credential against every protected operation, allow or deny, plus the logged-out state. The DOP-B cannot fill in a deny where a higher credential must be barred from a lower element — that cell does not exist in a hierarchy.

For this requirement the DOP100 series is the next step in the same family: its engineering environment works with user accounts whose rights are assigned individually instead of one ladder. Build the two buttons and the two accounts in a bench project, confirm each allow and each deny, then commission. If the move is toward a PC-based HMI rather than another Delta terminal, industrial panel PCs put a PC runtime at the machine, where the operating system's user manager grants rights per account; CODESYS-based panels take the same approach, and granular user access on a CODESYS touch panel is a setup procedure of its own.

Whatever runs the screen, keep one boundary clear: access control decides who may press a button, and permissives and safety functions stay in the controller.

Questions asked

What happens with three or more protected buttons instead of two?

The nesting simply continues. With buttons at levels 2, 4 and 6, the level-6 login operates all three, the level-4 login operates the level-2 and level-4 buttons, and the level-2 login operates only its own. Adding protected elements adds rungs to the same ladder; it never creates a second, independent lock. Any number of exclusive operations is equally out of reach.

Why does a protected button sometimes work without asking for a password?

Because an earlier login is still active. The panel holds the operator's authorization level until the project's logout function clears it, so a press inside that session inherits the level instead of triggering a prompt. Add a logout element to the screen, clear the session, and retest each credential from the logged-out state.

Would protecting the whole window instead of the button fix it?

No. The ladder is a project-wide setting: every protected object, whether a window, a button or a numeric input, draws its level from the same 0-to-7 range. Moving the protection from the button up to the screen changes where the prompt appears, not who ends up authorized, and the higher password still reaches the lower window.

When is the ladder design the right choice?

When operators are ranked and senior roles should inherit junior operations. A machine with trainee, operator and maintenance logins maps cleanly onto levels: each higher password legitimately opens everything below it. Exclusive rights, where two specialists each own one operation and must be barred from each other's, are the one case the ladder cannot express.

Keep reading

  • Troubleshooting

    Keeping PanelView Plus User Passwords After an MER Download

    There is no download option that leaves terminal users intact: a .mer replaces the runtime's users and passwords with the project's accounts. The working path is to upload the running runtime, restore it in FactoryTalk View Studio ME 8.00 or higher, which returns the terminal's current users to the project, then edit, rebuild and download, qualified once per terminal family. If downloads must never touch accounts, manage them with FactoryTalk Administration Console instead.

    HMI and touchscreens

  • How-to

    How to Size HMI Touch Buttons in a Dense Button Matrix

    On a graphics HMI there is no fixed touch-cell grid: the button you draw is the touch target. Lay out all 42 elements — 32 matrix buttons, 5 feedback displays, 5 navigation keys — with at least a 6 mm gap between touch areas, keep any pixel deadband small, then press every target on the actual terminal before sign-off.

    HMI and touchscreens

  • Troubleshooting

    Reaching HMI Config Mode With No Startup Square

    Test the documented USB keyboard path once - Ctrl+Shift+Alt+Windows held for a few seconds - because on terminals that never show the startup square it is the supported route in. A password-protected GO TO CONFIG button is application access control: get the credentials or the project from the owner, never a reset file. If you only need the IP address, discover it on an isolated link and skip configuration mode entirely.

    HMI and touchscreens