Glossary
What is access profile?
An access profile is a bundle of dashboards and apps that you assign to a group of users in one go. In ENABLE, you use access profiles to manage permissions per group instead of per person.
Access profile explained
Assigning permissions per person works with ten users, but not with a hundred. With a profile you define once what a group needs, for example "branch manager" or "dealer", and attach people to that profile. When a new dashboard is added, you add it to the profile once.
An access profile resembles a role or group in other systems. It decides which dashboards and apps someone sees, but not automatically which rows of data are visible within a dashboard. You handle the latter with row-level security.
Keep profiles simple: a handful of clear profiles is better than a new one for every exception. Regularly check whether people who change roles or leave still have the right profile.
Example
Acme Groothandel has three profiles: "Board" with all dashboards, "Branch" with the branch dashboard and the stock planner, and "Dealer" with only the purchasing dashboard. A new branch manager is given the "Branch" profile and immediately sees the right content.
Access profile in ENABLE
In ENABLE, access profiles bundle dashboards and apps. Customer admins invite users by email, see in a matrix which profiles belong to which dashboards, import users in bulk and use "view as user" to check what someone sees. Profiles can also be linked to Power BI roles for RLS.
FAQ
Frequently asked questions
What is the difference between an access profile and row-level security?
An access profile decides which dashboards and apps someone sees. Row-level security decides which rows of data someone sees within a dashboard. They are often used together.
What is the difference between an access profile and a role?
In practice they are similar: both bundle permissions for a group of users. An access profile in a portal is about which content you see, while a role often also covers what you may do, such as managing or publishing.
How many access profiles do you need?
As few as possible, usually one per clear audience such as the board, a department or an external partner. Too many profiles make management confusing.
Further reading
- PlatformPower BI row-level security and dashboard accessAccess profiles, Power BI row-level security, two-factor authentication and an audit log.Read more
- ResourcesShare Power BI dashboards securely: your optionsYou can share a Power BI dashboard in four ways: Publish to web, sharing in the Power BI service (directly or through an app), inviting external users as B2B guest users, or showing the reports in a portal with Power BI Embedded. For colleagues, the Power BI service is usually enough. To share Power BI dashboards securely with customers, suppliers and other external users, guest users or a customer portal are the right choice; Publish to web is public and never suitable for business data.Read more
- ResourcesRow-level security in Power BI explainedRow-level security (RLS) in Power BI is a security layer in the semantic model that determines which rows of data a user gets to see. Everyone opens the same report, but a regional manager only sees their own region and a customer only their own orders. You define RLS in roles with DAX filters: static with fixed values, or dynamic based on who is viewing.Read more
- PlatformBuild internal apps on your business dataDescribe an app in a chat and the AI Builder builds it on your own data (pilot). Plus all your other apps in one hub.Read more
Use AI on your own data. Securely, and without the headache.
In an online demo we show how ENABLE makes your data securely available and how you build on it: describing an app in the AI Builder, plain-language questions, dashboards and APIs. And how we set it up and manage it for you.