Before you enable AI
To use AI features, go to Settings > AI.
Before enabling AI, review the data-sharing summary shown on the page.
Data sent to AI providers
When AI is enabled, Cambuildr may send:
Page content and email content you are editing
Custom instructions you define for Cora
Theme settings such as colors, fonts, and styles
Messages you send to Cora
Images referenced in your content
Files and images you attach to the chat
Images from your media library, when you ask Cora to find or use one
The description you give when you ask Cora to generate an image
Content from the websites you have approved under allowed domains, when you ask her to read one
Data not sent
Cambuildr does not send:
Personal data of your contacts
Payment information or donation data
Analytics or tracking data
Your API keys or credentials
This describes Cora, the assistant inside Cambuildr. If you connect an external AI tool over MCP, that tool can also read contact records unless you switch those tools off — see the MCP step below.
Step 1: Enable AI features
On Settings > AI, click Enable AI features.
Once enabled:
Cora becomes available in supported places across Cambuildr
The settings page will show who enabled AI and when
You can later disable AI again if needed
If you disable AI, Cora will no longer be available.
Step 2: Decide whether to use the built-in AI key or your own
In the AI API Key section, Cambuildr uses its built-in API keys by default. You do not have to set anything up to get started.
The built-in key is there so you can try the AI features out. It comes with a limited monthly allowance of AI credits, shared by everyone in your account, and it is not sized for running your day-to-day content production through it. Once AI becomes part of how your team works, connect your own OpenAI key.
Keep the built-in key if you are evaluating AI, using Cora occasionally, or just want the quickest possible start.
Connect your own OpenAI API key if you want AI usage billed to your own OpenAI account. There is then no Cambuildr credit limit — how much you can use is up to your own OpenAI account.
If you connect your own key:
Use an OpenAI API key
The key should start with `sk-`
Treat it as a sensitive credential
Would you rather use a different AI provider? OpenAI is the only provider you can connect your own key for today. If your organisation wants to use another one — for example because of an existing contract or a data-residency requirement — write to us in the chat bubble and tell us which provider you need. We will check whether we can add support for it.
AI credits and your quota
On the built-in key, AI usage is measured in AI credits, and your account has a monthly allowance. The allowance is the same on every plan — it is a trial allowance, not a production budget.
How the allowance works:
It resets at the start of every calendar month. Unused credits do not carry over.
It belongs to the account, not the user — everyone on your team spends from the same pool.
Cora's chat shows how much you have used and warns you when the allowance is running out.
When it is used up, Cora stops working until the next month begins or until you top up. You can top up by writing to us in the chat bubble.
Two things are worth knowing before you plan your month:
Generating images is the most expensive action, and it is charged per image. A handful of generated images can eat a noticeable share of the allowance. Reusing an image from your media library, attaching one to the chat, or linking to one does not cost extra.
Credits do not apply when you connect your own OpenAI key. Usage is then billed to your own OpenAI account instead, with no limit from our side.
If you find your team running out of credits month after month, that is the signal to move to your own OpenAI key.
Step 3: Add customer instructions for Cora
The Customer instructions setting lets you define guidance that is injected into every conversation with Cora.
Use this area for long-term guidance, such as:
Your tone of voice
Writing rules
Campaign priorities
Preferred terminology
Do not use this field for one-off requests, temporary details, or sensitive information.
Step 4: Limit which websites Cora can read
The Allowed domains for getting web content setting controls which websites Cora is allowed to retrieve content from when asked.
Add domains in a clean format such as:
`example.com`
`docs.example.org`
Only add domains that are trusted, relevant, and up to date.
Step 5: Connect an external AI tool (optional)
Everything above is about Cora, the assistant inside Cambuildr. Separately, you can let an AI tool you already use — Claude, ChatGPT, Cursor, VS Code Copilot, Gemini CLI — work on your Cambuildr account from the outside.
That is set up on its own settings page, Settings > MCP, which appears once we switch the feature on for your account. There you copy your server URL, connect your tool, and choose exactly which tools it may use.
Best practices
Keep customer instructions short and evergreen
Put campaign-specific requests into the task prompt
Only allow domains Cora truly needs
Treat AI output as a draft and review it before publishing
Avoid sensitive information in prompts or long-term instructions
Ask Cora to reuse images from your media library before asking her to generate new ones
Treat the built-in key as a trial, and move to your own OpenAI key once AI is part of your routine work
Tell us early if you need a provider other than OpenAI, so we can look into supporting it
When to update your AI settings
Review your AI settings when:
Your brand voice changes
You launch a new campaign strategy
Your website or documentation URLs change
You are regularly hitting the monthly AI credit limit on the built-in key
You want to switch from the built-in key to your own OpenAI key
Your team notices that Cora's output is drifting from your preferred style
Someone leaves the team who had connected an external AI tool over MCP — revoke their access there
Quick checklist
Use this checklist when setting up AI for the first time:
AI features enabled
Data-sharing summary reviewed
Built-in key kept for trying things out, or your own OpenAI key connected for regular use
Team aware that the built-in allowance is limited, resets monthly, and is shared across the account
Team aware of what uses credits up fastest — especially generated images
Customer instructions added
Allowed domains reviewed and limited to trusted sources
Team aligned on how AI content should be reviewed before publishing