Teams
Libre gives people shared places to talk, share resources, schedule work, and involve a model—without making private content visible to an operator by default or borrowing another person’s model credentials.
Channels carry conversation beyond a one-to-one chat while keeping membership as the authority for every message, attachment, and live event.
Public and private rooms plus deduplicated direct messages use persistent ordered timelines. Replies stay one level deep, deletion preserves ordering, and read cursors never move backwards.
A model mention becomes a durable reply using the invoking member’s model access, provider credentials, and routing. Membership is checked again before generation.
Every read, write, attachment download, and event checks channel membership. Non-members receive a non-enumerating response, including global administrators.
Owners share to a user or group with a read, write, or admin role appropriate to that resource. Access is recalculated on every request instead of freezing permission into a copy.
Chats, notes, knowledge collections, personas, prompts, skills, calendars, and tool servers use the same grant foundation, with the operations each resource can safely expose.
Direct and group grants are evaluated live. Remove a user from a group or revoke a share and stale permission does not linger in a cached session.
The global administrator role manages platform capabilities but deliberately does not confer access to another person’s private resources or channel content.
The inbox, webhooks, and calendars are durable application records first. Live delivery makes them timely without becoming the sole source of truth.
Direct messages, mentions, replies, channel invites, shares, automation failures, reminders, and system messages arrive in a per-user inbox and update live.
Notifications guideAdministrator-managed targets can subscribe by event type. Deliveries are egress-guarded, optionally HMAC-signed, retried as durable jobs, and exclude prompts, documents, and message bodies.
Outbound webhooksNamed calendars support colors, recurring events, one-time reminders, and ICS import and export. Built-in tools let a model read or mutate events under the ordinary approval flow.
Calendar guideTeam capabilities build on a shared authorization layer rather than feature-specific identity shortcuts.
Users can review and revoke signed-in sessions. Personal API tokens are shown once, stored only as hashes, rate limited, expirable, and restricted to explicit scopes.
Administrators manage group membership while the authorization service evaluates that membership live for shared resources and feature access.
Generic OpenID Connect supports PKCE, state, nonce validation, allowed-domain policy, role mapping, and optional group synchronization. GitHub and Hugging Face OAuth remain available too.
Single sign-on