Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Dashboards Login: Business Insights / Power BI Credentials Not Working

Dashboards Login: Business Insights / Power BI Credentials Not Working

If a franchisee or club admin user can't log in to Dashboards (Business Insights / Power BI reporting) because the credentials they were given don't work, this article covers what's been reported and the escalation path.

Symptoms

  • A user was given login credentials for Business Insights / Power BI (PBI) reporting, but the credentials do not work when they try to log in.
  • Access was supposed to have been granted to a specific user, but they still can't get in.

Cause

Not established from the ticket data — both sampled tickets show the reported symptom and an internal note that the issue was being routed to a team for a reset, but neither shows the underlying cause (e.g., credential provisioning failure, expired invite, typo in the account setup, etc.). Flag for SME confirmation.

Solution

Option 1: Escalate for a credential reset

No self-service password reset or troubleshooting step is evidenced in the ticket data — in both sampled cases, the resolution path shown is escalating internally to get the user's Dashboards access reset. Contact Enhance Support (or, internally, the team responsible for Business Insights/Power BI access) with: - The user's full name and email address - Club/franchisee name - Confirmation of when access was supposed to have been granted, and by whom (if known)

Prevention

Not established from the ticket data.

Still Having Issues?

If a credential reset doesn't resolve access, escalate to the team responsible for Dashboards/Business Insights provisioning with the details above — this is a distinct product/access system from Manager Suite and Client/Trainer App logins, so front-desk or general support troubleshooting steps for those apps don't apply here.

Related Articles

  • None found covering Dashboards/Business Insights access specifically — this is a content gap beyond what this article documents; the underlying provisioning/reset process should be documented separately once confirmed with the team that owns it.