Navigate ExpertHub and its operational areas
ExpertHub access with the applicable application role, team membership, modules and operating view.
ExpertHub is the specialist workspace over the same Bourgos service information used by ServiceHub and AgentHub. It supports investigation, fulfilment, controlled change, Knowledge, portfolio, configuration, assets and authorized administration.
Before you start
Sign in to the correct tenant. The documented current layout is an icon-driven, always-visible left sidebar with independently expandable sections. Earlier horizontal-menu descriptions are historical.
Steps
- Start in Work → My work or Team queues to identify assigned or waiting work.
- Use Service Operations for Incidents/tasks, Problems/candidates/tasks, Changes/tasks, Requests/tasks and Knowledge.
- Use Service Portfolio for Services/Offerings and the separate Service Catalog menu item.
- In CSM Full with Configuration Management enabled, inspect applications, Instances, CIs, relationships, maps and availability under the applicable permissions.
- Use optional Asset Management for inventory, custody, stockrooms, contracts, repairs, campaigns and reconciliation.
- Open Analytics where enabled to build or revisit reports, checking entity, filters, aggregation and measurement meaning.
- Use authorized gear/Administration controls for tenant Setup and the announcement action where eligible.
Shared records and scoped authority
The Incident reported in ServiceHub is not copied into a separate ExpertHub register. AgentHub Contacts can link formal work that specialists continue here. The interface and visible information differ by role; record visibility does not imply permission to edit.
Domain manager roles include staff capabilities but are not universal administrators. Many staff edits depend on current assignment-team membership. CI/relationship writes and several settings actions remain administrator-only; record ownership and AgentHub roles introduce separate rules.
Expected result
Specialists can find the right working area and understand why some capabilities or actions are unavailable.
Important behaviour
Module activation, operating view and role are separate gates. A missing CI screen does not require a fabricated record; check prerequisites. The Service Catalog is separate from Services/Offerings and is no longer the old Request Settings manager.