Skip to main content
Brand Atlas integrates with the tools brand teams most often use alongside the portal. The goal is to surface the atlas where the team is already working: Slack notifications, Figma references, webhook events for custom workflows.
Integration availability varies by tier and is being rolled out through 2026. The list below reflects the current and planned set; check Settings → Integrations in your atlas for the live status.

​
Notification integrations

​
Slack

Post atlas notifications to a Slack channel. The integration is one-way: the channel receives notifications; actions still happen in the portal. Configurable events:
  • New Update Requests.
  • Mentions of team members.
  • Milestone publications.
  • Guest Pass activity flagged for review.
Setup: Settings → Integrations → Slack. Authorise the Slack workspace and pick the destination channel.

​
Microsoft Teams

Functionally identical to Slack. Posts notifications to a Microsoft Teams channel via incoming webhook. Setup: Settings → Integrations → Microsoft Teams.

​
Discord

For brands running on Discord. Same one-way notification posting, channel-scoped. Setup: Settings → Integrations → Discord.

​
Design-tool integrations

​
Figma

The Figma plugin lets designers reference Brand Atlas values inside Figma:
  • Colour values pulled from the Colour System.
  • Typography styles pulled from the Typography section.
  • Logo files pulled from the master file index.
When the atlas updates, the Figma file’s references can be refreshed. Setup: install the Brand Atlas plugin in Figma. Authenticate against your atlas. The plugin is available in the Figma community.

​
Adobe Creative Cloud

Coming through 2026. The plan: an Adobe Creative Cloud extension that exposes the Colour System, Typography, and asset library to Illustrator, Photoshop, and InDesign. Setup: not yet available.

​
Content integrations

​
Notion

Embed a section of the atlas inside a Notion page. The embed displays a live read of the section; it updates as the atlas updates. Setup: Settings → Integrations → Notion. Authorise Notion and create the embed in the destination Notion page.

​
Webhooks

For custom workflows. Brand Atlas can fire a webhook on configurable events:
  • Brand record change applied.
  • Update Request raised, approved, rejected, escalated.
  • Guest Pass created, accessed, revoked.
  • Milestone published.
  • Horizon published, archived, restored.
Each webhook receives a JSON payload with the event details. Useful for piping events into a custom dashboard, a project-management tool, or a logging system. Setup: Settings → Integrations → Webhooks. Configure the endpoint URL, choose the events to fire on, and (optionally) configure a signing secret for payload verification.

​
Authentication integrations

​
Single sign-on (SAML)

Available on Guardian, for organisations using SAML-based single sign-on (Okta, Azure AD, Google Workspace, OneLogin). SAML configuration:
  • Identity provider. Pick from the supported list, or configure custom.
  • Domain restriction. Limit sign-up to specific email domains.
  • Just-in-time provisioning. Auto-create team-member accounts on first sign-in from a recognised IdP user.
Setup: Settings → Integrations → SAML. Requires IT-side configuration on the IdP.

​
SCIM

Available on Guardian. Sync team membership and roles from an IdP through the SCIM standard. Reduces the manual work of provisioning and deprovisioning team members. Setup: requires the SAML integration above; SCIM is layered on top.

​
The public API

Brand Atlas exposes a REST API for read access to the brand record and write access to Update Requests:
  • Read. Sections, Horizons, the brand record’s history.
  • Write. Raising Update Requests programmatically.
  • Stream. Webhook delivery as described above.
The API is documented at docs.brandatlas.pro/api. API access is available on Keeper and Guardian with rate limits set per tier.

​
Building your own integration

For workflows none of the above covers, the public API plus webhooks plus the MDX upload format together cover most custom integrations. The atlas is designed to be programmable; the standard integrations are the most common shapes, not the only ones. If you build an integration worth sharing, write to hello@madeby.wtf. We may feature it.

Account and profile

Personal settings.

Authoring in MDX

For Notion and external authoring.

The GitHub-repo content model

For agencies running multiple atlases via Git.