|
| 1 | +--- |
| 2 | +title: "End-Users" |
| 3 | +url: /control-center/end-users/ |
| 4 | +description: "Describes the End-Users page in the Mendix Control Center." |
| 5 | +weight: 30 |
| 6 | +beta: true |
| 7 | +--- |
| 8 | + |
| 9 | +{{% alert color="warning" %}} |
| 10 | +This feature is in Private Beta. For more information, refer to [Release Status](/releasenotes/release-status/). |
| 11 | +{{% /alert %}} |
| 12 | + |
| 13 | +## Introduction |
| 14 | + |
| 15 | +End-user metering is a process that accurately measures the number and types of users interacting with Mendix apps. This is important for ensuring transparency and compliance with license agreements, while optimizing licensing costs. |
| 16 | + |
| 17 | +End-user metering ensures that you benefit from: |
| 18 | + |
| 19 | +* Automatic tracking – User consumption is tracked from the moment your app is deployed to production and running. |
| 20 | +* Monthly reporting – Usage data is collected regularly, processed monthly, and made available in Control Center. |
| 21 | +* App-level visibility – View named user counts per app to identify optimization opportunities. |
| 22 | +* Subscription type classification – Users are classified as External, Multi-App Internal, or Single-App Internal based on their subscription type. |
| 23 | +* Historical data – Access usage data for all the months since enabling user metering. |
| 24 | + |
| 25 | +You can read about the user metering process in [User Metering](/developerportal/deploy/user-metering/). |
| 26 | + |
| 27 | +The **End-Users** page allows you to keep track of end-user subscriptions and usage for all apps across your company. |
| 28 | + |
| 29 | +### User Types |
| 30 | + |
| 31 | +Mendix differentiates between these types of users: |
| 32 | + |
| 33 | +* Multi-app internal user – An employee or a contractor of the customer or of the affiliated company or group who can access any number of apps. |
| 34 | + The associated licensing model is **Multi-App Internal User Subscription**. |
| 35 | + |
| 36 | +* Single-app internal user – An employee or a contractor of the customer or of the affiliated company or group, who holds a subscription for one specific app. |
| 37 | + The associated licensing model is **Single-App Internal User Subscription**. |
| 38 | + |
| 39 | +* External user – A user who is not an employee or a contractor of the customer or of the affiliated company or group. |
| 40 | + The associated licensing model is **External User Subscription**. |
| 41 | + |
| 42 | +For details on user types, refer to the [User Types and Definitions](/developerportal/deploy/licensing-apps-outside-mxcloud/#user-types-and-definitions) section of *Licensing Apps*. |
| 43 | + |
| 44 | +## Overview Tab |
| 45 | + |
| 46 | +The **Overview** tab displays end-user entitlements, and named user details. It also allows you to assign Internal single-app user subscriptions. |
| 47 | + |
| 48 | +### User Entitlements – Active Today |
| 49 | + |
| 50 | +The cards in this section display end-user subscription entitlements, grouped by user type, and valid as of the current date. Each card also includes the expiration date of that subscription. |
| 51 | + |
| 52 | +The information is refreshed in real time. |
| 53 | + |
| 54 | +### Named User Consumption |
| 55 | + |
| 56 | +This section includes a list of apps and their corresponding number of named users for the current month. These are the available details: |
| 57 | + |
| 58 | +* **App Name** – The name of the app. |
| 59 | +* **ID** – The unique ID of the app, with the option to copy it. |
| 60 | +* **Environment Name** – The name of the production environment to which the app is deployed. |
| 61 | +* **Env ID** – The unique ID of the environment to which the app is deployed. |
| 62 | +* **Deployment Type** – The target platform to which the app is deployed. |
| 63 | +* **Usage Extracted On** – The date and time when usage information was recorded. |
| 64 | +* **Named Users** – The number of named users who hold a subscription for the app. |
| 65 | +* **Actions** – This option is only relevant for single-app internal user subscriptions, and it allows you to assign such a subscription to the app. For details, refer to [Assigning Single-App Internal User Subscriptions](#assign-subscriptions). |
| 66 | + |
| 67 | +### Assigning Single-App Internal User Subscriptions {#assign-subscriptions} |
| 68 | + |
| 69 | +If you have single-app internal user subscriptions in your account, you must assign them to apps deployed to production. Follow these steps to do that: |
| 70 | + |
| 71 | +1. In the **Named Users** list, identify the app to which you want to assign a single-app internal user subscription, and click **Assign** at the end of its row. |
| 72 | +2. In the **Assign Internal Single-App User Subscription** dialog box, select a subscription from the **Select Single-App User Subscription** list. |
| 73 | +3. Click **Confirm**. |
| 74 | + |
| 75 | +## Usage Report Tab |
| 76 | + |
| 77 | +The **Usage Report** tab allows you to monitor user entitlements and consumption across all available subscription types over a period of one calendar month. |
| 78 | +The report is generated on the first day of every month for the previous month's usage. As such, the information on this tab is updated every month, and reflects the usage as processed on the last day of the previous month. |
| 79 | + |
| 80 | +### Entitlements & Consumption |
| 81 | + |
| 82 | +This is the information available in the **Entitlements & Consumption** section of the **Usage Report** tab: |
| 83 | + |
| 84 | +* **Usage Month** – Allows you to select the month for which you want to see consumption information. By default, the field is set to the most recent month for which a report is available. |
| 85 | +* Subscription cards – These cards display the entitlements and consumption as calculated on the last day of the selected month. |
| 86 | + |
| 87 | +In case of over-usage, which means that entitlements have been exceeded, apps continue to work, with no consequences to end-users. Over-usage needs to be discussed with the Mendix CSM or representative. |
| 88 | + |
| 89 | +<!-- |
| 90 | +
|
| 91 | +Usage in Apps |
| 92 | +The Usage in Apps section of the Usage Report tab displays the number of consumption units per app, detailed as follows: |
| 93 | +
|
| 94 | +App Name – The name of the app where units were consumed. |
| 95 | +
|
| 96 | +Environment Name – The name of the app environment where units were consumed. |
| 97 | +
|
| 98 | +Deployment Type – The platform to which the app is deployed. |
| 99 | +
|
| 100 | +Multi-App Users – The number of multi-app users who consumed units in the app. |
| 101 | +
|
| 102 | +Single-App Users – The number of single-app users who consumed units in the app. |
| 103 | +
|
| 104 | +External Users – The number of external users who consumed units in the app. |
| 105 | +
|
| 106 | +--> |
0 commit comments