Collaboration

Available in the local environment

Katra keeps team communication beside the work it informs. Channels and Direct Messages share ordered messaging primitives while preserving distinct membership and authorization rules.

Channels

• Public internal Channels are visible to active internal members of the installation’s operating organization.
• Private Channels use an explicit bounded roster.
• Channel owners can invite members, promote another owner, remove members, and manage lifecycle without bypassing organization boundaries.
• Client-team Channels remain separate from Product and Project authorization. Conversation membership does not grant broader work access.

Direct Messages

• Human Direct Messages require at least two participants.
• Participants are structural and cannot be bypassed by an administrator override.
• Internal users can create or reopen the canonical conversation through an organization-scoped people picker.
• Client participation is bounded to one client organization and requires at least one internal participant.

Messages and threads

Messages support Markdown text, one level of thread replies, structured @ mentions, semantic reactions, unread state, author edits, and tombstone deletion. Revisions append corrected content while preserving the durable message identity and thread references.

Attachments are not yet available. Their authorization, type, size, integrity, and removal policy remain planned.

Realtime behavior

The HTTP API remains authoritative. Reverb publishes content-minimal refresh hints after the database transaction commits, and Katra Client reconciles committed state through authenticated reads. Reconnecting does not rely on receiving every transient WebSocket event.

Favorites and discovery

Users can favorite authorized Channels and Direct Messages. Favoriting changes navigation placement only and never grants access. General discovery remains in Katra’s global search rather than separate page-level search fields.