Merge pull request #6495 from ens60013/PLAT-251799/Destinations-Important-Callouts

PLAT-251799/Update-Important-Callouts-in-Destinations [READY]

Author: Carlo Javier

help/access-control/abac/apply-access-labels-destinations.md

@@ -67,11 +67,12 @@ You can add standard and custom labels to destination dataflows. After you add a
 
 ## Important callouts and items to know {#important-callouts}
 
-Currently, access labels can only be applied to existing dataflows. This means that you need to create a dataflow to a destination before you can apply access labels.
+* Currently, access labels can only be applied to existing dataflows. This means that you need to create a dataflow to a destination before you can apply access labels.
+* You cannot apply an access label to a destination dataflow if you do not have access to that label.
+* When adding multiple labels to a destination dataflow, users who should be able to view and edit the dataflow must be added to a role with at least the same combination of labels. For example, if you apply the labels C1, I2, and another custom label to a destination dataflow, only users added to roles with access to the combination of these three labels are able to view and edit this specific destination dataflow.
+* Destination dataflows that a user does not have access to due to access label configurations may appear in the UI in a greyed-out state; users cannot perform any actions on those dataflows.
 
-You cannot apply an access label to a destination dataflow if you do not have access to that label.
-
-When adding multiple labels to a destination dataflow, users who should be able to view and edit the dataflow must be added to a role with at least the same combination of labels. For example, if you apply the labels C1, I2, and another custom label to a destination dataflow, only users added to roles with access to the combination of these three labels are able to view and edit this specific destination dataflow.
+![The destinations browse catalog with the actions window greyed out.](../images/olac/destinations-greyed-edit.png)
 
 >[!NOTE]
 >

help/access-control/images/olac/destinations-greyed-edit.png

@@ -60,6 +60,10 @@ For more information on destination categories and information on each destinati
 
 ## [!UICONTROL Browse] {#browse}
 
+>[!NOTE]
+>
+>Due to access label configurations, destination dataflows that a user does not have access to may appear in the UI in a greyed-out state. Read the documentation on [using access labels to manage user access to destination dataflows](../../access-control/abac/apply-access-labels-destinations.md#important-callouts-and-items-to-know) for more information.
+
 The **[!UICONTROL Browse]** tab displays the destinations with which you have established a connection.
 
 >[!TIP]
@@ -112,10 +116,6 @@ The **[!UICONTROL Browse]** tab includes enhanced filtering and search capabilit
 
 Use the search bar at the top of the table to quickly find dataflows by name. As you type, the results automatically filter to show only matching dataflows.
 
->[!NOTE]
->
-> When searching for dataflows using the search box, the results may include dataflows which your [user access labels](/help/access-control/abac/apply-access-labels-destinations.md) restrict you from seeing. This behavior will be corrected in a future update. Selecting such dataflows does not display the information in the right rail and users without access to the required labels are not able to perform any modifications such as mapping audiences to the dataflow or editing its schedule.
-
 ![Animated demonstration of searching for a destination dataflow in the Browse tab](../assets/ui/workspace/search.gif)
 
 ### Filter options {#filter-options-browse}

help/destinations/ui/destinations-workspace.md

@@ -17,10 +17,6 @@ There are two types of identities that get linked:
 * **Profile records**: These identities usually come from CRM systems.
 * **Experience Events**: These identities usually come from WebSDK implementation or the Adobe Analytics source.
 
->[!IMPORTANT]
->
->Identity Service is case-sensitive. For example, **abc<span>@gmail.com** and **ABC<span>@GMAIL.COM** would be treated as two separate Email identities.
-
 ## Semantic meaning of establishing links
 
 An identity represents a real-world entity. If there is a link established between two identities, this means that the two identities are associated to one another. The following are some examples that illustrate this concept:
@@ -38,6 +34,7 @@ An identity consists of an identity namespace and an identity value.
 
 * An identity namespace is the context of a given identity value to. Common examples of identity namespaces include CRMID, Email, and Phone.
 * An identity value is the string that represents a real-world entity. For example: "julien<span>@acme.com" can be an identity value for an Email namespace and 555-555-1234 can be a corresponding identity value for a Phone namespace.
+* Identity Service is case-sensitive. For example, **julien<span>@gmail.com** and **JULIEN<span>@GMAIL.COM** would be treated as two separate Email identities.
 
 >[!TIP]
 >

help/identity-service/features/identity-linking-logic.md

@@ -71,16 +71,12 @@ For more information about alerts, read the [[!DNL Observability Insights] overv
 | [Several new destinations that support audience-level monitoring](../../dataflows/ui/monitor-destinations.md#audience-level-view) | The following destinations now support audience-level monitoring: <ul><li>[!DNL Airship Tags]</li><li>(API) [!DNL Salesforce Marketing Cloud]</li><li>[!DNL Marketo Engage]</li><li>[!DNL Microsoft Bing]</li><li>(V1) [!DNL Pega CDH Realtime Audience]</li><li>(V2) [!DNL Pega CDH Realtime Audience]</li><li>[!DNL Salesforce Marketing Cloud] Account Engagement</li><li>[!DNL The Trade Desk]</li></ul> |
 | Dataset export guardrails fix | A fix has been implemented to the dataset export guardrails. Previously, some datasets that included a timestamp column but were _not_ based on the XDM Experience Events schema were incorrectly treated as Experience Events datasets, limiting exports to a 365-day lookback window. The documented 365-day lookback guardrail now applies exclusively to Experience Events datasets. Datasets using any schema other than the XDM Experience Events schema are now governed by the 10 billion records guardrail. Some customers may see increased export numbers for datasets which erroneously fell under the 365-day lookback window. This enables you to export datasets for predictive workflows that have a long lookback window. For more information, read the [dataset export guardrails](../../destinations/guardrails.md#dataset-exports). |
 | Enhanced audience-level reporting for enterprise destinations | After this release, customers will see more accurate audience reporting numbers that include only audiences relevant for the selected destination. This monitoring adjustment ensures reporting includes only audiences mapped on the dataflow, providing clearer insights into actual data activation. This does not affect the amount of data being activated—it is purely a monitoring enhancement to improve reporting accuracy. |
+| UI greyed-out dataflows due to access labels | To address the issue where some users were seeing blank pages because destination dataflows they did not have access to were being completely hidden, the UI now displays those restricted dataflows in a greyed-out state instead of omitting them entirely. For more details, read the documentation on [using access labels to manage user access to destination dataflows](../../access-control/abac/apply-access-labels-destinations.md#important-callouts-and-items-to-know). |
 
 {style="table-layout:auto"}
 
 For more information, read the [Destinations overview](../../destinations/home.md).
 
-<!--
-| [!DNL Snowflake Batch] (Limited availability) | Create a live [!DNL Snowflake] data share to receive daily audience updates directly as shared tables into your account. This integration is currently available for customer organizations provisioned in the VA7 region. |
-| [!DNL Snowflake Streaming] (Limited availability) | Create a live [!DNL Snowflake] data share to receive streaming audience updates directly as shared tables into your account. This integration is currently available for customer organizations provisioned in the VA7 region. |
--->
-
 ## Sources {#sources}
 
 Experience Platform provides a RESTful API and an interactive UI that lets you set up source connections for various data providers with ease. These source connections allow you to authenticate and connect to external storage systems and CRM services, set times for ingestion runs, and manage data ingestion throughput.

help/release-notes/2025/october-2025.md

@@ -72,6 +72,7 @@ For more information about alerts, read the [[!DNL Observability Insights] overv
 | [Several new destinations that support audience-level monitoring](../../dataflows/ui/monitor-destinations.md#audience-level-view) | The following destinations now support audience-level monitoring: <ul><li>[!DNL Airship Tags]</li><li>(API) [!DNL Salesforce Marketing Cloud]</li><li>[!DNL Marketo Engage]</li><li>[!DNL Microsoft Bing]</li><li>(V1) [!DNL Pega CDH Realtime Audience]</li><li>(V2) [!DNL Pega CDH Realtime Audience]</li><li>[!DNL Salesforce Marketing Cloud] Account Engagement</li><li>[!DNL The Trade Desk]</li></ul> |
 | Dataset export guardrails fix | A fix has been implemented to the dataset export guardrails. Previously, some datasets that included a timestamp column but were _not_ based on the XDM Experience Events schema were incorrectly treated as Experience Events datasets, limiting exports to a 365-day lookback window. The documented 365-day lookback guardrail now applies exclusively to Experience Events datasets. Datasets using any schema other than the XDM Experience Events schema are now governed by the 10 billion records guardrail. Some customers may see increased export numbers for datasets which erroneously fell under the 365-day lookback window. This enables you to export datasets for predictive workflows that have a long lookback window. For more information, read the [dataset export guardrails](../../destinations/guardrails.md#dataset-exports). |
 | Enhanced audience-level reporting for enterprise destinations | After this release, customers will see more accurate audience reporting numbers that include only audiences relevant for the selected destination. This monitoring adjustment ensures reporting includes only audiences mapped on the dataflow, providing clearer insights into actual data activation. This does not affect the amount of data being activated—it is purely a monitoring enhancement to improve reporting accuracy. |
+| UI greyed-out dataflows due to access labels | To address the issue where some users were seeing blank pages because destination dataflows they did not have access to were being completely hidden, the UI now displays those restricted dataflows in a greyed-out state instead of omitting them entirely. For more details, read the documentation on [using access labels to manage user access to destination dataflows](../../access-control/abac/apply-access-labels-destinations.md#important-callouts-and-items-to-know). |
 
 {style="table-layout:auto"}