Skip to Main Content

Share your product feedback

Status Future consideration
Categories Roadmaps
Created by Julia Pence
Created on Mar 4, 2026

User Permissions checking selected workspace rather than records

What is the challenge?

  • To export a report to PowerBI, the workspace selected in the top left must be one where the user has contributor or owner permission, even though the workspace selected there does not have any impact on the report being viewed.

  • Additional case: when viewing a saved kanban view, users cannot drag and drop items if they do not have edit access in the workspace selected in the top left, even if they do have edit access to the records in question.

What is the impact?

  • Additional steps when exporting a report to PowerBI--the user must first make sure they have a workspace selected where they have the appropriate permissions, then open up the report they want to export, then do the linking.

  • General contribution to the impression that Aha is difficult to use and has bizarre design / implementation decisions. Needing to check with an Aha expert (internal or at Aha support) to do what seem like they should be simple tasks.

Describe your idea

  • Allow users with owner or contributor permissions in any workspace to export reports to PowerBI, regardless of which workspace is selected.

  • When checking for permissions to implement certain actions, permissions should be checked based on the item in question, not based on what workspace is selected in the top left.

  • Attach files
  • Julia Pence
    May 19, 2026

    An additional place where this same kind of issue came up: some of my users were accessing a saved kanban view, where the records being shown are in a workspace where they have edit permissions, but the workspace selected in the top left drop down was a different workspace, and they were unable to drag and drop the items into new status columns. Generally Aha seems to use that top selected workspace to determine what permissions users have, when it should be checking for the access relating to the specific records in question, not where the view is coming from.