AI Settings
UmbSocial AI writes through Umbraco.AI, with your own provider: Anthropic, OpenAI or another one Umbraco.AI supports. UmbSocial never stores a provider key; the key lives in Umbraco.AI’s connection, under AI › Connections.
The AI settings are a box called AI on Settings › UmbSocial › Schedule & writing, under the page’s own boxes, and the page’s Save saves them with the rest of the page. They need the ManageSettings permission, and UmbSocial must be licensed.
What UmbSocial sets up for you
Section titled “What UmbSocial sets up for you”The first time the page opens, UmbSocial sets up two things in Umbraco.AI, which you then change there like anything else:
- UmbSocial brand voice: an Umbraco.AI context (alias
umbsocial-brand-voice) with one empty brand-voice resource. Fill in your tone, audience, style guidelines and what to avoid under AI › Contexts. It needs no connection, so it is always created. - UmbSocial copywriter: an Umbraco.AI profile (alias
umbsocial-copywriter), once there is an AI connection that can chat. It uses that connection’s first model, a temperature of 0.7 and a system prompt written for social posts, which you can edit under AI › Profiles.
Each is created once: if one with its alias is already there, UmbSocial uses it. If a profile or context the settings point at is deleted, the page points at the defaults again the next time it opens.
No AI connection yet
Section titled “No AI connection yet”A profile needs a connection. Without one, UmbSocial uses the site’s default chat profile, if Umbraco.AI has one. It doesn’t save that choice, so once you add a connection, UmbSocial still creates the UmbSocial copywriter for you.
With no connection and no default chat profile, the box only says: “Add an AI connection under AI › Connections first.”
The settings
Section titled “The settings”| Setting | What it does |
|---|---|
| Profile | The chat profile UmbSocial writes with: its connection, model and system prompt. Only chat profiles are listed. |
| Brand voice | The context that describes your brand. Choose No brand voice to write without one; UmbSocial then leaves it unset and doesn’t create one again. |
| Sites to start from | The sites whose pages Start from a link may read, one per line, such as example.com. Each one covers its subdomains too, so example.com covers www.example.com and blog.example.com. Leave it empty to turn Start from a link off. |
A site is stored as its host name: lowercase, without https://, a path or www., and a name in another script in its ASCII form (bücher.de is stored as xn--bcher-kva.de). An IP address, or a single name such as localhost, isn’t accepted, and there can be at most 20 sites.
Why the lists aren’t Umbraco.AI’s own pickers
Section titled “Why the lists aren’t Umbraco.AI’s own pickers”Umbraco.AI’s profile and context pickers read Umbraco.AI’s management API, which needs access to the AI section. Someone who may manage UmbSocial’s settings doesn’t always have that, so the box lists profiles and contexts through UmbSocial’s own endpoint, which needs only ManageSettings. You still create and edit profiles and contexts in the AI section.
The API
Section titled “The API”GET /umbraco/management/api/v1/umbsocial/pro/ai/optionsreturns{ "profiles": [{ "id", "name", "model" }], "contexts": [{ "id", "name" }], "hasConnection": true }.modelisprovider/model, and only chat profiles are listed.GET /umbraco/management/api/v1/umbsocial/pro/ai/settingsreturns{ "profileId", "contextId", "sourceHosts": [] }, after setting up the defaults described above.contextIdisnullfor no brand voice, andprofileIdisnullonly while there is nothing to write with.PUTto the same address saves a body in that shape and returns the settings as saved, with the hosts normalised. If any part is refused, nothing is saved:
| Code | When |
|---|---|
ai.profile_invalid |
No profile, or one that is gone or can’t chat. |
ai.context_invalid |
A brand voice that is gone. |
ai.host_invalid:<entry> |
An entry that isn’t a host name. |
ai.hosts_too_many |
More than 20 sites. |
All three need the ManageSettings permission, and UmbSocial must be licensed (licence.pro_required otherwise). The values are kept in UmbSocial’s own settings (Umbraco’s key/value store), so every server of a load-balanced site has the same ones.