Think of the last time you created a Facebook account.
You filled in your details, hit sign up, and from that point you had an identity inside the Facebook system. Every time you logged in, your credentials were validated against that stored account. You could update your settings, manage your preferences, control your access.
Pega works exactly the same way. Except in Pega, we do not call it a user account. We call it an Operator ID.
Every single person who interacts with a Pega application – developers, architects, administrators, end users – everyone needs an Operator ID. No Operator ID means no access. Simple as that.
What Is Inside an Operator ID
An Operator ID is more than just a username and password. It is a rule form that holds a surprising amount of configuration.
At a high level, here is what you can define inside an Operator ID – contact details and profile information, which applications the operator can access and with what permissions, localization settings like language and time zone, routing and organisational structure, work queue assignments, availability and absence schedules, and security settings including authentication preferences.
For developers, most of this is straightforward. But for end users in a production application, these configurations directly affect how cases get routed, who picks up work, how escalations are handled and how the system behaves during absences.
Getting Operator ID configuration right is not optional. It is foundational.
Three Ways to Create an Operator ID
- You can create an Operator ID manually from Dev Studio – useful when setting up a development team.
- You can also create operators during the application creation process.
- And in most enterprise environments, operators are provisioned automatically through single sign-on, where Pega integrates with your organisation’s existing directory – typically LDAP – so users do not need separate credentials for every application.
One Thing Developers Often Get Wrong
There is one setting inside Operator ID that catches developers out more than any other.
The option to mark an operator as available to receive work.
If this is accidentally enabled on a developer’s Operator ID in a production environment, real cases can get routed to that developer. It happens more than you would think. Always double check this setting when you are working on production environments.
Watch the Full Walkthrough
In the video below I walk through a live Operator ID creation – from the create form all the way through to logging in with the newly created operator. You will see every configuration section in action.
Operator ID is one of those topics that looks simple on the surface but has a lot of depth when you start working on real enterprise applications. This video gives you the full picture.
