Headquarters / Use cases

Give distributed teammates the context to continue.

Coordinate distributed teams with presence, chat, company updates, shared documentation, and configured meetings in Headquarters.

For teams working across locations and schedules

When colleagues work at different times, the next person needs to understand what changed, what was decided, and what still needs attention. Team leads coordinate the handoff; contributors share progress; documentation owners maintain the reference material that new teammates will use.

Presence helps colleagues understand availability. Chat supports direct and group discussions. The company feed carries shared updates, Documentation keeps durable knowledge, and Meet supports live discussions where configured.

A handoff that carries its context

Illustrative workflow · distributed team handoff
  1. Share an update

    Use the company feed for a team-wide update and point people to the relevant work or resource.

  2. Clarify the immediate question

    Check presence as an availability cue and use chat to resolve questions with the appropriate colleagues.

  3. Meet when discussion helps

    Use configured meeting capabilities for decisions that benefit from a live conversation. Files, recordings, and analysis depend on organization configuration.

  4. Preserve the decision

    Update the shared documentation and the relevant ticket. Leave a clear next action so the next contributor can continue.

Example: a release handoff between two teams

One team finishes reviewing the setup instructions and posts a feed update with the agreed next step. A colleague in another location sees the update later, reads the shared runbook, and asks a focused question in chat.

When a decision needs more discussion, the lead arranges a meeting using the organization’s configured capabilities. The documentation owner updates the runbook afterward so the answer is available to everyone with access. The example describes a team habit the product can support.

Agree on channels and permissions

Define which updates belong in the feed, which questions belong in chat, and which answers should become documentation. Give each member access to the relevant collaboration products and shared items.

Presence is an availability signal, so agree on response expectations with the team. Choose document visibility for the intended audience and check meeting availability with your administrator before making recordings or analysis part of a required handoff.

Headquarters by Kooya

Explore your company workspace.

Discover how projects, people, and cost visibility come together in Headquarters.