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!


The apps are 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.

Tip: Check out the system requirements before the start of the installation 😊

Flow server

Download and install the server tool, when that is done, do a new installation of the Flow server and components.

Quick installation guide:

Find a more detailed installation guide here:

pageNew installation

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 and install the Flow studio launcher, when that is done, enter the Flow server URL or pin code, username and password, and log in.

Tip: The pin code can be found on the server page, just browse to the server URL in a web browser 🌎

Find more information about the Flow studio installation and log in here:

pageInstallation and log in


Users are added under Environment -> Users.

There are three levels of access; AdministerBasicData, AdministerWorkflows and Work.

AdministerBasicData: Have permission to the complete studio and can execute apps in the clients. AdministerWorkflows: Have permission to the application tab in the studio and can execute apps in the clients. Work: Can execute apps in the clients.

AdministerBasicData and AdministerWorkflows can only access the studio as full users.

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 use all licensed clients including the portal.

  • Workflow user: A workflow user will only have permission to execute specific granted workflows.

  • Machine user: A machine user can only execute machine workflows, read more about machine workflows here.

  • 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 execute a workflow without the need to log in.

  • App user: A user type for application packages.

Password, is optional because it is possible to authenticate through a connector, AD or OpenID Connect.

Read more about users here:


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:

pageDevelop your first app

Last updated