Use this guide to make your first WebReports report available to the right users. Follow the setup sequence, then test that an intended user can find and run the report.
If you only need to run existing reports, use Getting Started as a WebReports User.
Before you begin
This guide assumes WebReports is already installed and its site is accessible. If it is not, start with Installation and Setup.
Have the following ready:
- Your organization’s WebReports URL and an administrator account.
- Access to VDM and a working report or View to publish.
- The connection information for the report’s data source.
- The users who need the report and the actions they should be allowed to perform.
Start with one report and one intended user. Where a connection, role, or account already exists, review it and reuse it if it fits the setup.
1. Sign in as an administrator
Open your WebReports URL and sign in with your administrator account. The Admin role provides access to the management and configuration features used below.
2. Configure the report’s data connection
In WebReports, open Management → Connections. Create or review the connection profile for the database or data source the report will use. Test the connection and save it.
Ready to continue: WebReports can successfully connect to the intended data source.
Instructions: Managing Connections in WebReports.
3. Connect VDM to this WebReports site
Before connecting from VDM, confirm that the WebReports account used for publishing has the required Publisher permissions and access to the connection profile from step 2. Have the site’s authentication details and administrator-provided WRXValue ready. In VDM, configure a WebReports connection profile for that site and select the intended data connection.
This serves a different purpose from step 2: the data connection lets WebReports reach your reporting data; the VDM connection lets VDM communicate with the WebReports site.
Instructions: Creating A WebReports Connection Profile In VDM.
4. Publish one working report
Confirm that the report runs successfully in VDM, its required parameters are configured, and its name and description will make sense to users. Publish it to the WebReports site selected in step 3.
Ready to continue: the report has been published to the intended WebReports environment. Publishing alone does not grant users access.
Instructions: Publishing Views to WebReports.
5. Choose or create the role for report access
Open Management → Roles. Choose an appropriate existing role, or create a custom role for the users who should receive this report.
Review which roles grant application features and which roles group users for report assignments. A user may need both feature permissions and a role with access to the report.
Instructions: Managing Roles in WebReports and Understanding Default Roles and Permissions in WebReports.
6. Assign the report to that role
Open Management → Assignments. Add an assignment for the published report, the correct connection profile, the intended role, and the required report type. Set the expiration period for completed results.
Ready to continue: the role has an assignment for the correct report, connection, and report type.
Instructions: Managing Report Assignments in WebReports.
7. Create the user account and assign roles
Open Management → Users. Create or edit the intended user’s account and assign the role used in step 6, along with the roles needed for the actions they should perform. Save the changes.
Users with multiple roles receive the combined permissions and report access from those roles. Review the complete role list before handing over access.
Provide the user with the WebReports URL and the appropriate account activation or sign-in instructions.
Instructions: Managing Users in WebReports.
8. Test the complete user path
Use a test account with the same roles as the intended user, or have the user complete the test with you. Follow Getting Started as a WebReports User and confirm that the account can:
- Sign in.
- Find the report under Reports → Available.
- Choose a permitted output and complete any required parameters.
- Open the expected results or retrieve generated output from Reports → Completed.
- Access only the reports and features intended for that account.
Do not rely on administrator visibility to confirm user access. Administrators can see all reports, while execution still depends on their assigned roles.
If the test fails, check the setup in this order:
- Confirm that the report was published to the correct WebReports site.
- Check its assignment, including the role, connection, and report type.
- Confirm that the user has the report-access role and the roles required for the selected action.
In WebReports 2026.10.12 and later, execution permissions are checked before parameter prompts appear. If prompts do not open, check access before changing the report’s parameters.
Initial setup is complete when the intended user can find and run the report and open its results. Share the user guide as their starting point.
Next steps
After the first report works, repeat the assignment and user-access steps for additional reports and users. Configure optional features as needed:
- Automatic report runs: Schedule Overview.
- Email delivery, branding, and application settings: Configuration.
- Storage and retention: Database & Storage.
- Investigating errors: WebReports Logs Overview.
Comments
0 comments
Please sign in to leave a comment.