Hi. Sharing Pivot Reports with members of a team working on the same product is fine, but in our organization, certain people work in more than one product, so we have special Pivot Report tracking specific issues to which need to share with these unique people BUT NOT the entire team working with these products. So an interesting feature would be to allow sharing pivot reports with individuals, a bit like we can do in notebooks by adding collaborators (expect that we would need them to be "readers" of the report, hence the Collaborators feature would not accommodate our needs). Be happy to discus any details or reply any question you might have. Thanks!
Thanks for the idea!
We just launched a faster way to share your work, which could help support this idea.
Quickly turn a saved roadmap or report into a webpage. Simply create a link on the view you are working on and share it with anyone (including non-Aha! users).
Learn more here: https://blog.aha.io/share-as-webpage/
To share internally and give editing access to individual users, you could create a Product called "Group name" and give access to a set of users. When sharing views, you could share views specifically with this group only, which would allow only this set of users to access the view.
Adding another request to reconsider, as we frequently would like to allow certain individuals (not groups or people with access to a specific workspace) to view or edit certain reports.
I think the request here is two-fold.
To have the ability to provide access for saved reports & folders at user level rather than at product level. creating a dummy product to handle this is not effective way even though it serves the purpose.
And we should be able to provide access to the same report/folder separate access for view & edit. Currently its either one. These are access level basics which any application should provide.
Please reconsider this idea and change the status from 'Unlikely to Implement'.
yeah, ability to separate the view and edit perms is huge
JIRA & other ticketing systems allow you to create 'groups' of users & then use that group to assign permissions or share reports. It seems silly/unecessary to create miscellaneous Products just to share a report.
Also consider the option to allow editing by certain people (not the group), besides the owner. This would allow maintenance of the report when the owner is not available.
I would love if we can do both. Allow for an option to share with Individuals or with a product. Also, being able to define a group of users associated with the a report or set of reports.
This is more a security controls thing than just a reporting functionality. Controlling access to functions at a product level is ok, but in a world of least privileged access, we need more delineation and separation of duties.
This would be create for all types of reports as there are some reports that would not be useful to some members of staff,
I would love if we can do both. Allow for an option to share with Individuals or with a product.