# Manage services in a library Source: https://govform.com/resources/documentation/article/19-manage-services-in-a-library Topic: Library Settings **My services** is the library workspace for finding, organising, creating, duplicating and moving services. Each service card shows its name, stable ID, labels, environment state and latest update time. ## Find the service you need Use **Search services** to match a service name or ID. The label filter includes environment states—Prototype, In QA and Live—as well as labels created in the library. Sort by latest update, service name or environment. The environment label is a quick orientation aid, not a release record. Open the service’s **Environments** screen to verify the exact running version and current status before an operational decision. ## Organise services with labels Select **Add label** on a service card, then choose an existing label or create one with text and a colour. Select an existing label tag to edit or remove it. An edit to a label’s text or colour applies everywhere that label is used in the library. Use labels for stable, useful categories such as team ownership, product area or review state. Do not create a second near-duplicate label for a temporary spelling change. Labels do not grant access, prevent deployment or change the service. Use user roles, sandbox mode and environment controls for those outcomes. ## Create a service Select **Create new service** and choose a starting method: - **Blank service, template or quick starter** — start from a minimal service, a reusable template or a configurable example. - **Upload a Word, Excel or PDF document** — generate a starting service from an uploaded document. - **Enter or paste text that describes your service** — generate a starting service from a written description. Generated services are drafts. Review every page, component, identifier, condition, action and setting before relying on them. Remove source-document personal data and confirm that tables, repeating structures and branching were interpreted correctly. For a manual service, choose a stable lower-case Service ID with hyphens. The ID appears in URLs and integrations and is more costly to change after deployment. ## Duplicate a service **Duplicate a service** copies a selected service into the same library or another library you can access. A copy in the same library requires a different Service ID. Use duplication for a genuinely related starting point, not as an unreviewed backup strategy. ``` flowchart LR A[Select source service] --> B[Choose destination library] B --> C[Enter unique Service ID] C --> D[Duplicate] D --> E[Review identity, access and integrations] E --> F[Test as a new service] ``` After duplication, review library-dependent settings, properties, secrets, feeds, storage links, email, authentication, domains and analytics. A destination library may not contain the same named resources or may point them at a different organisation. ## Move a service or change its ID **Move a service** transfers it to another accessible library. Leaving the destination library unchanged and entering a new Service ID changes the ID within the current library. The service cannot be moved or have its ID changed while it is deployed to QA or Production. Remove it from those environments first. A move or ID change also prevents restoration of the previous version history, so treat it as a high-impact migration. Before moving: 1. Record the current service ID, deployed versions, links and owners. 2. Remove the service from QA and Production under the normal closure process. 3. Inventory library users and shared resources the service depends on. 4. Choose the destination library and required new ID. 5. Confirm redirects or communications for links that will change. 6. Move the service. 7. Reconfigure destination-library dependencies and test in Prototype and QA. 8. Update operational documentation and monitoring. Moving the Builder service does not move files, external accounts, DNS records, spreadsheets or provider credentials. ## Create regular returns or import a definition The creation screen also offers **Set up regular returns** to prepare a Collection programme and return service. Review the programme and return before creating them. Where platform administration features are authorised, blank-service creation also accepts Govform service JSON. The entered Service ID takes precedence; leave the name blank to use the JSON name. Review imported settings and library dependencies before testing or deployment. ## Delete a service and its Darcy conversation Service deletion uses a confirmation dialog and is blocked while the service is deployed. Deleting the Builder service also deletes its saved Darcy conversations. Recreating the same service ID starts with a fresh conversation; deletion in a runtime environment does not remove Builder's Darcy history. See [Service lifecycle and administration](). ## Related guides - [Library settings overview]() - [Library patterns]() - [Service identity, lifecycle and administration]() - [Service environments and deployments]() ## List services through the API An authorised application can discover service IDs and metadata without reading service cards manually. The Builder REST API also exposes field summaries, full current definitions and deployment history. See [List services, metadata and form schemas](). The directory includes undeployed services and confirmed deployment status per environment in `publicationStatus`. Use a direct QA or Production endpoint when you need to check the environment itself.