This documentation is about a version that is out of support, here is the latest documentation version.

How about downloading a newer, supported version?

Profiles overview in Bonita User Interfaces

This page explains what a profile is for a user with the profile Administrator in Bonita Portal.


A profile is an indirection to some entities of the organization: users, groups, roles, and/or memberships. Profiles work as permissions to give access to:

One organization entity can be mapped to several profiles. In Bonita Portal, a logged in user can switch between his/her profiles in the navigation bar.

In development, the creation and edition of profiles is done through the profile editor in Bonita Studio.
In non-production and production, an Administrator can use the Organization>Profiles menu of Bonita Portal.

Changing the mapping of a profile on a non-production or production Runtime may lead to inconsistencies when updating the project or deploying it on another server.
It should only be done to recover from an error temporarily. We strongly encourage you to report all changes in the sources profiles files of the project.

Default profiles


By default, it gives access to the User navigation of Bonita Portal. It includes:


By default, its gives access to the Administrator navigation of Bonita Portal. It includes:

This profile is also mapped to the Bonita Administrator Application, bringing about the same value but with more customization options.

Process manager

This profile is available for Subscription editions only. Someone mapped to the Process manager profile has limited administration rights for activities related to the processes they manage. It includes:

In Bonita ACME organization, all users have the role Member, and the role Member is mapped to all default profiles.
This simplifies process testing (log in as any user to see any Portal content).

Custom profiles

In addition to the default profiles, users of Enterprise, Performance and Efficiency editions can create custom profiles.
To create a custom profile, use the profile editor in Bonita Studio, and map it to entities of the organization.
If a custom profile is created to give access to custom content in Bonita Portal, its Portal menu (navigation structure and pages) must also be defined in the profile. We highly recommend to create the profiles in Bonita Studio so the custom profiles are versioned with the whole project and maintained consistently.
In a production environment, if updating a profile is needed to recover from an issue temporarily, the Administrator can use the _Organization>_Profiles menu.