diff --git a/docs/userguide/reporters.md b/docs/userguide/reporters.md
index 9b1a7e75b..24d1065fe 100644
--- a/docs/userguide/reporters.md
+++ b/docs/userguide/reporters.md
@@ -175,6 +175,16 @@ If you need to produce a colored text output from the custom reporter, then you
 
 It is recommended to create the reporter type in the schema where utPLSQL is installed (by default it is the `UT3` schema). Note that before running the utPLSQL uninstall scripts, all custom reporters should be dropped (cf. [the installation documentation](install.md)). In particular, when upgrading to a newer version of utPLSQL, one has to drop the custom reporters and recreate them after the upgrade.
 
+!!! note
+    Please make sure that grants have been added and synonyms created for the custom reporter in order for reporter to be accessible the same way as other reporters.
+    Assuming that reporter with name `customer_reporter` was created in schema `UT3`
+```sql
+    grant execute on ut3.custom_reporter to public;  
+    create or replace public synonym custom_reporter for ut3.custom_reporter;
+```
+
+
+
 !!! note
     It is possible, but cumbersome, to use another schema for storing the custom reporters. This requires to create a synonym for the base reporter type in the schema that is going to own the custom reporter, and to provide appropriate grants both to the owner of the custom reporter and to the user running the reporter. After upgrading or reinstalling utPLSQL, the extra privileges need to be recreated. This approach is not recommended.