Any signed-in account, including one holding only the User role, has a self-service portal scoped strictly to its own identity. It exists so a request for a routine certificate doesn’t need to go through an administrator at all: a user browses the templates made available to them, submits a request, and comes back later to collect the result. Nothing in the portal is edition-gated — a Free installation gets the same self-service surface as a Pro one.
How it works
A template only appears in the portal if an administrator has explicitly offered it there and set its subject mode for self-service use; templates left at their default are invisible to this surface entirely, so nothing is available to request until an admin opts a template in. Every action a user takes is scoped to their own account: a user can view and manage their own certificates and requests, and never another user’s.
My Certificates
Lists the signed-in user’s own issued certificates and enrolment requests, and lets them browse whichever templates an admin has marked for self-service and enrol against one. A CSR can also be pasted directly here for signing, for the case where the key was generated outside the browser.
My Profile
Shows the signed-in user’s own identity details and MFA status, with the ability to enrol or manage two-factor authentication and change the account password — the self-service equivalent of what an admin manages for other accounts under Settings → Users.
Completing a stored CSR
The CSR tool under Tools lets any signed-in user generate a certificate signing request in the browser and, if the key doesn’t need to leave immediately, have CertOps hold the private key server-side so the request can be finished later. Pending CSRs can be listed, deleted, or completed from the same page, which is useful when the certificate template or approval isn’t settled yet at the moment the key is generated.
Limits
A template has to be explicitly opted in. Nothing appears in the portal by default, however active it is elsewhere in the console — a template only shows up once an admin sets it to be offered there.
The portal cannot see across accounts. It has no view of another user’s certificates, requests or profile, by design — an administrator manages other accounts from the main console instead.