Microsoft Teams
Learn how Giga can be used from Microsoft Teams while keeping Giga's live company context and permissions underneath.
Microsoft Teams is an official Giga surface.
When Giga is available in your Teams environment, you can work with Giga from Microsoft Teams while the underlying workspace context, permissions, and connected capabilities continue to come from Giga.
The Giga model stays consistent
Using Microsoft Teams changes the interface around the work.
The same core Giga primitives still apply:
The current Teams integration determines how those capabilities are presented.
Company Brain remains permission-aware
Giga’s Company Brain stays scoped to what the current user is allowed to access.
Depending on the current session, that can include relevant:
- workspace and Group context
- Track context and memory
- files
- Agent and Skill context
- Connections and live external data
- user-level context
Opening Giga from Teams does not widen that access.
Permissions stay with Giga
Giga should only retrieve or use company context the current user and session are allowed to access, regardless of the interface being used.
Work with Giga from Teams
The exact actions available depend on the current Microsoft Teams integration and live tool environment.
Where supported, Giga can help with work such as:
- answering questions from permitted company context
- working with an explicitly selected Track
- using available Connections
- applying available Skills
- creating or updating supported work product
- taking actions exposed by the current Teams and Giga environment
Giga should verify the live surface before claiming that a specific Teams action is supported.
Tracks still require explicit selection
A Chat can link to at most one Track.
Giga should never infer a Track from a Teams chat, channel, meeting, or topic alone.
The Track should be explicitly selected or confirmed because Track attachment affects where observations from the Chat can become retrievable.
Connections stay permission-aware
Connections continue to come from the Giga workspace.
A Connection being available elsewhere in Giga does not prove every related action is exposed in Microsoft Teams.
Giga should resolve:
- whether the user can access the Connection
- whether the current Teams surface exposes the needed capability
- what the external provider allows
- whether the requested action needs confirmation
File behavior follows the current Teams surface
File display and upload behavior can differ across Giga surfaces.
For Microsoft Teams, Giga should use the file capabilities exposed by the current integration rather than assuming the same viewer, upload, or artifact behavior as Web or Slack.
Learn about working with files →
Teams vs other surfaces
Microsoft Teams
Use Giga from the Teams environment with the capabilities available there.
Giga Web
Use Giga’s first-party web interface with its web-specific viewer and rich UI where supported.
Slack
Use Giga from Slack with Slack-specific messaging, file, and action behavior.
ChatGPT and Claude
Use Giga from other supported AI interfaces while keeping the same permission-aware workspace underneath.
A simple example
Imagine a team member asks Giga for project context from Microsoft Teams.
Ask from Teams
Start the request from the Teams surface.
Resolve Giga permissions
Giga checks the current user, Groups, Connections, and explicitly selected Track.
Use the relevant context
Giga retrieves the permitted company context and capabilities available for the task.
Return the result in Teams
Giga responds through the presentation and action capabilities supported by the current Teams integration.
Image placeholder
Diagram showing Microsoft Teams → Giga permission layer → Company Brain / Track / Connections → response back in Teams.