Business Support and Technical Support for Sharing Power BI Reports Securely

• Define which user groups need access before launch
• Keep report names simple and user-friendly
• Avoid exposing internal report names to customers
• Use clear portal categories
• Assign ownership for user access
• Review customer access regularly
• Document who owns each report

• Validate Power BI workspace setup
• Review authentication flow
• Confirm report embedding configuration
• Test access with different user roles
• Check row-level security before launch
• Monitor report performance
• Keep a clear process for adding and removing users

• Design reports for the end user, not only for analysts
• Use clear labels and filters
• Avoid unnecessary complexity
• Test reports with real users
• Confirm data refresh schedules
• Document report logic and ownership

Possible causes:

• The user has not been invited
• The user is using the wrong email address
• The account has not been activated
• Login credentials are incorrect
• Authentication configuration needs review

Suggested solution:

Check that the user has been created, assigned to the correct group and invited with the correct email address.

Possible causes:

• No reports are assigned to the user
• The user is in the wrong group
• The report is not connected correctly
• Power BI permissions are incomplete

Suggested solution:

Review the user’s group membership and report assignments.

Possible causes:

• Incorrect group assignment
• Report assigned to the wrong customer or team
• Permission rules need review
• Power BI row-level security may be misconfigured

Suggested solution:

Remove incorrect access, confirm the correct group and validate the report permission setup.

Possible causes:

• Power BI dataset has not refreshed
• Source data is delayed
• Filters are applied
• Row-level security affects visible data
• The report logic needs review

Suggested solution:

Check the report directly in Power BI and confirm the dataset refresh status.

Possible causes:

• Report page size is not optimized
• Visuals are too wide or too dense
• Browser zoom affects layout
• Report was designed for desktop-only viewing

Suggested solution:

Review report layout in Power BI and test the report in the portal using the expected user devices.

Skald BI is used to share existing Power BI reports in a more controlled, scalable and branded way.

Many organizations already have valuable dashboards and reports in Power BI, but struggle when those reports need to be shared with customers, partners, suppliers or many internal users.

Skald BI solves this by adding a portal layer around Power BI. Users access reports through a branded portal instead of navigating directly inside Power BI.

Skald BI is designed for organizations that already use Power BI and need a better way to distribute reports.

Typical users include:

• SaaS companies sharing analytics with customers
• Consulting firms delivering dashboards to clients
• B2B companies sharing performance reports with partners
• Internal analytics teams distributing reports across departments
• Organizations with many customer-specific or role-specific reports
• Companies that want better control over Power BI report access

No. Skald BI does not replace Power BI.

Power BI is still used for:

• Building reports
• Creating dashboards
• Data modelling
• Visualizations
• Dataset management
• Analytics and insights

Skald BI is used for:

• Secure report sharing
• User access management
• Branded portal experience
• Customer and partner distribution
• Role-based report access
• Cost and license control
• Easier report navigation for end users

For some internal use cases, standard Power BI sharing may be enough.

Skald BI becomes valuable when report sharing becomes more complex. This is often the case when reports are shared with many users, external customers, partners or different user groups.

Common limitations with direct Power BI sharing include:

• External users may get a confusing user experience
• Branding is limited
• User and permission management can become manual
• Customers may need access to several reports in one place
• Different users may need different report access
• Distribution can become difficult to scale
• License and access models may become hard to manage

Skald BI helps solve these issues by creating a dedicated portal for report access and distribution.

Yes. Skald BI can be used as a customer portal for Power BI reports.

This is one of the most common use cases. Customers log in to a branded portal and access the Power BI reports they are allowed to see.

This is useful when your company wants to provide customers with dashboards, KPIs, performance reports or business insights without building a custom portal from scratch.

Yes. Skald BI can be used to share Power BI reports with partners, suppliers, resellers or other external stakeholders.

You can control which users or groups should have access to specific reports.

Yes. Skald BI can also be used internally.

For internal teams, Skald BI can make it easier to organize reports by department, role, function or business unit. This can improve report discoverability and reduce confusion around where users should go to find the right dashboard.

Yes. Your Power BI data stays in your Microsoft tenant. Skald BI adds a secure sharing layer on top.

Skald BI is most useful when your organization:

• Already uses Power BI
• Needs to share reports with customers or partners
• Wants a branded report portal
• Has many users, reports or user groups
• Needs better access control
• Wants to reduce manual reporting administration
• Wants to make Power BI reports easier for non-technical users to access
• Needs a more scalable model for report distribution

Skald BI may not be necessary if:

• You do not use Power BI
• You only share a few internal reports with a small team
• Standard Power BI sharing already works well for your use case
• You need a tool to build reports rather than distribute them
• You are looking to replace your BI platform completely

Skald BI is a distribution and portal layer around Power BI, not a replacement for Power BI itself.

Skald BI is designed to work with your existing Power BI reports. Your reports remain in Power BI, while Skald BI provides a secure portal layer for access and distribution.

The technical setup depends on your Power BI environment, authentication model, workspace structure and report sharing requirements.

Typical setup areas include:

• Power BI workspace access
• Report embedding configuration
• User authentication
• Permission mapping
• Portal structure
• Branding settings
• Report visibility rules

Usually, no.

Skald BI is designed to work with existing Power BI reports. However, some reports may need adjustments depending on how they should be shared.

Possible adjustments may include:

• Separating reports by customer or user group
• Reviewing row-level security
• Simplifying report navigation for external users
• Checking report performance
• Adjusting naming, layout or report structure for portal use

If a user cannot see a report in Skald BI, the most common reasons are:

• The user has not been granted access
• The user belongs to the wrong user group
• The report has not been assigned to that user or group
• The Power BI report or workspace configuration is incomplete
• The user is using the wrong login account
• The report is not published or available in the expected workspace
• Permission mapping between Skald BI and Power BI needs to be reviewed

Recommended checks:

1. Confirm that the user exists in Skald BI.
2. Check which user group the user belongs to.
3. Confirm that the report is assigned to the correct user or group.
4. Verify that the Power BI report is available and active.
5. Check whether Power BI permissions or embedding settings are correctly configured.

For some internal use cases, standard Power BI sharing may be enough.

Skald BI becomes valuable when report sharing becomes more complex. This is often the case when reports are shared with many users, external customers, partners or different user groups.

Common limitations with direct Power BI sharing include:

• External users may get a confusing user experience
• Branding is limited
• User and permission management can become manual
• Customers may need access to several reports in one place
• Different users may need different report access
• Distribution can become difficult to scale
• License and access models may become hard to manage

Skald BI helps solve these issues by creating a dedicated portal for report access and distribution.

If a report does not load inside the portal, common causes include:

• Power BI service availability issues
• Incorrect report or workspace configuration
• Missing permissions
• Authentication problems
• Expired or invalid access tokens
• Browser or session issues
• Report performance problems
• Network or firewall restrictions

Recommended troubleshooting:

1. Reload the page.
2. Log out and log in again.
3. Test the report directly in Power BI.
4. Confirm that the user has access to the report.
5. Check whether other users have the same issue.
6. Review recent changes to report permissions or workspace settings.
7. Contact your Skald BI administrator if the issue continues.

Skald BI is designed as a sharing and portal layer around Power BI reports. Your Power BI reports and underlying data remain managed through your Power BI and Microsoft environment.

The exact data handling model depends on your implementation, authentication setup and hosting configuration. For security-sensitive cases, your technical team should review the architecture, access model and data processing setup before launch.

User authentication depends on your selected setup and organizational requirements.

Common authentication-related questions include:

• Who can log in to the portal?
• Are users managed internally or externally?
• Can customers access reports without using Power BI directly?
• How are user groups managed?
• What happens when a user leaves a customer or partner organization?
• How is access removed?

These questions should be defined during implementation to ensure secure and scalable access management.

Yes. Skald BI is built around the need to show the right reports to the right users.

Role-based or group-based access is important when different customers, partners, teams or departments should only see the reports relevant to them.

Examples:

• Customer A should only see Customer A reports
• Partner users should only see partner-level dashboards
• Internal managers should see management reports
• Local teams should only see local performance data
• Executives should see consolidated reporting

Power BI row-level security controls what data a user can see inside a report.

Skald BI access control manages which reports, portal areas or report experiences a user can access.

In many setups, both can be relevant:

• Power BI controls data-level security inside the report
• Skald BI controls portal-level access and report distribution

Your technical team should decide how these layers work together.

Before launch, review the following areas:

• Which reports should be available in the portal
• Which users or groups should access each report
• Whether reports use row-level security
• Whether external users need access
• Authentication and login flow
• Branding and portal structure
• Report naming and navigation
• Power BI workspace configuration
• License and cost implications
• Support ownership after launch

Try the following:

1. Check that you are using the correct email address.
2. Confirm that your account has been added to the portal.
3. Try resetting your password if applicable.
4. Clear browser cache or try another browser.
5. Contact your internal Skald BI administrator if the issue remains.

Contact your Skald BI administrator and include:

• Your name and email address
• The report you expected to see
• The customer, team or organization you belong to
• A screenshot of what you can see
• The time when the issue occurred

This helps the administrator check your user group, report assignment and Power BI access configuration.

If a report shows old data, the issue is usually related to Power BI data refresh rather than Skald BI itself.

Recommended checks:

1. Check when the Power BI dataset was last refreshed.
2. Confirm whether the refresh failed.
3. Check whether the source system has updated data.
4. Confirm whether the report is using cached or delayed data.
5. Contact the Power BI report owner if the issue continues.

Slow reports are often caused by report design, dataset size, complex calculations or Power BI performance issues.

Recommended checks:

• Test the report directly in Power BI
• Check whether the same issue affects all users
• Review report visuals and filters
• Check dataset size and refresh model
• Reduce unnecessary visuals if needed
• Ask the Power BI report owner to review performance

For business questions, contact your Skald BI owner, customer success contact or account manager.

For technical issues, contact your internal Skald BI administrator or technical support contact.

When reporting an issue, include:

• Your name and email
• Company or customer name
• Report name
• Description of the issue
• Screenshot if possible
• Browser and device
• Time when the issue occurred

No. Skald BI is not a Power BI alternative. It is a secure portal and distribution layer for organizations that already use Power BI.

Skald BI is designed to make existing Power BI reports available through a secure portal experience. The exact technical embedding setup depends on your Power BI environment and implementation model.

Yes, the purpose of Skald BI is to give users a simpler portal-based way to access reports. This is especially useful for customers and partners who should not need to navigate Power BI directly.

Yes. Skald BI supports a branded portal experience so the report environment can feel like part of your own company, customer portal or SaaS product.

Yes. Skald BI makes it easy to set up branded, role-based portals for different clients, regions, or internal teams.

Yes. Skald BI is designed to support controlled report access for different customers, partners, teams or user groups.

Yes. Skald BI can reduce manual work around report distribution, user access and external sharing by creating a more structured portal and access model.

Yes. Your Power BI data stays in your Microsoft tenant. Skald BI adds a secure sharing layer on top.

Skald BI can help organizations gain better control over how Power BI reports are distributed and accessed. However, Power BI licensing depends on your Microsoft setup, user model and commercial agreement.

License questions should be reviewed based on your specific environment.

This depends on your Power BI setup, embedding model, Microsoft licensing and user access requirements. Skald BI should be evaluated together with your current Power BI licensing model before rollout.

Yes. External reporting is one of the strongest use cases for Skald BI.

Examples include:

• Customer dashboards
• Partner performance reports
• Supplier reporting
• Franchise reporting
• Reseller reporting
• Client reporting for consulting firms

Yes. Skald BI can also be used as an internal Power BI report portal, especially when many users, departments or roles need structured access to different reports.