> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/service-principals.md).

# Service Principals

### Introduction

A Service Principal is a non-human identity that can act like an operator. It gives a process or service access to Command Centre by acting within its privileges on behalf of the process or service. Its actions are recorded as events, similar to operator events.

Service Principals are the preferred alternative to assigning Cardholder operators to processes and services. A Service Principal gets its access the same way an operator does, through Operator Group membership. However, it has none of the extra fields that come with a cardholder record, and you cannot use it to log on to a standard workstation client.

A Service Principal gives a process or service its own identity, which you can audit and revoke without affecting anyone else. This lets you give each process and service only the privileges it needs.

### How Service Principals differ from Operators

* **No logon:** A Service Principal has no password and cannot be used to log on to Command Centre.
* **No Advanced User privilege:** A Service Principal cannot be in an Operator Group that has the Advanced User privilege. Services should never have unrestricted control of Command Centre.
* **No multi-server replication:** Each server manages its own Service Principals. They are not replicated between servers in a multi-server environment.
* **Configuration Client only:** Service Principals can only be configured in Gallagher Configuration Client.

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating a new Service Principal](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/service-principals/creating-a-new-service-principal.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Disabling a Service Principal](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/service-principals/disabling-a-service-principal.md)


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/service-principals.md?ask=<question>&goal=<user_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.
