App Roles

Last update: Edit

1 Introduction

The roles defined in Developer Portal for an app and team are described below.

2 Team Member

If you want to join an a team, you have to ask a current team member (with the Invite permission) to send an invitation. Because team members are not visible to users outside that team, you can ask the App Contact to send the invite. This means it is important the App Contact has the correct permissions to manage the app (for example, the Scrum Master role).

3 Team Roles

Within a team, there are predefined roles that can be provisioned to team members. Each team role has access to permission areas based on the following factors:

Scrum Masters can edit and create new team roles on the Team page, and Mendix Admins can edit and create new team roles within the company in Control Center.

4 App Contact

When you view the General Settings for a specific app, you will see the two roles responsible for the app: App contact and Technical contact. These are users you can contact with questions related to the app.

The App Contact is visible to regular users and is the go-to person for questions on the app. If you build your own app, you will automatically become the App Contact and you will have the Scrum Master team role.

To change the App Contact, you need to have a Scrum Master role or possess the team Settings permission.

Change the App Contact by going to General Settings, clicking Edit App Info, selecting a new App Contact from the drop-down menu, and finally clicking Update Settings.

5 Technical Contact

The Technical Contact manages the technical deployment settings of the app. The Technical Contact can be responsible for Mendix Cloud or various deployment platforms. A Mendix application will always be set up and delivered with a Technical Contact assigned to it. The Technical Contact for a Free App is assigned when the app is deployed for the first time. The Technical Contact needs an MxID before Mendix can activate a license for an application.

The responsibilities of a Technical Contact depend on whether you are hosting your app in the Mendix Cloud or on premises.

5.1 Mendix Cloud Responsibilities

For apps in the Mendix Cloud, the Technical Contact is the first point of contact for the app. In this scenario, the Technical Contact does the following:

  • Receives notifications for upcoming maintenance operations on the application
  • Can configure the alert settings in the Monitoring tab of the cloud node
  • Can receive alerts from the Mendix app when problems arise (for example, CPU load is high, running out of disk space)
  • Make adjustments to environments (for example, resize and add new environments)

As a Technical Contact, you can perform all the regular operations on the Mendix Cloud node in the Developer Portal. Additionally, you can manage the access rights of your team members so that they can deploy, stop and start the app, and perform other actions. For more information, see Node Permissions.

The Technical Contact is also responsible for managing licenses (as in, renewals, activations, and upgrades) and is the first point of contact for the Mendix Support department. Please note that Mendix is responsible for Mendix Cloud app renewals, and you can contact your Customer Success Manager (CSM) if you want to expand the license.

5.2 On-Premises Responsibilities

When a Mendix app is on premises, it is running on the customer’s own infrastructure. For managing licenses in this scenario, Mendix sends license renewal notifications to the Technical Contact via email. As a Technical Contact, if you want to expand the license (for example, for more users), you need to contact your Account Executive.

5.3 Changing the Technical Contact

To change the Technical Contact, you need to be a Technical Contact.

If you are the current Technical Contact for an app, make another team member the Technical Contact by following these steps:

  1. Navigate to Deploy > Environments.
  2. Select the Permissions tab.
  3. Click Change to Technical Contact for the team member who should be the new Technical Contact. You may have to authenticate first to perform this action. If so, click Change to Technical Contact again after successful authentication to finish this action.