Feature Request: Contextual Inline Identity Badges (Location, Working Hours, Team & Role)

Summary
Enable customizable, compact inline metadata pills/badges directly alongside user display names in message headers (building upon the current basic flag/city indicators). This allows team members to instantly understand who they are communicating with, their operational hours translated to the reader’s local time, and their organizational context without hovering, opening profile cards, or context switching.

The Problem & Value Proposition
Cognitive Overhead & Context Loss: In distributed, cross-functional organizations, users frequently collaborate with teammates across different geographies and departments. Remembering everyone's location, time zone, department, and seniority level is mentally taxing.

Friction in Async Collaboration: Determining whether a coworker is currently working requires clicking their avatar, inspecting their profile, and mentally calculating time zone offsets. This micro-friction often leads to delayed urgent requests or inappropriate out-of-hours pings.

Organizational Blind Spots: In large channels (e.g., incident response, announcements, or company-wide help desks), readers often lack context on whether a poster is a triage engineer, a decision-maker (director/VP), or an external stakeholder, leading to unnecessary back-and-forth clarification.

Primary Value:
Presents crucial operational context at the point of consumption, saving time, reducing cognitive strain, and streamlining asynchronous handoffs.

Proposed Feature Details

Visual Format (Inline Header):

[Avatar] John Smith 🇪🇸 Valencia · [Working: until 5 PM (2h left)] · [Core Backend] · [Staff Engineer]

Location: Country flag + optional city name (e.g., 🇪🇸 Valencia).

Dynamic Working Hours: Automatically translated to the viewer’s time zone (e.g., Active · ends 5:00 PM or Off-hours · starts tomorrow 9:00 AM).

Team / Department Badge: Highlighting primary ownership (e.g., Core Platform, Design Ops).

Role / Seniority Tag: Functional title or level (e.g., EM, Security Lead, Staff Eng).

Data Ownership & Governance Model

To prevent visual clutter while ensuring compliance and utility, configuration should operate across three tiers:

1. Global / Admin Level (Controlled by Workspace Admins)
   • Sync core role, title, and department directly from HRIS/IdP systems (e.g., Okta, Workday, Google Workspace) to maintain a single source of truth.
   • Set org-wide default visibility settings and allowable badge fields.
2. Channel Level (Controlled by Channel Owners / Admins)
   • Define required or hidden metadata pills per channel type. Example: An incident management channel can mandate "Role" and "Timezone/Working Hours," whereas a social channel can hide roles to minimize clutter.
3. User Level (Controlled by Individual Users)
   • Set working hours and scheduling preferences.
   • Control privacy settings (e.g., toggle between country flag only vs. city-level precision).
   • Select primary display team/project for cross-functional staff.

UX & Display Considerations
Progressive Disclosure: On narrow screens or dense view modes, show an abbreviated chip (e.g., 🇪🇸 · Platform · 🟢) that expands on hover.

Visual Hierarchy: Use muted, secondary text styling or subtle pill containers to ensure the message body and sender's name remain the primary focal points.

Thread Consistency: Allow the full badge to display on the root message, with a more compact treatment on subsequent replies within the same thread to conserve vertical space.