Skip to content

Account Settings

On the Account page, you see your plan usage, manage your tracking keys, and see where your data is stored. To open the page, select Account in the BI Pixie Portal sidebar.

Account Info

The Account Info section displays your name, email, and BI Pixie role (Admin or Member), along with your license key. Admins see the account license key. On the Enterprise plan with multiple licenses, members see the license key of the license they are assigned to.

If a payment has failed (past-due status), an additional row appears with a link to Update payment method, which opens the Stripe billing portal. For accounts billed through Azure Marketplace, this link is replaced with Check Azure Billing, which opens the Azure portal where you can manage your Marketplace subscription.

Profile

In the Profile section, you can add optional details: company, job title, department, city, state or region, country, and phone. To update your profile, select Edit, and then select Save.

Plan Usage

In the Plan Usage section of the Usage tab, you see your plan and how much of it you use.

Plan Information

The Plan Usage section shows your plan name (for example, "Pro Plan"), its start date, and its renewal or expiry date.

Usage

  • Tracked Items Used. This meter shows how many of your plan's tracked items are in use. A tracked item is a report with Pixies, or a semantic model or data agent you are preparing for AI. On the Free plan, reports are counted separately from semantic models and data agents, and on every other plan they share one count. For the full definition, see What Counts as a Tracked Item.
  • Sessions (fair use). This informational meter shows the sessions across your tracked reports in the current period against your plan's fair-use allowance. A session is one person using one report on one day. Exceeding this allowance never results in additional charges. Above the Fair-Use Allowance describes what happens when usage goes over it.
Your cost is always fixed. The session meter is informational only. It never becomes a bill.

Above the Fair-Use Allowance

Going over your fair-use session allowance never results in additional charges, and BI Pixie never changes your plan because of it. What happens depends on how far usage goes over the allowance:

  • Over the allowance. A fair-use advisory appears in the Plan Usage section. When BI Pixie stores your telemetry and refreshes your dashboard, and usage stays over the allowance, your daily data refresh limit is reduced until usage drops back below the allowance. Event collection continues.
  • Far over the allowance. BI Pixie also limits how much event data it keeps for your account. Your admins choose how BI Pixie handles that limit, as described in Data Retention at Extreme Usage.

Data Retention at Extreme Usage

Far beyond the fair-use allowance there is a ceiling on how much event data we keep for your account. Admins choose what should happen if it is ever reached:

  • Keep collecting. Tracking continues without a break. Your oldest event data is removed first, and removal stops as soon as your rolling 30-day usage drops back down. This is the default for new accounts.
  • Preserve existing data. Nothing already stored is removed. New events stop being collected until your rolling 30-day usage drops back down, then tracking resumes automatically.

The ceiling on stored event data sits far above the fair-use allowance and is not expected to be reached in normal use. Neither Keep collecting nor Preserve existing data ever affects your bill. Accounts whose telemetry is delivered to their own OneLake never have data removed by BI Pixie.

Limits

  • Data Refreshes. The number of data refreshes used today versus your plan's daily refresh limit.

Usage Notices

When usage crosses a threshold, notices appear in the Plan Usage section:

  • Usage limit warning. You are approaching your plan's usage limits, and BI Pixie pauses event collection if usage keeps rising.
  • Fair-use advisory. Session usage across your tracked reports has run past your plan's fair-use allowance. Your daily data refresh limit may be reduced until usage drops back below the allowance. Data collection is not affected, and nothing is billed.
  • Data refresh access blocked. You have used today's refresh limit, and the notice gives an estimated time when refresh becomes available again.

On the usage notices, admins can select View plans to compare and change plans. Admins also see a link to manage billing in the Plan Usage section: Manage in Azure for a subscription billed through Azure Marketplace, or Billing & Invoices for a subscription paid by card.

Security

In the Security section, you manage your tracking keys and the allowed link destinations in managed reports. This section is hidden when your account is suspended.

Account Tracking Key

Your account tracking key is used to authenticate telemetry data sent from your tracked reports. Without it, usage data is rejected.

The account tracking key is masked by default. You can reveal the full key or copy it to your clipboard.

Rotating the key (admin only):

  1. Select Rotate Key.
  2. Read the warning: reports with Pixies pause tracking until you update them with the new key.
  3. Select Confirm Rotate to proceed.
  4. After rotation, navigate to Add Pixies and update your reports so they use the new key.

Per-Report Tracking Keys

On the Enterprise plan, administrators can enable per-report tracking keys. When per-report keys are on, each Add Pixies run creates one new key. The reports in that run that do not already have a key share it, and a report you add Pixies to on its own gets its own key. When you rotate a report's key, that report gets a new key of its own, and every other report keeps its key.

  • To turn on per-report keys, select Enable.
  • To turn them off, type your account name to confirm, and then select Disable Per-Report Keys. Reports with dedicated keys then pause tracking until you update their Pixies with the shared account key.

Individual report keys can be rotated from the Managed Reports page using the action menu on each report.

How BI Pixie identifies report viewers

In the Security section of the Account page, a BI Pixie administrator chooses how BI Pixie identifies the people who view your reports. Each license has its own choice, and changing the choice for one license does not change the others. A member who is not an administrator sees the choice for their own license and cannot change it.

The section starts closed, and its heading says how many licenses it covers. Select How BI Pixie identifies report viewers to open it. Each license has its own card with the three choices below.

The choice applies only while Capture user identity is on in Tracking Setup. That setting is off for every new account. While it is off, BI Pixie collects no user names, whichever choice is made, and counts viewers by a masked IP address.

  • Email address is the default. BI Pixie stores each viewer's Power BI user name, which is usually their email address, and your reports can show who viewed what.
  • Masked user names stores a masked ID made with a secret key held for the license. The ID cannot be turned back into the user name without that key, and it ends in @masked.bipixie.
  • Not collected stores no identity. BI Pixie groups viewers by a masked IP address, which is less accurate when many viewers share a corporate network or a VPN.

A change applies to events recorded from then on, within 5 minutes, and Pixies do not need to be added again. Events already recorded keep the identity they were stored with, so the same person can appear twice in user counts for the period that spans the change.

Allowed Link Destinations in Managed Reports

When a report tracks link clicks, every link a viewer selects in it passes through BI Pixie on its way to the destination. With a list of allowed link destinations, you make sure those links open only to websites you trust. A link to any other website shows the viewer a short notice instead of opening.

Prerequisites

  • Your account is on the Enterprise plan. On other plans, the section offers Compare plans instead of the list.
  • You are an account admin. Members can see the list but cannot change it.
  • At least one report tracks link clicks, through Track clicks on links in Tracking Setup. A report that does not track link clicks opens no links through BI Pixie, so the list has no effect on it. When no report on the account tracks link clicks, the section says so and offers Open Tracking Setup.

Add allowed link destinations

  1. On the Account page, select the Security tab.
  2. In Allowed link destinations in managed reports, type a website name or an address prefix in Website or address prefix, and then select Add.
  3. Repeat for each destination. The list holds up to 200 destinations, and each can be up to 500 characters long.
  4. Select Save list. When you save the first entries, BI Pixie asks you to confirm, because links to every other website stop opening.

Your reports use the saved list within five minutes.

How an entry matches a link

  • A website name, such as contoso.com, matches every address on that website and on its subdomains, such as finance.contoso.com. It never matches a different website whose name merely contains it, such as notcontoso.com.
  • An address prefix that starts with https:// or http:// matches every address that begins with it. For example, https://contoso.sharepoint.com/sites/finance/ allows that SharePoint site and nothing else on SharePoint.

Remove a destination or clear the list

  1. Next to the destination, select the remove button.
  2. Select Save list.

When you save an empty list, links in reports that track link clicks open to any website again within five minutes.

Considerations and limitations

  • One list applies to the whole account, across every license, workspace and report.
  • The list applies only to links that pass through BI Pixie, which are the links in reports that track link clicks. Other links in Power BI reports are ordinary links, and the list does not affect them.
  • Viewers do not see which destinations are allowed. A blocked link shows them a notice page instead.
  • If BI Pixie cannot load or save the list, your reports keep using the list that was last saved.
  • If your account moves to a plan below Enterprise, BI Pixie keeps the saved list but stops applying it. The list applies again if the account returns to Enterprise. See Plans.

Scripts and AI agents

People in your account can use BI Pixie from scripts that call the BI Pixie API and from AI agents, such as Claude, that act for them. With the Scripts and AI agents setting, you decide whether your account allows that at all. When you turn it off, BI Pixie refuses those calls for everyone in your account, and nobody has to remove a script or disconnect an agent first.

Prerequisites

  • You are an administrator of your BI Pixie account. Members can see the setting but cannot change it.

Turn off scripts and AI agents

  1. Open the Account page and select the Security tab.
  2. In Scripts and AI agents, turn off Allow scripts and AI agents.
  3. In Turn off scripts and AI agents?, select Turn off.

The change applies to the next call each script or AI agent makes, including scripts that run on a schedule.

Turn scripts and AI agents back on

  1. Open the Account page and select the Security tab.
  2. In Scripts and AI agents, turn on Allow scripts and AI agents.

BI Pixie does not ask for confirmation when you turn the setting on, and calls are accepted again from the next one.

What people see while the setting is off

  • A script or AI agent that calls BI Pixie receives this message: "Your organization has turned off access to BI Pixie from scripts and AI agents. An administrator of your BI Pixie account can turn it on in Account settings."
  • On the AI Assistants page, the Use the BI Pixie API card says that your organization has turned off access from scripts and AI agents.
  • The Use BI Pixie MCP Server card says that BI Pixie refuses changes from AI agents, and that questions about usage still work.
  • Administrators also see Change this in Account settings on both cards, which opens the setting.

Considerations and limitations

  • One setting applies to everyone in the account, administrators included, across every license.
  • The setting does not stop anyone from using BI Pixie in the customer portal.
  • The BI Pixie MCP server can still answer usage questions while the setting is off. Those questions read the BI Pixie semantic model through Power BI, with the person's own access, and do not call the BI Pixie API.
  • The setting does not change what a person can reach while it is on. A script or AI agent acts with the same access as the person it acts for.
  • BI Pixie records each change to the setting, with who made it and when.

Related content

Pixies Missing Emails

BI Pixie emails every admin of your account when it has received no usage for seven days from a report it used to receive usage from. A report goes quiet like this when someone publishes it again without its Pixies, and also when nobody opens it for a week, so the email names the missing Pixies as the likely cause rather than the certain one. Members of the account do not receive the email.

Turn the email on or off

  1. On the Account page, select the Overview tab.
  2. In Email notifications, turn Email the admins when BI Pixie stops receiving usage from a report on or off. BI Pixie saves the change at once.

The email is on for every new account.

Considerations and limitations

  • The setting applies to the whole account. Only an account admin can change it. Members see it with an Admins only label.
  • BI Pixie shows the Pixies Missing status on the report's row in Managed Reports whether this email is on or off.
  • BI Pixie does not receive the usage of a report whose usage goes to your own backend, so it does not email you about that report. When every license on the account sends usage to your own backend, the setting is shown but cannot be changed.

Dashboard Data Source

Use this SAS Token to refresh the semantic model of your BI Pixie Dashboard. The Dashboard Data Source card shows a single SAS Token (masked by default). To reveal it, select Show. To copy it, select Copy Token. To issue a new token, select Rotate SAS (admin only).

You paste the SAS Token into Power BI when you first install the dashboard, and again whenever you rotate the SAS Token. For the full walkthrough, see Dashboard Data Source.

Data Region

The Data Region section shows where your analytics data is stored (e.g., "UK South (London)"). Region changes require a manual review and historical data cannot be transferred to a new region. This section is hidden when your account is suspended.

Requesting a Region Change

Administrators can request a region change by expanding the "Request a different region" section:

  • Move to available region: You move to a region that BI Pixie already supports. Historical data from your current region cannot be transferred, so your data in the new region starts fresh.
  • Request new region: You request a region that BI Pixie does not support yet. The BI Pixie team reviews region requests and prioritizes them by demand.

To submit a request:

  1. Select the request type (migration or new region).
  2. Choose the target region.
  3. Select an urgency level and add a note explaining your reason.
  4. Select Submit Migration Request or Submit Region Request.

Leave Account

If you are not the only user on the account, you can leave it, which removes your access to the account. If you are the only admin, you need to promote another member to admin on the Team tab first, so that the account is not left without an administrator. To leave the account:

  1. Open the Licenses tab of Account.
  2. Select Leave account, and confirm.

Danger Zone

If you are an admin of an active account, you can permanently delete it in the Danger Zone section of the Licenses tab.

Warning: Account deletion is immediate and cannot be undone. You must remove all team members before you can delete the account.

Deleting your account will immediately:

  • Stop tracking on all reports and revoke your API key.
  • Remove portal access for all team members.
  • Permanently delete all telemetry data, configurations, and reports.
  • Cancel your card subscription. BI Pixie cannot cancel a subscription bought through Azure Marketplace, which you cancel in the Azure portal, under SaaS resources.

To delete your account:

  1. Select Delete Account.
  2. Type DELETE to confirm.
  3. Select Delete Account again. BI Pixie confirms the deletion, and you can then select Sign out.

Related Resources

What's Next