@SudheerS4590

Create a dedicated access group for your app, add pxAdminStudio to Available portals, and remove any admin roles; then add the role PegaRULES:SysOpsObserver (this is the read-only baseline for Admin Studio). In Access Manager (or AROs), grant Read/Open only on the key classes: Data-Admin-QueueProcessor, Data-Admin-JobScheduler, System-Queue-ExecutionRequest-, and System-Message- so users can open items but not act on them. Do not include SysOpsAdministrator or any role that has “Manage/Start/Stop/RunNow” privileges. If your Broken Queue items live in application-specific classes, add Read only AROs for those too. Create a test operator with just this access group and verify: Admin Studio opens, Queue Processors and Job Schedulers pages load, and action buttons (Start/Stop/Run now/Requeue/Clear) are disabled by missing privileges. If any button still shows, explicitly deny those privileges on your custom role or override the section to hide actions when the user lacks them. This setup gives System Architects view-only access to Broken Queues and Queue Processor info.