> For the complete documentation index, see [llms.txt](https://bpmflow.gitbook.io/project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bpmflow.gitbook.io/project/application-manuals/backoffice-manual/main-menu/applications/manage-environments.md).

# Manage Environments

**BPM Flow** support **multi tenant** configuration. Internally each **tenant** is called **Environment**. Only **Backoffice Administrator Users** can set up different **tenants**. Backoffice regular users does **not** have access to **multi tenant configuration**.

Each **Environment** has a collection of **Applications** and **Users**. In a particular **Environment** only **Bpm Processes** of the **Applications** of the **Environment** will be available for the user. A user that is **not** a part of an **Environment** can **not** login to that **Environment**.

Note:\
**Application Names** must be **unique** in the entire **System**. Even in a **Muti-Tenant** installation. If **not** then the creation attempt will be rejected and informed with a **Javascript popup**.

More about **Environments** [here](/project/engineering-models/4+1-architecture-models/logical-view/bpm-environments-or-tenants.md).

![](https://3974112602-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LH4gGgyMb1_fhOg782r%2F-M1kzMzdpXs9FVYm6Tlr%2F-M1kzp_AojmZ4LDpEenH%2Fenvironments-02.png?alt=media\&token=3f93dbd7-f5cf-4f9b-8e45-5314dfbf9f28)

1- Search Environment (or Tenant)

2- List of current Environments

3- Add or Delete an Environment\
In ordered to delete an Environment remove all applications and users from the environment.

4- Set Code Analyzer Level\
The code analyzer is used when process are imported. There are six elements where code can be embedded when the process is imported:\
\* **Loops**: when a loop is defined for a task.\
\* **Queries**: complex queries can be added when filtering processes.\
\* **Scripts**: scripts tasks can be a part of a process definition. \
\* **Start Events**: when a start event has a timer in it.\
\* **Intermediate Events**: timer inside this events.\
\* **Transitions**: when transitions have conditions.\
There are three types of code analyzers:\
\* **High**: it has a list of valid classes and valid selectors to invoke inside the code. \
\* **Medium**: it has a list of valid classes to invoke inside the code. For each class all selectors are valid.\
\* **Low**: any code can be executed.

![](https://3974112602-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LH4gGgyMb1_fhOg782r%2F-M1l-KR-JmBHUZZ5bGON%2F-M1l-y-G8spbwY8ybdMK%2Fimage.png?alt=media\&token=d51cef40-59f6-4205-b184-21976af4783f)

5- Set Icons and Named\
Used to customized names and icons of each environment.

6- Applications of the selected Environment (add/remove applications)

7- Users of the selected Environment (add/remove users)