> 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/create-a-website-entry.md).

# Create a Website entry

A ***Web*** entry stores a website address along with the credentials used to sign in to it. Once saved in a vault, the entry opens the site and fills in the sign-in form.

### Create the entry

1. In the ***navigation pane***, select the vault or user vault and the folder in which to create the entry.
2. Select ***Add*** to create a new entry.
3. In the entry type list, select ***Website***, then select ***Continue***.
4. In the ***Name*** field, enter a display name for the entry.
5. Select how the credentials are provided in the *​*​***Credentials***​*​* drop-down menu.
6. In the ***Website*** field, enter the target URL.
7. In the ***Username*** field, enter the account used to sign in to the website.
8. In the ***Password*** field, enter the account password.
9. Select ***Add*** to save.


---

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