> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/how-to-articles/add-a-web-entry.md).

# Add a web entry

Add a web entry in Devolutions Server to store website login credentials, accessible from the web interface or from Remote Desktop Manager.

A Web entry stores login credentials for a website, allowing users to save and retrieve web-based credentials directly from the Devolutions Server web interface or from Remote Desktop Manager connected to a Devolutions Server workspace.

#### Add a web entry from the Devolutions Server web interface

1. Select the vault or user vault, and the folder in which you want to create the entry.
2. Select the ***Add*** button.
3. Select ***Website*** from the entry type list, then select ***Continue***.
4. Configure the entry with the required information.
5. Select ***Add*** to save the entry.

#### Add a web entry from Remote Desktop Manager

1. Open Remote Desktop Manager and connect to your Devolutions Server workspace.
2. Select the vault and folder in which you want to create the entry.
3. Right-click the vault or folder, then select ***Add new entry.***
4. Configure the entry with the required information.
5. Select ***Save*** to add the entry to the Devolutions Server workspace.


---

# 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.devolutions.net/server/knowledge-base/how-to-articles/add-a-web-entry.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.