---
sourceDocument: Brazil Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Role based data visibility

# Role based data visibility {#ariaid-title1}

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
AI Control Tower shows value, engagement, and cost data for the AI systems in a user's scope. AI stewards can view data for all AI systems in an instance. Product owners can view data only for the AI systems that they
manage.

AI Control Tower supports two responsibility levels. AI stewards oversee AI systems at the instance level. Product owners oversee individual AI systems.

To access AI Control Tower, users must have either the AI steward role (`sn_ai_governance.ai_steward`) or the product owner (`sn_ai_governance_ai_asset_owner`) role. Users without one of these roles
can't access the application.

## Data scope for each role {#mv-data-visibility-by-ai-control-tower-role__section_scoping_model}

Data scope is based on the Managed by field on the AI system record. If the Managed by field lists a user, that AI system is in the user's scope. AI Control Tower filters value,
engagement, and cost data to that scope.

A product owner's scope is always a subset of an AI steward's scope. For example, an AI steward might see all AI systems in the instance, while a product owner sees only the AI systems that they manage.

Only deployed AI systems are included in calculations. Retired AI systems and AI systems in other states are excluded. As a result, the number of AI systems shown in a chart can be lower than the number of AI systems in the
user's scope.

If a product owner doesn't manage any AI systems, AI Control Tower shows zero values and empty widgets.

## Why access differs {#mv-data-visibility-by-ai-control-tower-role__section_why_scoping}

A product owner has detailed knowledge of the AI systems that they manage and can adjust how those AI systems are measured. Instance-level decisions stay with the AI steward, so a product owner can't change settings that
affect AI systems outside their scope.

Cost configuration is defined at the vendor level. Changes to vendor configuration affect every AI system mapped to that vendor, including AI systems outside a product owner's scope. For this reason, cost configuration is
read-only for product owners.

## When product owners use scoped data {#mv-data-visibility-by-ai-control-tower-role__section_when_encountered}

Product owners use scoped data to review value and engagement results, map AI systems to value templates, and review cost output for the vendors behind their AI systems.
**Related tasks**   

* [Review value and engagement insights for AI systems](https://www.servicenow.com/docs/IURrCywSJA0YPZe~gUfJuA "Use AI Control Tower to review productivity gains, cost savings, and engagement results for AI systems in your scope. AI stewards review data for all AI systems on the instance. Product owners review data for the AI systems that list them in the Managed by field.")  
**Related reference**   

* [Feature access by role](https://www.servicenow.com/docs/T0y3Xo74HDZVc~UkL3p7LQ "Access to features varies by role. The value, engagement, and cost features differ between AI stewards and product owners.")