Where this tenant's content lives — credentials and routing for one or more CMS systems.
How this page works
A connection ties the tenant to one CMS system from the CMS Systems catalogue with that system's credentials. Several connections can be active at once; priority (lower first) and path patterns decide which one serves a request, and primary marks the preferred one among equals.
For Contentstack, fill in the structured fields — region, environment, tokens. For any CMS you can instead paste the raw config and credentials JSON under Advanced; raw JSON always wins over the fields. Expected shapes: AEM {"username","password"}, Contentful {"accessToken","spaceId"}. A Contentstack config names itsregion (na, eu, au, azure-na, azure-eu, gcp-na,gcp-eu); the Substation derives every host from it and rejects hosts that are not Contentstack's.
Test connection makes a real request to the CMS and stores the result on the row, so a failing connection stays visible until it passes.
| Name | CMS system | Environment | Priority | Status | Stored secrets | Last test | Actions |
|---|---|---|---|---|---|---|---|
| eon-com (Nova) primary | contentstack | — all — | 100 | active | API key, delivery token set | OK · 2 h ago |