> 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/common-workflows/starting-an-application.md).

# Starting an application

<mark style="color:$primary;">**Outcome**</mark>\
You launch an application and have it open ready for use.

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

* The application has been added to an Instance you have access to.
* You hold at least the **Instance Editor** role in that instance (applications can only run with Editor rights).
* You are signed in to Nuvolos.

Applications are the interactive tools you use to do your work - JupyterLab, RStudio, MATLAB, VS Code, and others. The procedure below works the same for any role; what differs is who installed the application and where it lives in your space. For the conceptual model, see [Concepts › How Applications work](/concepts/applications.md).

### Start from the Dashboard

The fastest path when the application has been used recently:

{% stepper %}
{% step %}
Go to the Dashboard of the organisation that contains your course or project.
{% endstep %}

{% step %}
Your three most recently used applications are listed.
{% endstep %}

{% step %}
Click the application name to open it.
{% endstep %}
{% endstepper %}

### Start from your Instance

Use this path the first time you start an application, or when the application is not in your recent list:

{% stepper %}
{% step %}
Navigate to the space containing your instance.
{% endstep %}

{% step %}
Navigate to the instance.
{% endstep %}

{% step %}
Make sure you are in the Current state - applications can only run in the Current state, not in a snapshot view.
{% endstep %}

{% step %}
On the sidebar, click the screen icon (applications) to see the Application list.
{% endstep %}

{% step %}
Click the power button or the application name to start it.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Application startup typically takes 30–60 seconds. The first start may take longer if packages or configuration files need to be initialised. If the first start exceeds about 5 minutes, the cohort or environment may need pre-warming - ask the Space Administrator.
{% endhint %}

### Role-specific notes

{% tabs %}
{% tab title="🎓 For instructors" %}
You start applications in the Master Instance to develop and maintain teaching material. To pre-start applications for an entire student cohort (so students don't all wait at once during a session), see [How-to › For Instructors › Pre-start student Applications](/how-to-guides/workflows-for-instructors/configuring-student-applications.md#pre-start-student-applications).
{% endtab %}

{% tab title="📖 For students " %}
If your course uses GPU Lab Sessions, your instructor schedules the GPU-enabled application - you don't start it yourself. Hover over the Application icon to confirm GPU is enabled (a green badge with the GPU model appears). See [How-to › For Students › Work with a GPU in a course](/how-to-guides/workflows-for-students/working-with-a-gpu-in-a-course.md#work-with-a-gpu-in-a-course) for the full distinction between Lab Sessions and On-Demand GPU access.
{% endtab %}

{% tab title="🔬 For researchers" %}
Application startup time matters more for credit-based GPU sizes than for Included sizes - Credit charges start when you click the start button, not when the web UI loads. Make sure you have at least 30 consecutive minutes available before starting a credit-based application.
{% endtab %}
{% endtabs %}