Input Issue - "Backup and restore" label in domain context is inconsistent with page title and server-level equivalent

[moWerk]

Inconsistent navigation label causes hesitation and implies unintended action​

**Product:** Plesk Obsidian
**Version:** 18.0.77.2
**Area:** UI / Navigation

Description​

The navigation label used to access the domain-level backup interface reads "Backup and restore" in the domain context sidebar. The actual destination page is titled "Backup-Manager", which is also the label correctly used in the server-level path under Tools & Settings.

This creates two distinct problems.

First, the label is inconsistent. The same functional area carries two different names depending on the entry point: "Backup and restore" at domain level and "Backup-Manager" at server level. A user navigating both contexts has no reliable mental model for what the label refers to.

Second, the phrasing "Backup and restore" reads as a compound action rather than a navigation destination. A user unfamiliar with the interface will reasonably hesitate before clicking it, because the label implies that clicking it might trigger a backup or restore operation rather than opening a management view. This is a standard IA anti-pattern: navigation items should be named as nouns describing a destination, not verb phrases describing potential actions.

Steps to reproduce​

1. Log in as admin.
2. Navigate to Websites & Domains and select any domain.
3. Observe the sidebar navigation item labeled "Backup and restore".
4. Click the item and observe the page title is "Backup-Manager".
5. Navigate to Tools & Settings.
6. Observe the equivalent server-level item is correctly labeled "Backup-Manager".

Expected behavior​

The domain-level navigation item should be labeled "Backup-Manager" to match the page title and the server-level label. Navigation items should consistently use noun phrases that describe the destination.

Actual behavior​

The domain-level navigation item is labeled "Backup and restore", which differs from the page title, differs from the server-level equivalent label, and reads as an actionable verb phrase rather than a navigation destination.

Impact​

Users hesitate before clicking a navigation item that should be a routine management entry point. The inconsistency between domain-level and server-level labeling increases cognitive load when switching between contexts.

 

[Sebahat.hadzhi]

Thank you for the input, @moWerk . In short, the different labels reflect the different contexts in which the feature appears. “Backup-Manager” is the module name used in the server administration area, while “Backup and restore” is a more descriptive label intended for domain-level users. Both lead to the same interface - on system and on subscription level. The concern about inconsistency is understandable, but not entirely justified (in my oppinion). It is common in administrative platforms to use technical names in system-level areas and more user-friendly wording in customer-facing navigation. Likewise, “Backup and restore” is unlikely to be interpreted as an immediate action trigger. In sidebar navigation, users generally expect clicks to open a management page, not execute operations directly.

With that said, I cannot really classify that as a Plesk issue. Its nature is more of a feature request/improvement suggestion. Hence, please kindly submit the request at features.plesk.com . I will propose it for further evaluation by our team.

 

[moWerk]

Thanks alot for the swift reply!
I made another UX issue in the meanwhile, sorry if that looks like spamming. I juts had these two observations as a Plesk beginner.

Just as a pointer that it might be confusing to others. I have a 90s web dev and hosting background and still was confused by the nomenclature suggesting or at least not excluding an immediate action possibly affecting the live production site.