Per-Brand Integrations

Every connection in m18t belongs to one brand, chosen first in the wizard. Learn how that isolates publishing and how to share one API key across brands safely.

What you'll learn

  • Why every connection in m18t belongs to exactly one brand — chosen first, before anything else.
  • How that keeps one brand's content from publishing to another brand's CMS or social account.
  • How to share a single API key across brands without weakening that separation.

The concept: connections are brand-scoped

m18t is multi-brand. If you run Acme and Beta out of one workspace, the system has to make sure an Acme blog post can't land on Beta's Strapi, and a Beta caption can't post to Acme's Facebook Page. It does that by scoping every connection to a single brand.

This isn't a setting buried at the end of a form — it's the first thing the connection wizard asks. Step one is "Pick a brand." Credentials live in that brand's Vault context, and outlets (a Facebook Page, an Instagram account, a CMS instance) belong to that brand. When you publish a content piece, m18t looks at the piece's brand and only offers the connections that belong to it. The others don't appear.

The result: switch the workspace to another brand and the publishing targets change with it. Same UI, a different brand's wiring.

Configuring a connection for a specific brand

  1. Go to Business Settings → Connections (/studio/business/connections).
  2. Click Add Connection.
  3. Pick a brand first — the wizard shows your brands as cards. Choose the one this connection serves. (A brand at its connection limit is marked Full; free a slot or review your plan on the Billing page.)
  4. Pick a provider, then complete the setup, Authentication (Vault key), and — for Meta and Strapi — the Outlets step.
  5. Finish with Create connection.

The connection is now owned by that brand. Switch the workspace to a different brand and this connection won't appear as a publishing target there. (Editing a connection later lets you change its brand if you genuinely need to move it — but the normal model is one brand per connection.)

Sharing one key across brands

You'll often want several brands to use the same API key — one OpenAI account, say, to keep billing simple. m18t handles this without breaking brand separation, because the key in the Vault and the connection that uses it are two different things.

A single connection belongs to one brand. But many connections — across different brands — can reference the same Vault key. So you create one connection per brand, each pointing at the shared key:

  1. Open Add Connection, pick Brand A, pick OpenAI.
  2. On the Authentication step, instead of adding a new key, select your existing one (e.g. OPENAI_API_KEY).
  3. Create the connection.
  4. Run Add Connection again, pick Brand B, pick OpenAI.
  5. On Authentication, select the same OPENAI_API_KEY.
  6. Create it.

AI providers do not need this. m18t's AI features read one workspace-level Vault key directly, so a single Gemini, OpenAI or Anthropic connection already serves every brand. The steps above matter for publishers and CMS connections, where routing genuinely is per brand.

Now Brand A and Brand B each have their own connection record (so routing stays brand-scoped), but both resolve to one encrypted token in the Vault. Rotate that key once and both brands pick up the new value on their next call — see The Secret Vault for how rotation works.

Variations

  • Publishers stay isolated regardless. Even when brands share an AI key, each brand's social and CMS outlets are its own — a shared OpenAI key never lets Brand A publish to Brand B's Page.
  • Per-environment too. Within a brand, a connection is keyed by (brand, service, environment), so you can run Strapi-production and Strapi-staging side by side. See Connect Strapi.
  • Agencies. This is the model that makes agency work clean — each client is a brand with its own connections and (usually) its own client-owned keys. See Agency Mode.

FAQ

Can one connection serve two brands at once? No. A connection belongs to one brand. To use the same provider across brands, create one connection per brand — they can share a single Vault key.

If I share a key, can one brand accidentally publish to another's account? No. Sharing a key shares only the credential. Each brand's outlets (Pages, IG accounts, CMS instances) stay tied to that brand, so publishing routing is unaffected.

Why is a brand greyed out / marked "Full" in the wizard? That brand has hit its connection limit for your plan. Remove an unused connection on that brand, or review usage on the Billing page to free a slot.

I set up a key but the AI button is disabled for this brand. AI is the exception to the per-brand rule, so adding another connection will not help. AI features read a single workspace-level Vault key and their gate ignores brand entirely. Check instead that the connection is showing as healthy, and that its Purpose isn't restricted to a different kind of task. Publishing and CMS buttons are the ones that really are brand-scoped, and for those this answer does apply.

Can I move a connection from one brand to another? Editing a connection lets you change its brand if needed. It's not the everyday path — the intended model is one brand per connection — but it's available for genuine moves.

What's next

Was this article helpful?