Library general settings
General settings identify a library inside the Builder. Use them to make the library easy to recognise and to explain what belongs in it. These settings do not change the content of an individual service.
Open the library, select Library settings, then General settings.
Understand the three values
| Setting | What it is for | Guidance |
|---|---|---|
| Library ID | The stable technical identifier used in Builder URLs and integrations. | Treat it as read-only. Record it when an integration or support request needs an exact library reference. |
| Library name | The human-readable name shown to people who work in the Builder. | Name the service area, team or purpose rather than an individual project phase. |
| Description | Optional internal context for other library users. It is not published to service users. | State what belongs here, who owns it and any important operating convention. |
The Builder displays the Library ID rather than asking you to edit it. A library name or description can be updated with Apply.
Write a useful name and description
A good name helps a user choose the correct library before they create, move or deploy a service. Avoid names such as “Forms”, “New library” or “Test” when several libraries could match.
Use the description to answer questions that the name cannot:
- Which services should be created in this library?
- Is it an operational library, a training space or a sandbox?
- Who owns decisions about access, branding and integrations?
- Are there restrictions on the data or environments that may be used?
For example:
Services for customer licensing applications. Owned by the Licensing Product Team. Use the QA environment for integration testing; do not use live customer data in test journeys.
Apply a change safely
- Confirm that the breadcrumb and top navigation show the intended library.
- Update the name or description.
- Select Apply.
- Return to My services and check that the new name is easy to distinguish from other libraries.
- Update internal ownership records if the purpose or owner changed.
Changing descriptive text is low risk, but changing the apparent purpose of a library can lead people to create or deploy services in the wrong place. Tell current library users when a material rename takes effect.