@AlekhyaY17576243

First, make sure you’re using the orchestrator URL (the Deployment Manager server), not a candidate system, and that PegaDevOpsFoundation/Deployment Manager is installed there. Next, confirm your operator exists on the orchestrator, is unlocked/active, and has an access group that points to the Deployment Manager app with a DM role (for example DMReleaseAdmin or DMReleaseManager). If you use SSO, map your IdP group to that access group and test with a temporary local operator to rule out SSO mapping issues. Ensure your access group’s default portal includes the DevOps/Deployment Manager portal and that your role has privileges (otherwise you’ll see “not authorized”). Log out/in or try incognito after any role changes. If login loops or fails, clear cache and check that the orchestrator has at least one web node and no application/ruleset version mismatches. Check PegaRULES and Authentication logs for 401/403 to spot bad mappings or wrong operator IDs. Quick path: clone a known-working DM user for you; if nobody can get in, temporarily unlock [email protected], add DM access, and bootstrap proper users.