Support (OmniLore dual-seat members)

Audience: Product members
As-of: 2026-08-05
Install: chat / mail / forge under omnilore.ai

Self-serve first

| Need | Action |
|------|--------|
| What is OmniLore? | Ask OmniLore Shared Operator → product_answer |
| Change password | Ask agent → ldap_password_policy then change_ldap_password |
| Privacy of my chats | sot_get key tribal:shared:member:privacy-notice |
| Getting started | tribal:shared:member:getting-started |
| Agent says design_knowledge_forbidden | Expected for internal design docs — ask product questions or contact owner |
| Agent says session_corpus_forbidden | You cannot search other users’ sessions — use scope=self only |

Contacts (this install)

| Role | Contact |
|------|---------|
| Platform owner / security officer | Brent Bowlby · bbowlby@omnilore.ai · Mattermost @brent · LDAP bbowlby |
| Member (example peer) | Gwen Turecki · gwenturecki@omnilore.ai · Mattermost @gwen |
| Service identity (not human support) | omnilore@omnilore.ai |

Channels

| Channel | Use |
|---------|-----|
| OmniLore Chat (LibreChat) | Daily Q&A as yourself |
| Mattermost (when online) | Org channels; bot may assist under policy |
| Mail *@omnilore.ai | Org mail (internet send residual may apply — ask owner) |

What support will not give members

• Host shell / server sudo
• Other users’ private chats
• Full operator design encyclopedia access
• Unrestricted job submit / dual-envelope / HOOTL production controls

Members do not receive unrestricted MCP elevation by default.

• Truth + Governance — Disk SoT, tools, privacy badges