> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/administration/credentials.md).

# Credentials

## Overview

The Credentials View in the Servoy Cloud Control Center allows you to easily access the credentials for different services used or integrated into your application.

{% hint style="info" %}
Please note that these credentials are read-only and are displayed only for copying purposes.
{% endhint %}

### Servoy Admin

The Servoy Admin credentials refer specifically to the authentication details needed to access the admin page of the [Application Server](/reference/application-server.md).

### Tomcat Admin

The Tomcat credentials include the login information required to authenticate and access the Tomcat server.

### Docker AWS parameters

The Docker credentials include AWS parameter information required to set up [on-premise deployment](/reference/servoy-cloud/on-premise-deployment.md) using Docker.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.servoy.com/reference/servoy-cloud/cloud-control-center/administration/credentials.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.