# Quick start
This page summarizes all the essentials you will need to know to start creating apps with Novacura Flow. Here you can find all best practices and tips to create and run your first app!
## Installation
The apps is developed with the Flow studio, and the Flow studio must be connected to a Flow server. Follow below instructions to install your Flow server and Flow studio so you can start developing your own business apps.
{% hint style="info" %}
**Tip:** Check out the [system requirements](/6.11/system-requirements.md) before the start of the installation 😊
{% endhint %}
### Flow server
[Download](https://home.novacuraflow.com/Downloads/flow%206/latest/Novacura%20Flow%20Server%20Manager%20Installer.exe) and install the server tool, when that is done, do a new installation of the Flow server and components.
**Quick installation guide:**
{% tabs %}
{% tab title="Step 1" %}
{% endtab %}
{% tab title="Step 2" %}
* Click on the menu in the top right corner and choose *Install new*.
{% endtab %}
{% tab title="Step 3" %}
* Choose what Novacura Flow version to install.
* Choose the component/s that should be installed
{% endtab %}
{% tab title="Step 4" %}
* Create a new *Site* in the *Internet Information Services (IIS)* by clicking on *New\...*.
* Enter *Environment name*, for example: Novacura Flow.
* For *Install directory*, browse to the intended folder.
* For *Storage directory*, browse to the intended folder.
{% endtab %}
{% tab title="Step 5" %}
* Enter a *Admin user name*, use this user to log in to the *Novacura Flow Studio*.
* Enter a *Password* for the *Admin user*.
* Select wanted security options.
* Click on *Install* to start the installation.
{% endtab %}
{% tab title="Done" %}
* The installation will be listed here when the installation is successfull
{% endtab %}
{% endtabs %}
**Find a more detailed installation guide here:**
{% content-ref url="/pages/-LtPfxwuDfrda5WEbrp4" %}
[New installation](/6.11/installation-and-upgrade/new-installation.md)
{% endcontent-ref %}
### Flow studio
The Studio launcher supporting launching of different Flow studio versions, so it is easy to connect to different Flow servers, even though the Flow servers have different versions, you don't even have to know which version you are connecting to, the studio launcher takes care of all this, including downloading new versions and updates of the Flow studio.
[Download](https://home.novacuraflow.com/Downloads/flow%206/latest/Novacura%20Flow%20Studio.exe) and install the Flow studio launcher, when that is done, enter the Flow server url or pin code, username and password, and log in.
{% hint style="info" %}
**Tip:** The pin code can be found on the server page, just browse to the server url in a web browser 🌎
{% endhint %}
**Find more information about the Flow studio installation and log in here:**
{% content-ref url="/pages/-LuPStifUgB7SWEHwcrA" %}
[Installation and log in](/6.11/development/flow-studio/installation-and-login.md)
{% endcontent-ref %}
## Users
Users is added under Environment -> Users.
There is three levels of access; AdministerBasicData, AdministerWorkflows and Work, **AdministerBasicData:** Have permisson to the complete studio and can run clients\
**AdministerWorkflows:** Have permisson to the application tab of studio and can run clients\
**Work:** Can only run clients
{% hint style="info" %}
AdministerBasicData and AdministerWorkflows can only access the studio as full users
{% endhint %}
Enter name of the user and a user id, choose the type of the user.\
\
**User types:**
* **Full user:** A full user can log in and run all licensed clients including the portal.
* **Workflow user:** A worklow user will only have permission to run specific granted workflows.
* **Machine user:** A machine user can only run machine workflows, read more about machine workflows [here](/6.11/development/flow-studio/applications/workflow.md).
* **Transaction user:** For every workflow that is started will a transaction be counted.
* **Portal user:** A portal user will only have permission to log in to the portal client.
* **Public user:** A public user can run a workflow without the need to log in.
* **App user:** A user type for application packages.
**Password,** is optional becouse it is possible to authenticate through a connector, AD or openID.
**Read more about users here:**
{% content-ref url="/pages/-LucCtMtJ8mZrRqHFrtI" %}
[Users](/6.11/development/flow-studio/environment/users.md)
{% endcontent-ref %}
## App permissions
Workflows and inboxes are added into menus, roles are connected to menus and users get roles, and by that users getting access to workflows and inboxes.
**Go to Environment -> roles.**
* Add a new roles group, enter group id and group name
* Add roles to the group, click on the + button to add a role.
**Go to Environment -> users.**
* Find the user and click on edit under role tags.
* Select the role that was created, and click OK.
* Click save.
**Go to Applications -> server content.**
* Right click in the server content area, choose new\... -> menu.
* Enter a title for the menu.
* Click on edit roles and select the role that was created.
Now the user can run all apps connected to the menu. \
A quick guide to create your first app can be found here:
{% content-ref url="/pages/-LzCQ2qvmJrTX0DOff0f" %}
[Develop your first app](/6.11/getting-started/develop-your-first-app.md)
{% endcontent-ref %}
---
# Agent Instructions: 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:
```
GET https://help.novacuraflow.com/6.11/getting-started/quick-start.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.