From 463094043cd9ac08eacfb861391afcc5b7ffd865 Mon Sep 17 00:00:00 2001 From: dalilareis16 Date: Thu, 11 Dec 2025 12:08:40 +0000 Subject: [PATCH] Clarify deduplication The section where we talk about deduplication (" as long as they are assigned to a default tenant, even across user providers.") is confusing to customers. A User Provider can only have 1 default tenant. Therefore, users will only be deduplicated if they belong to different User Providers (same as default tenants). With the current writing, it seems that different User Providers is an optional situation. From different Support cases, we can see that customers believe that this sentence actually means that users in different tenants will be counted as 1 user only (inside the same or different User Providers), as long as one of the users belongs to the Default tenant. This is not true. We only discard users as duplicates if they exist across different default tenants (which, by definition, means different user providers). --- src/licensing/end-users.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/licensing/end-users.md b/src/licensing/end-users.md index 5fba4f78..aba72e3f 100644 --- a/src/licensing/end-users.md +++ b/src/licensing/end-users.md @@ -57,13 +57,13 @@ Each OutSystems subscription has an associated end-user capacity: the maximum nu * If the same individual uses apps in different production runtimes, it is counted in the estimate presented for each of the production runtimes. - * For the purpose of counting users, the platform deduplicates records with the same email address or login, as long as they are assigned to a [default tenant](https://success.outsystems.com/documentation/how_to_guides/development/how_to_build_a_multi_tenant_application/#multi-tenancy-in-outsystems-platform), even across [user providers](intro.md#User-providers). + * For the purpose of counting users, the platform deduplicates records with the same email address or login, as long as they are assigned to different [default tenant](https://success.outsystems.com/documentation/how_to_guides/development/how_to_build_a_multi_tenant_application/#multi-tenancy-in-outsystems-platform). This means that users that exist in the default tenant (different [user providers](intro.md#User-providers)) will count as one unique user. Note that the deduplication does not apply to users assigned to non-default tenants. This means that records with the same email address or login that belong to non-default tenants (same or different User Providers) will still count as distinct users. * Users without an email in neither the **Email** nor **Username** fields always count as internal. * The values displayed on the **User Distribution Per User Provider** table in Service Center show the total number of users without deduplication. - * From Platform Server version 11.11.3 and higher, users are counted by deduplicating records with the same email address or login, as long as they are assigned to a [default tenant](https://success.outsystems.com/documentation/how_to_guides/development/how_to_build_a_multi_tenant_application/#multi-tenancy-in-outsystems-platform), even across user providers. In earlier versions, all users were counted individually without deduplication. + * From Platform Server version 11.11.3 and higher, users are counted by deduplicating records with the same email address or login, as long as they are assigned to different [default tenant](https://success.outsystems.com/documentation/how_to_guides/development/how_to_build_a_multi_tenant_application/#multi-tenancy-in-outsystems-platform), across user providers. In earlier versions, all users were counted individually without deduplication. * Versions prior to Platform Server 11.7.0 don't support classifying end users as internal or external, so customers should update to the latest version to take advantage of this. Older licensing models licensed "named" users, which didn't require end users to be classified as internal or external.