For AI agents: the complete documentation index is available at https://www.jumpserver.com/docs/llms.txt, the full documentation bundle is available at https://www.jumpserver.com/docs/llms-full.txt, and this page is available as Markdown at https://www.jumpserver.com/docs/features/workbench/tickets/my-tickets.md.
🎉 JumpServer v5.1.1 is available. See what's new →
  • v5

    • My Tickets

    Enterprise Edition

    Tickets & Approvals requires JumpServer Enterprise Edition. Ticket entries, approval cards, and flow settings are hidden without a license.

    Request 14-day free trial

    Submitted is the end-user index of tickets you created. Use it to request temporary access to assets, follow the approval progress of a request, answer an approver's questions, and cancel requests that are no longer needed. In the navigation, this page is labelled Submitted; its page title is My Tickets.

    Figure 1: The Submitted tickets list and entry point

    Prerequisites

    • The Tickets feature is enabled and licensed. The Tickets & Approvals area requires an enterprise license.
    • Your role grants the ticket permission needed to view and create tickets.

    Submit an access request

    1

    Open the ticket area and make sure the Submitted tab is active.

    2

    Click New ticket and choose Request asset authorization.

    3

    Fill in the title, organization, and requested assets or nodes.

    4

    Choose the account and actions you need, and set the start and expiry dates.

    5

    Submit the ticket. It appears in the list and moves through the approval steps defined in the ticket flow.

    Figure 2: Completing a ticket request

    FieldDescription
    TitleShort description of the request
    OrganizationOrganization in which the permission is requested, and the organization the applicant belongs to
    Ticket flowApproval flow used for the request. It is selected from the organization and ticket type; when only one flow exists it is filled in automatically
    CC usersUsers who should receive updates without acting as approvers
    NodeRequest permission for every asset under a node
    AssetSpecific assets requested
    AccountAccounts requested on the selected assets
    ActionsPermissions requested, such as connect, upload/download, clipboard, or share
    Start date, Expiry dateValidity window of the requested permission
    CommentOptional context for the approver

    Ticket types

    TypeMeaning
    Apply for assetsA user requests temporary asset permission
    Login reviewA login blocked by an access policy waits for approval
    Command reviewA command blocked by a command filter waits for approval
    Asset connect reviewA login to a specific asset waits for approval

    Only asset authorization requests are created from New ticket. The other types are raised automatically by access policies, command filters, or login rules, and then appear in the same list for tracking.

    Track and manage tickets

    • Click a Title to open the ticket detail page. It shows basic information, the requested permissions, the approval steps and their handlers, CC users, and the conversation with the approver.
    • Use the Status filter to switch between pending, approved, rejected, and cancelled tickets. By default the list is limited to requests that still need attention.
    • Use Reply in the detail page to add context for an approver.
    • If a pending request is no longer needed, cancel it from the detail page so the approver's queue stays accurate.

    Column reference

    ColumnDescription
    No.Ticket serial number
    TitleTicket title; click to open the detail page
    TypeTicket type, such as Apply for assets
    StatusPending, approved, rejected, or completed
    DateCreation time of the ticket
    Note

    Requested permissions are valid only for the dates in the ticket. After the expiry date, the temporary authorization stops working even though the ticket record remains available for review. Auditors can review ticket history from Ticket Audits.