RBAC
Role‑based access control for Advanced Analytics is implemented through Salesforce CRM Analytics licenses and permission sets, combined with Cloudaware’s own RBAC model.
Who Should Have Analytics Access
Typical personas include:
- Cloudaware Administrators – manage integrations, datasets, and core analytics configuration.
- Product/analytics owners – define KPIs, build dashboards, and curate lenses for stakeholders.
- Read‑only stakeholders – consume dashboards and reports without changing configuration.
You can map these personas to Salesforce permission sets and then to identity provider groups (for example, Okta, Azure AD) as needed.
Verify Analytics Platform License in Salesforce
To access advanced analytics dashboards in your Cloudaware account, open Setup from the upper‑right menu:
- Go to Company Information.
- Under Permission Set Licenses, verify that the org includes an Analytics Platform license. This license provides the required CRM Analytics permissions:
- Enable Data Sync and Connections
- Enable dashboard saved views
- Enable CRM Analytics Watchlist
- Enable direct data for external data sources
- Include null values in CRM Analytics queries (by default widgets and lenses exclude rows with null values)
- Allow recipes to use direct data
- Allow users to access Data Manager (Legacy) (to keep the possibility to work with dataflows)
If the license is missing or exhausted, coordinate with your Cloudaware Technical Account Manager before proceeding.
Assign Analytics Permissions to a User
To assign the Analytics Platform license and permissions to a user:
- In Setup, go to Manage Users → Users.
- Open the user record.
- In Permission Set Assignments, click Edit Assignments.
- Add CRM Analytics Platform Admin or CRM Analytics Platform User, depending on the level of access required.
- Click Save.
Then confirm the license:
- From the same user record, open Permission Set License Assignments.
- Click Edit Assignments.
- Ensure that Analytics Platform is selected.
When you assign one of the CRM Analytics permission sets, the corresponding Analytics Platform license is typically granted automatically. The Permission Set License Assignments section confirms that the user now holds an analytics license.
See also: CRM Analytics Permission Set Licenses and User Permissions
Set Granular Permissions to Analytics Data
You can configure granular permissions for data in CRM Analytics datasets and dashboards using row-level security (RLS), field-level security (FLS), sharing inheritance, security predicates, and permission sets.
Setup
- Assign CRM Analytics permission set licenses and custom permission sets, such as "Create/Edit Dashboards": in Cloudaware, go to Setup → Permission Sets.
- Configure FLS for Integration User on source objects.
- In Analytics Studio → Datasets → Edit dataset → Security, toggle sharing inheritance or add predicates, such as
AccountOwner == $User.Name. - Share datasets/dashboards via the Share button, selecting users/groups/roles.
This setup ensures users see only authorized rows/fields without exposing underlying data.
Dataset Permissions
For datasets, enable row-level security via sharing inheritance (applies Salesforce object sharing rules automatically to dataset rows) or security predicates (custom filters like OwnerId == $User.Id or role-based conditions edited in the dataset's security tab).
Grant the Analytics Cloud Integration User read access to source fields via FLS: in Cloudaware, go to Setup → Object Manager for data syncs.
See also: Set Up Dataset Security to Control Access to Rows
Dashboard Permissions
Dashboards inherit security from bound datasets, so RLS/FLS applies automatically; control viewer access via app/folder sharing (Viewer/Editor/Manager roles) or permission sets. Use security predicates for custom row filters, such as territory- or team-based filters, directly in dataset settings post-creation.
See also: Analytics Security Implementation Guide