RELATED IDEAS
Permission Individual Notes
As a creator of a Note, I need to apply permissions at the individual Note level for sensitive information or until content is ready to be shared.
This functionality exists in Atlassian, Box, and other content mgmt spaces and it's limiting the ability for teams to move content info Aha! & really leverage it as a the source of truth for a Product.
Applying View status for everyone in our company for all products is critical for general transparency & accountability but at the same token, PM's & their teams need to have the flexibility at this level.
-
ADMIN RESPONSEJul 13, 2024
You can now set more granular permissions to control which users are able to view or edit a document!
For example, you could change the default level of access to view-only, and then allow just a few users to edit a document, to prevent accidental changes to strategy or process documents.
Or if you are working on a draft that is not yet ready to share with the entire workspace, you can hide that document from all workspace users, and only allow certain users to view or edit it while you polish up your draft.
You can learn more about this new feature here. It is available as part of our Aha! Knowledge Advanced plan, so please reach out to us at support@aha.io if you are interested in joining a demo or trialing this new functionality. We are looking forward to hearing your feedback about this and other ways to manage your documents, so please let us know!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
Fantastic - thank you so much!
We have an extensive hierarchy with 3 business units, many product families in each business unit, and many products in each family.
We’ve set up Product Managers to be Contributors for their product families
We’ve set up the whole company as Reviewers (we are an ISV, so the majority of our employees are technical in nature).
Our “globally shared” documents that we want to use for sharing the consistent information across our company are put at the top of the hierarchy – Company level.
Company – Shared Notes
Business Unit 1
Product Family 1 or more
Products 1 or more
Business Unit 2
Product Family 1 or more
Products 1 or more
Business Unit 3
Product Family 1 or more
Products 1 or more
We have a leadership team of about 8 product managers that I want to be able to contribute to those central notes, but not put the undue burden on them of being responsible protecting all the data across the company.
We house user guides and some standard procedure documents within Aha!, but the inability to lock editing permissions and see a clear version history is a bit crippling and introduces an amount of risk that we're uncomfortable with.
As a creator of a note I need the ability to restrict read and edits permission only to certain users.
Or least possibility to lock Notes I created from any editing (intentional or accidental) by other contributors.
As a creator of a note I need the ability to restrict read permission only to certain users. I want that only certain people can see a document and that not all users can immediately read the documents I create.
This would be a significant disadvantage compared to Confluence, which we currently use.
I want a way to block other users from making changes on the Notes page.
So that I can keep unexpected/unwanted updates from happening because users thought they were clicking a link, but instead clicked on white space and edited the page.
Luckily, there is "History" to correct the unwanted changes.