Bizagi Projects

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio >

Bizagi Projects


To automate your organizational Processes you need to first create a Bizagi project.


A project will automatically create and use:

A process repository

A database created to store your processes and their complete implementation details.


The Work portal for the development environment

A web-based application where you log in and work in the processes, presented exactly the same as the final application that your end users will use in a production environment.

This Bizagi Work portal for the development environment is included by Bizagi Studio so that you can do quick-prototyping and tests while automating the processes.


A Scheduler service

An agent run by Bizagi as a service called Bizagi Scheduler, in charge of running system maintenance, offline and asynchronous tasks, all which you can schedule.


Characteristics of a Bizagi project

Consider the following characteristics to work on a Bizagi project:


1. You may include as many processes as needed

Such processes you may classify and group, in order to consider appropriate browsing in the Work portal and authorization settings for user groups when accessing the different processes.


2. You may configure that a work team can collaborate on the processes implementation

You may host the project in a central server if you wish for other team members to connect and collaborate in the same set of processes.


For more information about the setup for a project when working on a team, and regarding the possibility to define a hierarchical structure for your organizational processes, refer to the Teamwork setup.



With Bizagi Studio, you may have multiple Bizagi projects being hosted on the same server (by using any of the two setup options described above), and work on implementations separately.

Recall that each Bizagi project can contain any number of processes, and multiple projects are not usually needed nor ideal in most cases. Merging information spread in multiple projects is not supported.


Multiple projects should be only needed to deliver different implementations, which is when you do want to have separate databases for each project, a different set of end users accessing each project and possibly using a different type of authentication.

When deploying processes to a production environment (using Automation Server), note that it is recommended to have a dedicated server running one Bizagi project, so that you can have a most accurate sizing for that project, and so that resources consumption or the execution of admin tasks related to the platform of one project do not affect others.