> For the complete documentation index, see [llms.txt](https://docs.dropzone.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dropzone.ai/dropzone-101/getting-started.md).

# Getting Started

This section will give you a high level overview of what the platform does and how it works as well as how you can access your tenant grant users access.

The **What's Needed to Use Dropzone** section will give a high level overview of how dropzone works.

The **Accessing Your tenants** section will show you how to connect to a tenant either with your username/password or with various SAML v2 options.

The **Roles and Permissions** sections will discuss the RBAC model used in Dropzone along with information on how to add and disable users.

The **Onboarding with Dropzone** page will give you an idea of what to expect in your onboarding journey with the Customer Success team.


---

# 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.dropzone.ai/dropzone-101/getting-started.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.