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

# Getting Access

Use your **FHNW account** to sign in to AISL applications. Before first use, your account must either be **enabled on request** or have been **pre-enrolled for a module, course, or project**.

{% hint style="info" %}
**Sign in:** Use your FHNW account after access has been enabled for the application.
{% endhint %}

{% hint style="warning" %}
**Test and teaching environment:** AISL-hosted services are not production systems. Availability and data persistence are not guaranteed. Keep your own copies of important work. AISL assumes no liability for data loss.
{% endhint %}

## How access works

For **LiteLLM, Open WebUI, Langflow, and n8n**, access is provided in one of two ways:

* you request access for a course, teaching activity, or project; or
* you are pre-enrolled as part of a module, course, or project.

## Request access

Email <engines@aisl.science> and include:

* the **application** you want to use
* a short description of the **intended use**, such as a course, teaching activity, or project

{% hint style="success" %}
**Request access:** <engines@aisl.science>
{% endhint %}

## Get help

AISL does not provide a formal support service. For access questions or problems using an AISL application, contact <engines@aisl.science>.


---

# 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.aisl.science/getting-access.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.