Use and extend

Connect messaging platforms

Plan channel credentials, private-message behavior, identity mapping, and rollout tests.

Messaging platforms give users a familiar interface while Maia remains a single governed runtime. Each platform authenticates its sender differently, but Maia converts the result into a stable platform:user_id before authorization.

Choose a channel pattern

Pattern	Use it when	Main concern
Private or direct message	The conversation can contain user-specific or sensitive context.	Verify the sender's stable platform identity.
Restricted team channel	Several governed users share an operational context.	Do not treat channel membership as a Maia role.
Mention-based public channel	Maia should respond only when explicitly invoked.	Minimize exposed tools and prevent sensitive output.
Webhook or API	Another system starts deterministic workflows.	Authenticate requests and define a non-human governance identity.

Common platform families

Maia includes adapters for platforms such as Discord, Slack, Telegram, WhatsApp, Signal, Matrix, Mattermost, email, SMS, Home Assistant, Microsoft Teams, and webhook/API integrations. The installed version is authoritative because adapters and provider requirements evolve.

Prepare credentials

Create a dedicated bot or application for the Maia deployment.
Grant only the platform permissions required for the intended channels and message types.
Store tokens through Maia's secret-aware Gateway or Keys interface.
Record the bot owner, renewal process, permitted workspaces or servers, and incident-revocation procedure.

Do not reuse an upstream Hermes bot.

If Maia and Hermes use the same bot credential, both gateways can consume or reply to the same events. Give each runtime its own bot identity.

Roll out a platform safely

Connect the bot to a private test channel.
Admit the bootstrap administrator and verify a simple response.
Add a second identity and confirm that it remains Pending Governance.
Assign that identity a minimal role and verify /whoami.
Test normal chat, an allowed tool, a denied resource, and any expected approval flow.
Expand to production channels only after logs and audit events match the intended policy.

Apply channel safety

Require direct messages for dashboard sign-in tokens and other private responses.
Do not expose administration commands in broad channels.
Restrict file and terminal tools independently of channel membership.
Define how message history, attachments, and generated files are retained by the platform.
Use platform-native audit and revocation features alongside Maia's audit trail.