> For the complete documentation index, see [llms.txt](https://docs.nuvolos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvolos.com/how-to-guides/workflows-for-instructors/configuring-student-applications/configure-applications-for-student-use.md).

# Configure Applications for student use

<mark style="color:$primary;">**Outcome**</mark>\
You set Application configuration and distribute it to all students at once.

<mark style="color:$primary;">**Before you start**</mark>

* You are a Space Administrator of the course.
* The application exists in the Master Instance.

Space Administrators can configure student applications in two ways:

* **During creation** - expand **Application configuration** on the **Application Resources** step before clicking **Create Application**.
* **Per application, per instance** - configure through the web UI. Affects only that application in that instance.
* **Via distribution** - configure the application in the Master Instance, then distribute it. Configuration is included with the distribution and applied to every student application.

When distributing applications in course spaces, three configuration values are particularly important and travel with the application:

* **Inactivity limit** - how long the application stays running without student interaction.
* **Shared mode** - whether multiple users connect to the same running application.
* **Home persistence** - whether session data in the home area persists between restarts.
* **Connectivity** - which other Nuvolos Applications may connect.
* **Add-ons** - optional services and packages attached to the Application.
* **Resource settings (size)** - how many NCUs the application uses.
* **Share Allocation** - the fractional GPU or accelerator allocation for supported resources.

For all configurable options and their effects, see [Reference › Applications](/reference/applications.md).