RELATED IDEAS
Restrict ability to convert or copy records
What is the challenge? |
When converting or copying records it can be difficult to trace history for the change. |
What is the impact? |
Unable to quickly understand audit history for a record. |
Describe your idea |
Add the ability to restrict the ability of users to convert or copy records. |
-
ADMIN RESPONSEFeb 18, 2026
We just launched enhanced custom workspace roles with record‑level controls.
You can now create custom roles that govern who can perform sensitive actions (copy, convert, delete, etc.) on most core record types: including goals, initiatives, releases, epics, features, requirements, and ideas. This makes it much easier to apply least‑privilege access at scale and prevent accidental or unauthorized changes.
-
-
-
-
-
-
-
-
-
- +2
4
MERGED
Disable cloning / copying records
What is the challenge? copied records bring over all data fields - including locked fields and fields used to indicate something was a part of a specific planning period What is the impact? there is no way to identify a record has been cloned, or ...
0
Shipped
© 2025 Aha! Labs Inc.•All rights reserved
We have several automations both within Aha and custom built against the API that populate fields for integrations with other systems. These fields are read-only as the data is coming from somewhere else or being calculated. We also need to be able to restrict copying of features and other records or be able to define which fields to include/exclude as part of copying a feature. Today copied features have incorrect information that the user can't clear. This causes a data integrity issue for us.
This will definitely be helpful in identifying copied records that may have data errors. Interested in a similar idea to manage which fields are copied: https://big.ideas.aha.io/ideas/A-I-18135