Overview
Ender Turing performs its analysis through a set of background processing services — components that handle work such as speaker diarization, punctuation, tagging, and segmentation. The Services page is where an administrator can see which of these services are installed on the system, whether they are currently running, and which version is active.
The page supports two jobs:
Operate the services that run on your own system — check status at a glance and start or stop a service when needed.
Point a service at an external endpoint — for selected services you can turn off the local component and have Ender Turing call an external service URL instead.
This page is intended for platform administrators. Day-to-day users never need to open it, and nothing on it changes analytics settings or conversation data directly.
How It Works
Accessing Services
Open Settings from the main navigation.
Select Apps.
Switch to the Services tab.
The tab shows a table of every service currently installed and activated on the system, plus every service that supports redirection.
Who Can Use Services
Reaching the Services tab depends on two separate conditions, and both must be true:
Condition | What it controls |
Access to the Apps section | The Apps entry appears in the Settings menu only for users whose role grants Marketplace Configuration or Integrations Configuration (Manage). Without one of these, there is no way into the section that contains the Services tab. |
System Configuration (Manage) permission | The Services tab itself appears only for users whose role grants System Configuration. Users without it see the other Apps tabs but not Services. |
Users who satisfy only one of the two conditions cannot reach the page. Superusers always have access.
The Services tab is also hidden in multi-tenant deployments. Processing services run at the system level and are managed only in single-tenant (self-hosted) installations.
There is no read-only mode for this page: anyone who can open it can also start, stop, and reconfigure services.
Reading the Services List
The table shows one row per service:
Column | Description |
Name | The service identifier, for example |
Version | The version currently activated for that service. It is empty for a service that supports redirection but has no local version installed. |
Status | Either a set of status chips for the service's containers, or Redirect to: followed by the external URL when redirection is enabled. |
Actions | An edit (pencil) icon, shown only for services that support redirection. |
Each status chip represents one container belonging to the service and is colour-coded:
Green — every container of that component is running.
Orange — some but not all containers are running; the component is still coming up or partially down.
Red — the component is stopped.
Hover a chip to see the container name and how many of its instances are running, for example Running: 1 / 1.
The list refreshes container statuses automatically every few seconds while the page is open, so you can watch a service come up without reloading.
Starting and Stopping a Service
Click a status chip to toggle that component:
Clicking a red chip starts the component.
Clicking a green or orange chip stops it.
After you click, the chip shows a short spinner while the change is applied, and further clicks are ignored until it clears. The chip then settles into its new colour once the automatic status refresh picks up the result.
Stopping a service stops the corresponding analysis for new conversations until you start it again, so treat this as a maintenance action rather than a routine one.
Redirecting a Service to an External Endpoint
Some services can run outside your Ender Turing installation. For these, an edit icon appears in the Actions column. In the current release the services that support redirection are diarization, punctuation, tagging, segmentation, ser, and promise-to-pay.
Because these services always appear in the list, you can redirect one even if no local version has ever been installed on your system.
To configure a redirect:
Click the edit (pencil) icon on the service row. The Update Service form opens.
Name is shown for reference and cannot be changed.
Tick Redirect to external Service.
Enter the endpoint in External Service URL. The address must be a valid
httporhttpsURL, and it is required whenever the checkbox is ticked — the form will not save without it.Click Save.
You are returned to the list, and the service's Status column now reads Redirect to: with the URL you entered.
Enabling a redirect stops and removes the local container for that service. The container status chips disappear from the row while redirection is active, because the work is no longer being done on your system.
To go back to running the service locally, open the same form, clear the Redirect to external Service checkbox, and save. The row returns to showing container status chips, and you can start the local component again from the list.
Redirection cannot be configured for services that are not on the supported list — those rows have no edit icon, and the system rejects the change if it is attempted another way.
Service Versions
The Version column on this page is read-only. Downloading a newer service image and activating a particular version is done on the System page, under the services version list. Once a version is activated there, it becomes the version shown on the Services page.
Things to Keep in Mind
Some navigation entries depend on running services. The Monitoring and Logs entries in the Settings menu appear only while the corresponding
monitoringandloggingservices are fully running. If you stop one of those services here, the matching menu entry disappears until it is running again.Changes take effect immediately. Starting, stopping, and redirecting are applied to the live system as soon as you confirm; there is no staged or draft state and no confirmation dialog.
A stopped service is not an error state. A red chip simply means the component is not running. Check whether it was stopped intentionally before restarting it.
Redirection replaces local processing entirely. While a redirect is enabled, the local component for that service is removed rather than left idle, so plan for the external endpoint to be reachable before you switch over.