New Upload weather data from web services into TM1/Planning Analytics โ€” Read the post โ†’

๐Ÿ”’ Securing Your Power BI Reports

Sharing TM1 numbers through Power BI is only useful if the right people see the right data. PowerConnect makes that easy: it translates your existing TM1 security model directly into Power BI security, so the dashboards you publish are governed by the same access rules your finance team has already defined in Planning Analytics.

TM1 security, applied to Power BI

You don't need to rebuild your security model from scratch in Power BI. PowerConnect reads the TM1 permissions you already have at the element-level security, and group memberships โ€” and transforms it into a Power BI Row Level Security.

The result: when a regional manager opens a Power BI dashboard, they see only their region. When the CFO opens the same dashboard, they see everything. The dashboard is shared once; the data each viewer sees is filtered by who they are.

Why this matters

  • One security model, not two โ€” Define access once in TM1. Don't maintain a parallel ruleset in Power BI that can drift out of sync over time.

  • Easy to secure your dashboards โ€” Securing a Power BI dashboard becomes a configuration step, not a project. PowerConnect handles the mapping from TM1 users and groups to Power BI viewers.

  • Confident distribution โ€” Once the dashboard is secured, you can distribute it across your Power BI community without worrying about who sees what. Each viewer's TM1 permissions follow them into Power BI.

  • Audit-ready โ€” Access decisions remain in TM1, where they're already governed, reviewed, and audited. Power BI inherits, rather than replicates.

What this looks like in practice

A single Power BI report can serve every cost centre manager in the business. PowerConnect filters the data on refresh against the viewer's TM1 permissions, so:

  • Each manager sees only their own cost centre, in the dashboard layout everyone shares.

  • The finance team sees the full roll-up in the same dashboard.

  • When TM1 access changes โ€” someone joins, leaves, or moves teams โ€” the change is reflected in Power BI on the next refresh, automatically.

In this section

Securing datasets when using Power BI Service
How TM1 security is enforced through the Power BI Custom Connector in Desktop versus the admin credentials used for refreshes in the Power BI Service, plus approaches to protect data for end users โ€” a self-service refresh model and configuring separate data sources per security portion.

Configuring Row Level Security (RLS)
A step-by-step guide to applying Row Level Security to a joined dataset.