DocumentationGuides & reference
Search across guides and reference articles. Try “email”, “API” or “conditions”.
Builder reference
Service Settings
Manage service identity, access, payments, content, domains, versions and deployments.
10 articles
Identity, content & experience
- Service identity, lifecycle and administrationThese Service settings define how a service is identified, presented and managed over time. Most are set once, but a few—such as reference formats, retention, file…↗
- Service content, branding and languagesThese service settings tailor the presentation of one service without changing the library-wide defaults. Use them to add service-specific guidance, header and footer…↗
- Service navigation, review and PDFsService navigation settings determine how a person starts or returns to a journey, where Continue and Back take them, and how answer documents are presented. These…↗
- Service accessibility statementAn accessibility statement explains how accessible the service is, where it has known limitations, how people can report a problem and how the statement was prepared.…↗
Access & integrations
- Service authentication and user accessAuthentication settings decide who can enter a service, how long they remain signed in, and whether people in the same group can work with the same journey. Configure…↗
- Service files, email and integrationsThese service settings connect a journey to file storage, messages and operational alerting. They should be configured with the library owner and tested in QA using…↗
Payments
Publishing & change management
- Service domains, analytics and deploymentDomain, URL-context and release settings affect how a service is reached, how it behaves when opened from a link, and how safely it moves through QA to production.…↗
- Service change managementChange management is the service’s version history and the safest way to undo or restore Builder changes. Every saved version records its version number, time, change…↗
- Service environments and deploymentsThe Environments area shows how a service is exposed in Prototype, QA and Production. Prototype follows the current Builder design; QA and Production run an…↗