> For the complete documentation index, see [llms.txt](https://knowledge.flyability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.flyability.com/getting-started/start-with-elios-3/set-up-the-logins.md).
# Set up the logins
At Flyability, we’ve worked to simplify your experience by minimizing the number of accounts you need to manage.
Your initial login will give you access to key services, including drone activation, the Inspector software, cloud connectivity, and the training simulator, all through a single account.
Please note, however, the access to the Flyability Academy requires a separate account, as it operates on a different platform.
## Steps to Activate Your Drone
* Turn on the tablet included with the drone and connect it to a Wi-Fi network.
* Connect the USB-C cable between the tablet and the remote control.
* Turn on the remote control.
* Open the Cockpit application on the tablet.
* Insert a fully charged battery into the drone and power it on.
* Wait for the Cockpit app to connect to the drone.
* A pop-up window will appear in the app prompting you to register the drone.
Click Register and follow the steps to create your account.
Keep your credential as you will need them after the installation of Inspector and for the simulator.
---
# 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://knowledge.flyability.com/getting-started/start-with-elios-3/set-up-the-logins.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.