WebReports includes built-in roles that control the features and actions available to users. Administrators can also create additional roles to organize users and assign report access.
Screenshots use fictional demo data consistent with the other WebReports articles.
Default roles
WebReports includes the following default roles:
- Admin
- API
- Bridgit Analysis
- Publisher
- Queue
- RoleAdmin
- Scheduler
- User
Role access and API credentials: The API role is for WebReports application integrations. The Bridgit Analysis role controls access to Bridgit AI in Finished Reports and Visualize; Admin users have this access as well. The WebReports API and the OpenAI API used by Bridgit are separate services.
The role directory includes default roles and the custom Demo Sales, Demo Finance, and Demo Operations roles. Demo Sales is selected with 3 users and 2 assignments.
Important information about roles
- A user can be assigned multiple roles.
- When a user has multiple roles, the user receives the combined permissions and report access provided by those roles.
- Report access depends on the reports assigned to each role.
- Additional roles can be created to provide users with access to specific reports.
- The Admin role provides the highest level of access in WebReports.
- A user with the Scheduler role can schedule only reports available through the user’s assigned roles.
- Queue for Role requires both the Queue and RoleAdmin roles.
For example, a user assigned both the User and Scheduler roles receives the permissions and report access provided by both roles.
Demo Administrator (demo.admin@example.com) has Admin, Publisher, Queue, RoleAdmin, Scheduler, and User assigned. This illustrates a user with multiple roles.
Report permissions in WebReports 2026.10.12 and later: Administrators can see all reports for management purposes, while report execution remains controlled by their assigned roles. WebReports checks execution permissions before displaying parameter prompts. A user without permission will not be able to execute the report.
DemoSalesSummary.vdm has separate assignments for Admin and Demo Sales. Both use DemoSQL, Detail Grid, and a 3-day expiration.
Admin
The Admin role provides the highest level of access in WebReports.
Users assigned this role can:
- Add, edit, and remove users.
- Assign, manage, and delete reports.
- Use execution, download, queue, download for a role, and queue for a role actions, with report execution controlled by the user’s assigned roles.
- View parameters for completed reports.
- View and download completed reports, and re-execute them when report execution is permitted by the user’s assigned roles.
- Use the Scheduler.
- Create and manage connection profiles.
- Configure the email profile.
- Access registration settings.
- View WebReports, execution, and other available logs.
- Use Bridgit AI in Finished Reports and Visualize when the feature is configured.
API
The API role supports authorized applications that connect to WebReports through the WebReports API.
For example, authenticated informational API calls can retrieve users, roles, connection profiles, UDFs, and report assignments. Each API operation has its own authentication and permission requirements; review the relevant endpoint documentation before configuring an integration.
The WebReports API is separate from the OpenAI API used by Bridgit AI. Assigning the API role does not provide an OpenAI API key or grant Bridgit AI access in Finished Reports and Visualize.
For integration guidance, see WebReports API Calls and Managing API Keys in WebReports.
Bridgit Analysis
The Bridgit Analysis role controls access to Bridgit AI in Finished Reports and Visualize. Users with the Admin role also have this access.
Open an available Finished Report or visualization and select Ask Bridgit or its chat icon to ask questions about the displayed results. Users without either role do not have access to the viewer chat.
Your organization must also configure Bridgit AI with a valid OpenAI API key. This key is separate from WebReports API keys. Bridgit Analysis does not by itself grant access to additional reports; review the user's report assignments and execution permissions as well.
For viewer instructions, see Viewing Report Results in WebReports. For configuration, see Configuring Application Settings in WebReports.
Publisher
The Publisher role allows users to connect through VDM and publish reports to WebReports.
Users assigned this role can:
- Execute and download available reports assigned to the Publisher role.
- View parameters for completed reports.
- View and download completed reports.
Queue
The Queue role allows users to queue reports.
Users assigned this role can:
- Execute, download, and queue available reports.
- View parameters for completed reports assigned to the Queue role.
- View, download, and rerun completed reports assigned to the Queue role.
RoleAdmin
The RoleAdmin role allows users to download and queue reports for roles.
Users assigned this role can:
- Execute and download reports assigned to the RoleAdmin role.
- Download reports for a role.
- Queue reports for a role when the user also has the Queue role.
- View parameters for completed reports.
- Download completed reports.
Scheduler
The Scheduler role allows users to automate report execution through the Scheduler.
Users assigned this role can:
- Execute and download reports assigned to the Scheduler role.
- View parameters for completed reports assigned to the Scheduler role.
- View and download completed reports assigned to the Scheduler role.
- Create scheduled jobs for reports available through their assigned roles.
User
The User role provides basic access to assigned reports.
Users assigned this role can:
- Execute and download reports assigned to the User role.
- View parameters for completed reports assigned to the User role.
- View and download completed reports assigned to the User role.
Comments
0 comments
Please sign in to leave a comment.