How do I provide access for a non-admin user to create (View/Run) Reports?

[Vamsi Sreenivas · Accepted solution]

Hi @Sandra Mack , you can provide report_user role to the user you want to create/run reports.

Mark my answer as HELPFUL / CORRECT if this help resolve your issue.

Regards,

Vamsi S

[Community Alums]

Hi @Sandra Mack ,

Users with a reporting role can create and customize reports.

Control which users and groups can see a report in their Reports list.

Role required: report_admin, report_global, or report_group.

Note: Users who do not have the report_admin, report_global, or report_group roles do not see the share menu in Report Builder.

Here are you reporting roles :

Report roles

Role title[name]	Description
No role	Can view reports that are shared with them.
itil [itil], report user [report_user]	Can create and view reports that have been shared with them. Cannot share, edit, or delete reports that have been shared with them.
report publisher [report_publisher]	Can Publish reports that they can manage. Publishing a report creates a public link to that report. Users with this role must also have another role that grants permission to create, edit, and share reports.
report scheduler [report_scheduler]	Can Schedule emailing of all reports that they can see, including reports they cannot manage. Users with this role must also have another role that grants permission to create, edit, and share reports.
group report user [report_group]	Can manage and share reports that are shared with them (listed in Group).
global report user [report_global]	Can manage reports that are shared with everyone (listed in Global).
report administrator [report_admin]	Can manage, share, publish, and schedule all reports. Can access Reports > Administration and manage all report-related objects. The report_admin role inherits all other report roles.
report description administrator [report_description_admin]	Can read and update table and field descriptions for reports.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep