Skip to main content
Once a Privilege Elevation rule is active on an endpoint, Syteca replaces the native Windows UAC prompt with its own experience, matching whatever elevation mode the applicable rule specifies.
Every Syteca pop-up shown on the endpoint carries the Syteca icon, so users can tell a policy decision from a native Windows dialog.

What the user sees, per elevation mode

No pop-up, and no UAC window. The application starts immediately with administrator privileges.

When the endpoint is offline

Without a connection to the Application Server, Syteca can’t check for approval or confirm an Auto-elevate schedule, so it falls back to denying elevation regardless of the rule’s configured mode:

Requesting and approving access

The approver’s side

A Require approval request appears on the Access Requests page in the Management Tool, visible to the users or groups selected as approvers on the rule. An email notification is also sent to them, including the request date and time, the requesting user and endpoint, their comment, the rule name, and the application’s path. Opening a request shows the same details, plus, once processed, who approved or denied it and when. Approving a request opens the Request Approval pop-up, where the approver adds optional comments and sets Access will be granted for. The default is 30 minutes, and the approver can change it before confirming. The duration applies as soon as they click Confirm, and administrator permissions are revoked automatically when it expires.
The Request Type filter on the Access Requests page includes Privilege Elevation as its own type, alongside your existing PAM access request types.
How long a request can sit unanswered is governed by the general Expiration time of Access Requests setting on the System Settings page, the same setting used by other access request types. A request that expires before anyone acts on it is marked Expired in the Management Tool, in the Syteca Access Center, and on the Events tab.

The user’s side, after a decision

During the approved period

While the granted time is still running, the user can launch the approved application with administrator rights in any of three ways:
  • Run in the Syteca Access Center
  • Run in the “Access request approved” tray notification
  • Launching it directly as administrator, for example with Run as administrator
The Request to launch application pop-up does not appear again during this period, and no new request is needed. Once the period expires, launching the application as administrator starts the approval flow from the beginning.

Syteca Access Center

Once at least one Privilege Elevation request has been sent from an endpoint, a Syteca Access Center icon appears in that endpoint’s Windows notification area.
1

Open the Access Center

Click the Syteca Access Center tray icon.
2

Review your requests

See every Approved, Pending, Denied, and Expired access request available to you. Use Search to find one by application or file name.
3

Launch an approved application

Each approved entry shows the date and time until which it stays valid, with a Run button to launch it directly, with no need to trigger a new elevation attempt.
Syteca Access Center window with a list of access requests

The Syteca Access Center, showing available access requests.

Requests stay listed for the whole granted access period, not just the current Windows session. A request approved for 30 days remains available in the Access Center for those 30 days, across sign-outs and different user sessions on that endpoint.
The Access Center needs a connection to the Application Server. If it can’t run, the user sees: “Failed to run Syteca Access Center application. Please contact an administrator.” If the connection drops while it is open, the window closes and the same message appears, and it can’t be reopened until connectivity is restored.

When elevation fails outright

Separate from a Deny decision, an elevation attempt can fail for operational reasons. A pop-up titled “Elevation failed” tells the user that elevation could not be completed and to contact their administrator, and, if configured, the failure notification is emailed to the recipients defined on the rule. The three known causes are:
  • The account in the rule’s Secret no longer belongs to the local administrators group on that endpoint.
  • The password of the account in the Secret was changed manually, outside Syteca.
  • The rule holds only an Active Directory Secret, and the endpoint isn’t joined to the domain.

Overview

What Privilege Elevation does and how it’s licensed.

Creating and managing rules

Configure the elevation mode and approval settings referenced here.

Events and monitoring

Every request and decision, logged for audit.

Access requests

Where approvers review and act on elevation requests.