Cadres IT Operations & Infrastructure
Sheet BEA-00 Rev 2026.08
Start Trial

Manual · ITSM Manual

Beacon manual.

Beacon is the Cadres service desk: tickets, SLA policy, journey automation, chat intake, change management, major incidents, problems, knowledge and experience reporting.

Audience: Service desk and IT operations teams Focus: Ticket handling, change control and requester experience

Beacon is the Cadres ITSM product. Incidents, service requests, changes and problems share one ticket model. SLA policy, journey automation, chat intake and change approval are part of the product.

The first three pages describe how the desk is organised. The operator guides after them come from the product manuals and cover each workflow step by step.

Operations Core2 sheets
Assurance & Control1 sheet
Detailed Operator Guides11 sheets
BEA-04 Tenant Setup & Onboarding First-run setup for a new tenant: what Beacon creates for you, what it leaves empty, and the steps to a working desk. BEA-05 Administration Console Reports, dashboards, workload views, the XLA scorecard and the settings administrators use to run the desk. BEA-06 Service Desk Workbench Queues, the ticket workbench, SLA clocks, classification, merging and the escalation handoff. BEA-07 Requester Portal The help center: search, catalog requests, issue reports, ticket status, approvals, chat and Teams intake. BEA-08 Journey Template Gallery The template gallery: which journeys ship on, how to enable and tune the rest, approvals, and run history. BEA-09 Journey Studio & Runs Authoring custom journeys, dry runs, manual runs, editing journeys with runs in flight, and run history on the ticket. BEA-10 Change Management Running a change: authoring, the governance gate, CAB approval, freeze windows, collision checks, implementation and review. BEA-11 Major Incident Operations Declaring a major incident, assigning roles, sending scheduled updates, standing down and the required post-incident review. BEA-12 Problems & Knowledge Turning recurring incidents into problems, recording known errors, and writing articles that deflect tickets. BEA-13 Knowledge Capture Loop Capturing articles at resolution, deflecting at intake, finding resolutions with no article, and reviewing aged content. BEA-14 Migrating from Another ITSM Moving tickets, knowledge, configuration items and users from ServiceNow or Freshservice into Beacon with the import console.
Read pathWhere teams usually start
  1. Start with Service Desk & Ticket Operations for the ticket model, intake channels and SLA policy.
  2. Read Automation & Change Governance before you enable journeys, run change approval or plan for major incidents.
  3. Read Visibility, CMDB & Experience when you set up configuration items, the device bridge or experience reporting.
BridgesHow Beacon connects · optional
B-01

Portal

Portal holds the identities, roles and permissions for everyone who works in Beacon. Migration imports match people against the Portal directory.

B-02

Relay

Relay is the endpoint management product. Its ITSM bridge turns device events into Beacon tickets and reads ticket status back.

B-03

Keystone

Keystone holds billing entitlements and seat counts, which Beacon service commitments must match.