> For the complete documentation index, see [llms.txt](https://docs.replicacyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.replicacyber.com/admin-guide/4.5-admin-guide/readme.md).

# Admin Guide Introduction

Replica supports self-service administration. Use this guide to manage access, configure platform services, and review operational data.

Admin pages cover user and group management, service configuration, and monitoring tools.

## Admin Navigation

Users with admin-level roles see extra items in the left-hand navigation.

Users with the **Admin** role see a dedicated administration section with links to:

* **Egress** — Create and manage egress routers and connectivity options.
* **External Storage** — Configure external storage providers such as Amazon S3 and MinIO.
* **Hardware Devices** — Manage hardware device pools.
* **Text API** — Configure the Text API integration.
* **Telephony** — Configure telephony providers.
* **Zones** — View and manage deployment zones.
* **Users** — Create and manage user accounts, roles, and credentials.
* **Groups** — Create and manage groups used to organize resources.
* **Proxy Management** — Configure proxy settings.
* **Notifications** — Send platform-wide or targeted notifications.
* **Logging** — Open the log search and analysis interface.
* **Monitoring** — Open the platform monitoring dashboard.


---

# 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.replicacyber.com/admin-guide/4.5-admin-guide/readme.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.