> For the complete documentation index, see [llms.txt](https://docs.dryad.app/dryad-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dryad.app/dryad-documentation/silvanet-suite/silvanet-sma/access.md).
# User access
Access the Site Management app (dryad.app) with user credentials provided by an Admin user.
{% hint style="info" %}
**User role**
* [x] Standard
* [x] Admin
{% endhint %}
## Login to dryad.app
After logging in, the user is required to change their password.
{% hint style="info" %}
**Recommended Browser**
The Site Management app works in all browsers. However, Dryad recommends using Google Chrome to access the Site Management app.
{% endhint %}
1. Before logging in, you must be provided with login credentials
2. Enter the app URL [dryad.app](https://dryad.app). The login page appears.
Login page
2. In the form, enter your **username** and **password** provided to you by Dryad, then select **Sign In**.
Enter your Username and password in Sign-in form
3. If this is your first log in, you are required to change your password. You cannot change your username.
4. Enter a new password in the **Update Password** form, then select **Submit**.
5. The *Dashboard Overview* appears.
## Logout
To logout of the Site Management app, select the **User Profile** icon and from the dropdown menu, select **Logout**.
---
# 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.dryad.app/dryad-documentation/silvanet-suite/silvanet-sma/access.md?ask=&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.
