Gridline Gridline
Integrations

Gridline where project teams already work

Last updated July 14, 2026
Ask grounded project questions and create coordinated action from Slack and Microsoft Teams, without weakening Gridline's firm and project access controls.
In plain terms
  • Slack and Teams native. Channel, thread, group chat, and direct-message workflows.
  • Gridline protected. A signed-in Gridline owner connects every workspace or tenant.
  • Governed and audited. Existing firm, user, project, and action controls still apply.

Sign in before you connect

A Slack workspace or Microsoft 365 tenant can connect only after a Gridline firm owner signs in to Gridline. A Microsoft 365 administrator must also approve the Teams tenant connection. Installation by itself never grants access to Gridline project data.

Every sender must personally sign in to Gridline with Google or Microsoft and bind that session to their Slack or Microsoft identity. Email matching and administrator-created mappings do not grant access. The signed-in user must also be active and authorized in the linked Gridline firm.

Sign in to Gridline or request access for your firm.

Gridline for Slack

Mention Gridline in a project channel or send a direct message to ask grounded questions about project status, RFIs, drawings, specifications, and code requirements. Gridline can also create accountable project tasks without moving the conversation to another tool.

  • Immediate processing feedback, followed by a threaded response.
  • Compact Slack-native formatting with links to governed Gridline sources.
  • Firm-owner connection from protected Gridline settings.
  • Individual Gridline sign-in and immutable Slack user binding.
  • Per-workspace credentials and explicit user authorization for public distribution.

Gridline for Microsoft Teams

Use Gridline in personal chats, group chats, and channels. Answers render as compact Adaptive Cards and preserve links to the relevant Gridline sources. A firm owner and, when required, a Microsoft 365 administrator connect the tenant before project data is available. Every user must then sign in to Gridline with Google or Microsoft and bind their Microsoft identity.

  • Personal, group chat, and team scopes.
  • Standard, Shared, and Private channel readiness.
  • Firm-owner Gridline sign-in plus Microsoft tenant verification.
  • Individual Gridline sign-in qualified by Microsoft subject, home tenant, and issuer.
  • Explicit per-user authorization and audited project actions.

The same Gridline authorization boundary

Slack and Teams are transport surfaces, not separate data stores or bypasses. Gridline verifies the external workspace or tenant, requires the sender to sign in to Gridline, resolves the bound identity to the connected firm, and applies the same user and project permissions used in the web product. Unknown mappings fail closed, and integration messages and actions are audited.

Read the Privacy Policy, Terms of Service, and integration support guide.

Availability

Slack and Microsoft Teams integrations are currently available to Gridline pilot firms. Public marketplace distribution is being prepared with authenticated installation, per-tenant authorization, reviewer fixtures, and platform certification.

Existing Gridline customers can email support@gridlineos.com. New firms can request a tailored demo.