Expose Hub User Fields in ARC for Reporting

What is the challenge?

Currently, several key user metadata fields managed in Hub are not available within ARC for reporting or analysis. These include:

• Job title

• Mobile number

• Time zone

As a result, customers cannot build meaningful user-based reports in ARC without exporting data or maintaining parallel records outside the platform. This limits the value of ARC reporting, particularly for organisations with large or geographically distributed user populations.

What is the impact?

The absence of these Hub user fields in ARC reporting impacts customers’ ability to:

• Build context-rich audit, risk, and assurance reports

• Confidently report across global teams operating in different time zones

• Reduce manual effort and data inconsistencies caused by external tracking

For regulated customers (e.g. healthcare, financial services, public sector), incomplete user context in reporting weakens governance oversight and increases reliance on manual workarounds.

Describe your idea

Expose key Hub user fields within ARC so they can be used in reporting, filtering, grouping, and dashboards.

Specifically, make the following fields available in ARC reporting:

• Job title – to support user-based analysis and accountability reporting

• Mobile number – for completeness and operational reference where required

• Time zone – to support global reporting and accurate interpretation of user activity

These fields should be read-only in ARC and remain mastered in Hub, ensuring a single source of truth while enabling richer reporting where customers consume insights.

Reporting Use Cases

This enhancement would enable customers to:

• Report on audits, actions, incidents, or risks including the by users given role or job title

• Improve interpretation of activity timestamps across multiple time zones

• Produce clearer management and board-level reports without external data joins

Value

• Increases the practical value of ARC reporting without altering customer workflows

• Reduces reliance on exports, spreadsheets, and manual data reconciliation

• Improves consistency and transparency between Hub and ARC

• Supports more mature governance, risk, and assurance reporting