How can I make only one specific report read‑only for end users?

[NowNinja727]

Hi everyone,

I’m looking for guidance on restricting edits to a single report ....

We have a use case where one particular report should be read‑only for end users. The issue we’re seeing is that users often open the report, change the filter conditions, and re‑run it — which causes confusion because the data shown no longer matches the intended definition of the report.

The key requirement here is:

• Only one specific report should be non‑editable
• End users should still be able to view but not able to change the filter & run the report
• But they should not be able to modify the filter conditions or save changes
• Other reports must remain editable as usual

I’m exploring whether this can be achieved using ACLs without affecting other reports, or whether there is another recommended pattern for locking down a single report while keeping general reporting functionality intact for users.

Has anyone implemented a targeted “read‑only report” configuration like this?

Looking for best practices or potential ACL/scripted approaches.

Thanks in advance!

[Ankur Bawiskar]

@NowNinja727 

you can create WRITE ACL on sys_report table

Condition: Name = Your Report Name

Advanced Script:

answer = false;

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏