> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/data-flows/services/managing/enabling.md).
# Enabling Services
Enable services in the Connectware Admin UI after uploading a service commissioning file and grant the required resource access.
After uploading a service commissioning file, you must enable each configured service in the Admin UI.
1. In the **Services** view, click the service that you want to enable to open its **Service Details** view.
2. In the upper right corner, click **Enable**.
3. The **Authorization Required** dialog displays the resources that the service must access. Review the requirements, then click **Allow**.
The service shows **Enabling** at the status while creating all resources specified in the service commissioning file. Once complete, the status changes to **Enabled**.
4. Select the **Live Data** tab to get insights into topic activity, message content, and associated resources of your service. For more information, see [Live Data](/2-6-1/monitoring/live-data.md).
{% hint style="warning" %}
If a service does not work as expected, it may have a deviation. Check the [Deviation](/2-6-1/data-flows/services/deviations.md) tab to see all deviated services.
{% endhint %}
## Troubleshooting
### Invalid Service Commissioning Files
If a service commissioning file with invalid resources, references, or other defects is installed, it will fail to be enabled and will result in the service being deviated.
If this happens, manually reinstall the previous working version of the service commissioning file. Keep backups of stable versions so they can be restored when needed.
To prevent such issues, it is recommended to validate your service commissioning files before installation and maintain backups of working configurations.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.cybus.io/2-6-1/data-flows/services/managing/enabling.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
