Name of Feature/Request: Ability to prevent editing custom reports used for integrations and API’s
What financial, time savings, or quality of life improvements will occur from this: Ability to prevent editing custom reports used for integrations and APIs | Frequency: Infrequently, but there’s a high potential for things to break if a report is edited inadvertently | Basically I’m just trying to avoid editing a report by accident that is crucial for integration purposes. These reports need to be edited very infrequently, usually in conjunction with a development task. So if we do need to edit it, I’d like it to be very intentional.
In addition, having an audit log of who “unlocked” the report to edit it and when would be useful to confirm if breakage in the integration occurred due to an actual report edit. Ideally we would know what changed in the report as well.
Attempted Solutions So Far: - Limit editing privileges to only those that need it: This helps only to limit who could make this mistake, but still leaves a potential for error with those who have access
- Mark reports as “DO NOT EDIT” for clarity: This can be easy to miss in the report list, and sometimes we make copies of reports for testing purposes which still have this tag. So it’s easy to mix them up.
Digging deep - Any additional Why behind this request / How was this accomplished before Striven in what system or software: Original Description: We have custom reports that are used both internally and for customers for integration purposes (for example, using the API Keys feature), but one thing is that they can be edited at any time, which will probably break the integration. | Previously accomplished: Currently, we just tag reports that shouldn’t be edited as “DO NOT EDIT”
StrivenID: 4261643