Integration · Build & run
Drafts in. Publishing behind approval.
Brigham.ai can put a draft in your CMS. Making it public is a separate step that needs a yes.
How content moves
1
Draft
Brigham.ai writes a draft into the CMS as a draft.
2
Review
You read it where your editors already work.
3
Approve
Publishing goes through the approval engine.
Scopes and access
- Connects as
- A scoped connection per site or tenant
- Access
- Read-only by default
- Reads
- Published and draft entries
- Writes
- Create and edit drafts (separate grant)
- Needs approval
- Publishing, unpublishing or deleting
- Visibility
- Only the sites the connection is scoped to
- Availability
- Available
Yours to connect, yours to revoke.
Each person connects their own accounts from the Connections page. Every connection can be revoked on its own, and every connection starts read-only. A write scope is a separate, explicit grant.
- Credentials are encrypted at rest and referenced by id. They never appear in model context, logs or tool results.
- Each agent gets its own connection grants.
- Tool results from outside sources are untrusted data. They cannot approve anything.
Ask it
- ›“Draft a post from this outline and save it as a draft.”
- ›“Which posts are still in draft?”
- ›“What did we publish last month?”
Questions, answered.
Can Brigham.ai publish a post?
Only after approval. Drafts are the default.
Keep reading.
Marketing & GrowthSearch Console, analytics, ad accounts and your CMS compared across brands. Brigham.ai drafts posts and proposes changes. Publishing and budgets wait for you.Read →
Search ConsoleBrigham.ai reads Google Search Console to report clicks, queries and indexing trends, and to explain a traffic change in plain words. Read-only.Read →
Drafts & outreachBrigham.ai writes replies into Gmail Drafts and never sends them itself. Follow-ups are checked against the CRM. Sequences need approval.Read →