Hubz.

Operator area / Health, audit and support metadata

Operator console: service health and audit records

Authorized operators review available service signals, safe error summaries, platform changes and read-only support metadata.

PRODUCT VIEW

See how it works.

Authorized service operators can review service health, audit records and read-only support metadata. Health reviews existing service signals and supplied error summaries, showing similar errors together with the records available. Audit shows platform actions by event, actor, workspace and time. A separate support area provides read-only metadata. These views are neither customer CRM reports nor a general-purpose monitoring platform included with a subscription.

Hubz.Workspace / Platform operations and auditDK
EXPLORE THE PRODUCT

Platform operations and audit

Sample view
Available service signalsGrouped error summariesPlatform audit trailRead-only support metadata

Platform operations and audit

Available service signalsReview service statuses and assessments supplied by the API without implying that unavailable telemetry exists.Review ↗
Grouped error summariesAssess similar records through time, available frequency and safe descriptions. Incomplete scope must not be generalized to platform-wide totals.Review ↗
Platform audit trailReview recorded events by actor, workspace and time, using list search and pagination to return to the relevant event.Review ↗
Read-only support metadataInspect metadata provided for operational support without presenting it as unlimited access to all customer communications.Review ↗
01Open the relevant operations view
02Review scope and time
03Start authorized follow-up
Interface illustration using sample data. The layout is simplified to explain the relevant feature.

FROM NEED TO OUTCOME

Where this helps.

A health signal, error record and customer support issue are different types of evidence. Treating them as one definitive service status, or losing the trail of an operator change, makes investigation harder.

WHAT YOU CAN WORK TOWARDS

Investigate using the available service data, trace who changed what and when, and keep support metadata separate from customer content.

STEP BY STEP

How to use it.

  1. 01

    Open the relevant operations view

    Choose health, audit or support metadata according to the question. Missing data is not proof that the service is healthy.

  2. 02

    Review scope and time

    Assess signal freshness, the records available for that error group or audit event time. Keep source and organization context distinct.

  3. 03

    Start authorized follow-up

    Investigate with existing operational tools and records. Visible panel information does not grant unrestricted customer data access or unlogged action rights.

INSIDE THE MODULE

What can you do?

FOCUS 01⊙
Platform operations and audit
Scope●Permission○Review○
Open the relevant operations view

Available service signals

Review service statuses and assessments supplied by the API without implying that unavailable telemetry exists.

FOCUS 02▤
Platform operations and audit
Scope○Permission●Review○
Review scope and time

Grouped error summaries

Assess similar records through time, available frequency and safe descriptions. Incomplete scope must not be generalized to platform-wide totals.

FOCUS 03↗
Platform operations and audit
Scope○Permission○Review●
Start authorized follow-up

Platform audit trail

Review recorded events by actor, workspace and time, using list search and pagination to return to the relevant event.

FOCUS 04◇
Platform operations and audit
Scope●Permission○Review○
Open the relevant operations view

Read-only support metadata

Inspect metadata provided for operational support without presenting it as unlimited access to all customer communications.

IN EVERYDAY WORK

What it looks like in practice.

Authorized platform operator

After an access decision, the relevant audit event and current service signals need review together.

Investigate service, policy and individual action context through separate evidence.

Scenarios are illustrative; they are not customer testimonials or measured performance claims.

KNOW WHAT IS INCLUDED

Plans, permissions and limits.

Only for separately authorized Hubz platform operators. No CRM plan grants access to this operations console.

  • This panel is not a general-purpose APM, SIEM, security certification or guarantee of uninterrupted service.
  • Available monitoring is limited to the service signals and records shown. It does not provide access to all customer content.
Compare plans

YOUR QUESTIONS

About this feature.

01Does Business include the audit console?

The platform operations console described here is separate from customer plans. Customers' own workspace permissions and existing record access have a different scope.

02Does no visible error prove everything is working?

No. The panel shows signals from existing sources. Freshness, scope and inaccessible data must be assessed separately.

RELATED WORKFLOW GUIDES

You may also need these features.

Release notesReview recorded product updates by version, date and change descriptions.Settings centerManage profile, organization, security, communication, data and usage settings within the relevant permission boundaries.PWA and connection statusUse browser-based installation on supported devices while keeping connection and update status visible.

MODULES THAT WORK TOGETHER

Explore related modules.

01

Data management

Identify gaps in CRM records and manage migration and data organization around the workspace’s actual needs.

02

Integrations

Set up email, calendar, task-file and approved communication connections with the correct account, permissions and action scope.

03

Security and team access

Arrange team access through workspace membership, existing roles, enabled modules and connection permissions.