In order to use Mendix, you must sign up to create an account. With this signup you create a MxID, and this ID will be linked to a company. If the company already exists, you will join the company. If it is a new company, a new company will be created and you will automatically join it.
To make changes to the roles, see How to Manage Company Roles and App Roles.
The roles defined within a company and the company’s apps are described below.
2 Company Roles
Everyone with the same email domain will be automatically placed in the same company. For example, all the users that sign up with an email address with the
@bouncetravel.com email domain will automatically join the company named Bounce Travel.
Within the company there are three roles, which are described below.
2.1 Company Admin
The Company Admin is a regular user with additional privileges. The Company Admin role is a “super role” allowed to manage all the settings of the company, including the settings of the company’s apps, cloud nodes, and users. A company can have multiple Company Admins, but regular users cannot see who has the Company Admin role.
For details on this role, see Company Admin Overview.
2.2 Company Contact
Because a company can have multiple Company Admins and regular users cannot see who has the the Company Admin role, making one of the Company Admins the Company Contact is recommended. The Company Contact is visible to regular users. In addition, if they also have the Company Admin role, the Company Contact can perform company operations on behalf of all Company Admins.
To view the Company Contact, follow these steps:
- Go to the Developer Portal.
In the top-right corner, click your avatar and then select My Profile:
Below your name, click your the name of your company.
Below Contact, you will see the Company Contact:
The Company Admin who is the Company Contact can change roles on the Comapny Admin’s Company page.
2.3 Regular Users
Regular Users are all company members. Regular Users can join the company, start building apps, and view other apps made within the company.
Under My Company’s Apps in the Developer Portal, the Regular Users can view the apps made within the company by clicking.
The Regular Users cannot join the apps by themselves. If they want to join an app that they are not a member of, they have to ask any Team Member (with an invite permission) of the app to send an invitation. Because the Team Members are not visible , contact the the App Contact to send the invitation is recommended. Therefore, it is important that the App Contact has the correct permissions to manage the app (for example, the Scrum Master role).
3 App Roles
As a Regular User you can view apps made within the company by clicking My Company’s Apps in the Developer Portal. If you select a specific app, you will see two responsible roles for the app. You can contact them with questions related to the app.
If you are a Team Member of an app, you can view the app roles in Settings > General.
The app roles are described below.
3.1 App Contact
The App Contact is visible to Regular Users and is the go-to person for questions related to the app. If you build your own app, you will automatically become the App Contact and you will have a Scrum Master role within the App Team roles.
If the App Contact changes, it is recommended to provide the new App Contact with the App Team Scrum Master role. The App Contact will be the contact person for Regular Users and will be able to perform app operations on behalf of all Scrum Masters.
3.2 Technical Contact
The Technical Contact manages the technical deployment settings of the app. The Technical Contact can be responsible for different deployment platforms: Mendix Cloud node, on-premises, other plaforms such as MxBlue, Azure etc.
With an app hosted in the Mendix Cloud, the Technical Contact is the first contact for App Team members regarding the Node Permissions and node operations.
Only the Technical Contact is allowed to do the following:
- Manage users with node permissions
- Make adjustments to environments (resize/new environments etc.)
- Manage licenses (renewals/activation/upgrades)
- Configure alert settings
For more information, see Technical Contact.
4 App Team Member Roles
Within an App Team, there are six predefined roles that can be provisioned to App Team members. Company Admins can also create new team roles within the company.
The App Team roles have access to different permission areas based on the following:
- Who can edit the backlog and current sprint
- Who can edit the app model
- Who has access to node information
- Who can change the app settings
Note that the Node Permissions must be provisioned by the Technical Contact.
The predefined roles can be changed in two places:
- As a Company Admin, you can change them, and the changes will effect every app created after the change
- As a Scrum Master, you can change them for the specific app of which you are the Scrum Master
These are the predefined App Team roles:
|Application Operator||A member who does not actively develop the app, but is responsible for operations on the app’s cloud node.|
|Business Engineer||A member of the App Team who contributes to the development of the app.|
|End-user||A user of the app who should have insight into the backlog but doesn’t actively participate in development (for example, a stakeholder).|
|Product Owner||The product owner of the Scrum team who is responsible for managing the app’s backlog.|
|SCRUM Master||The Scrum Master of the Agile App Team. In addition to contributing to development, the Scrum Master manages all the settings within the app. If you create a new app, you will automatically become the Scrum Master.|