#Operator Guide

Operator access is built from two layers: a System Operator system role and an Organization Operator organization role. The organization role is what grants day-to-day Workbench access inside a specific organization. See Role Model for the general model.

#Operator roles

#System Operator baseline

The system role provides the personal and cross-organization baseline used with an organization role:

• Profile, Preferences, and Notifications
• Access Keys and Tokens
• Workbench Overview and the Workbench entry
• JumpServer Client and Asset Connection

#Organization Operator

Organization Operator uses Workbench inside the assigned organization. It does not administer users, assets, authorizations, or platform settings.

#Workbench

• Overview
• Access Assets
• File Transfer
• Personal Credentials
• Job Center — Adhoc, Jobs, Templates, and Execution History
• Tickets & Approvals — Submitted and Assigned tickets
• Tools

#Client

• Client Overview — desktop client features and requirements
• Asset Connection — Linux, Windows, database, and web assets
• Connection Settings — local preferences and application paths

#General

• Global Search
• Notifications
• Profile
• AI Assistant when enabled for the deployment

#Scope boundaries

• Console administration, PAM lifecycle automation, Audits, and System Settings are not part of Organization Operator by default.
• Flow Setup in Workbench > Tickets & Approvals is an administrative configuration, not an operator task. Operators use Submitted and Assigned.
• To use Workbench in another organization, assign Organization Operator there and switch organizations.

#Assigning operator roles

1. Assign System Operator as the user's system role when a baseline account is required.
2. Invite the user to the target organization with Organization Operator.
3. Switch organizations to confirm the Workbench shows the expected authorized assets.