Integrations & SSO

The assistant lives inside the tools your team already uses: sign in with your Microsoft work account, get content-review activity in a Teams channel, and build straight from Figma designs.

Sign in with Microsoft

Every plan includes single sign-on with the Microsoft identity platform (Entra ID). On the sign-in page, choose Sign in with Microsoft and authenticate with your work account — no codes, no passwords held by us. Access is still decided by your workspace seat: signing in identifies you, your admin's invitation authorises you, and an uninvited account is told to ask their admin rather than being let in. Teams that use the email-code sign-in can switch to Microsoft (or mix both) at any time — the same seat is recognised either way.

Microsoft Teams notifications

Route content-review activity into a Teams channel of your choice. When a team member without publish rights asks the assistant for a change, the approval request appears in the channel as a card — who asked, what document, which environment, their note — with a Review & decide button into the portal. When an approver decides, the outcome posts back to the same channel, so nobody re-reviews a settled request. Email notifications continue alongside.

To connect (workspace admins, on the portal's Integrations page):

• In Teams, open the channel that should receive notifications → ⋯ → Workflows → choose “Post to a channel when a webhook request is received” and finish the short wizard.
• Copy the webhook URL it gives you and paste it on the Integrations page. We send a test card and only save once it lands in the channel.

Figma

On Growth and above, connect a Figma personal access token (read-only) and the assistant can implement designs from their exact values: paste a Figma link in chat, it reads the frame's spacing, colours and typography plus a visual render, and builds it. Your Figma files are never modified. See Research, images & documents for the assistant's other built-in skills.