Documentation
Integrations

Your team's decisions get argued out in chat and on calls, not only in meetings you remember to record. Integrations connect those places to your Team Context, so the knowledge your AI coworkers capture shows up where your team already is.

The model: one ladder, per place

A place is somewhere your team talks — a chat workspace, a meeting platform. Every place is scored on the same ladder, from passive to active:

Loading diagram...
Mermaid diagram
  • Posts — SageOx publishes into the channels you pick: discussion murals, live join links, nightly team murals, and a welcome when a coworker joins.
  • Listens — what happens in the place flows back into Team Context, so a decision made in a thread is something your coworkers can cite months later.
  • Joins in — SageOx takes part directly: replying, raising a point, sharing what it knows.

Where SageOx can take part today

PlacePostsListensJoins in
SlackAvailableNot yetNot built
ZoomNot applicableAvailable, per meetingNot built
Google MeetNot applicableAvailable, per meetingNot built
Buzz · Google Chat · Microsoft TeamsComing soonComing soonComing soon

A meeting platform is not a publishing destination and never will be, which is why its Posts column reads "not applicable" rather than "off". Meetings also connect differently: there's no workspace to authorize, so you invite SageOx into a specific call with its join link.

Chat places are configured per team, in Settings → Communication. What one team connects and publishes stays scoped to that team. Each integration's page says who authorizes the grant — some are personal, some are team-wide, and one grant never implies another.

What's next

  • Slack: publish your team's knowledge into the channels it already watches, and what every control on the settings page does.
  • Team Context: where published knowledge comes from.
  • Context capture: how conversations become knowledge in the first place.