> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-administration/platform-administration.md).

# Platform Administration

Xygeni platform is based on a downloadable scanner that performs the analyses on the customer premises and uploads the results to the cloud service. The scanner typically runs at certain points in the DevOps build/deployment process (like in CI pipelines). As there could be multiple non-persistent scanner instances running, a *central configuration* permits each scanner to use the configured detectors relevant for the target software under analysis.

Xygeni provides facilities for managing the organization resources in the platform: *User accounts*, software entries ("*projects*"), *policies to enforce* for the projects, and *security configuration* tasks like creating API tokens. This guide documents also how to perform such administrative tasks.

You can reach the administration section under **Settings** icon.

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2FFdJp66iVmmvehCyw1C44%2Fimage.png?alt=media&amp;token=418f8b1e-caf8-4d83-acda-0f69dc622917" alt=""><figcaption></figcaption></figure>


---

# 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.xygeni.io/xygeni-administration/platform-administration.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.