The available evidence establishes only that an existing Panorama P2 application requires a change to user management and that the location of user access-right configuration is unknown. It does not identify the software version, project structure, runtime environment, or menu path. Do not assume a specific editor, dialog, or database location until those details are confirmed.
Define the Access-Control Target
First distinguish user records from authorization rules. The requested change could involve accounts, groups or roles, object-level permissions, or another project-specific security mechanism. Record the exact behavior to change—who needs access to what function—before editing configuration.
Separate Confirmed Facts from Unknowns
| Item | Status | Engineering decision |
|---|---|---|
| Platform name | Panorama P2 | Use only documentation and tools matching that identified platform. |
| Requested work | Modify user management | Preserve the existing configuration before making changes. |
| Required setting | User access rights | Trace both account definitions and the protected functions that reference them. |
| Version and configuration location | Unknown | Do not publish or follow an unverified menu path. |
| Authorization model | Unknown | Determine whether the project uses users, groups, roles, or another mechanism. |
Locate and Verify the Configuration
Use the installed Panorama P2 help and the open project's configuration tree to search for terms corresponding to users, security, access rights, groups, or roles. Also inspect the properties of the function being protected: its authorization reference may reveal where the associated rights are defined. Treat these as diagnostic search paths, not confirmed Panorama P2 menu names.
Before changing anything, preserve a recoverable copy of the project and document the current account-to-right mapping. After the edit, test one authorized user and one unauthorized user against the specific protected function. Confirm both outcomes; a successful authorized test alone does not prove that access is restricted correctly.
FAQ
Where are user access rights configured in Panorama P2?
The supplied evidence does not identify a verified menu or configuration path. Confirm the installed version, then inspect the project configuration and the protected object's properties for references to users, groups, roles, security, or access rights.
What information is needed before changing Panorama P2 users?
Identify the installed version, the project being edited, the affected function, the users who require access, and the current authorization model. Without these details, a specific navigation path or permission change cannot be stated reliably.
How do I verify a Panorama P2 access-right change?
Test the protected function with one account intended to have access and one intended to be denied. Record both results and retain a recoverable copy of the original project configuration.