General Settings and Audit
Note
Starting in version 8.27, permissions have been enhanced with granular access control. Upgrade to version 8.27 or later to use this feature.
The General Settings & Audit page lets an Admin configure instance-wide preferences that control how QMetry behaves for every user.
From this page you set paging, login attempts, session timeout, password policy, two-step verification, embedded report URLs, API usage alerts, and analytics data sharing.
Note
The Super Admin can assign General Setting view and modify permissions from Roles under Customization.
Accessing General Settings & Audit
Note
Super Admins and users with General Settings and Audit View Permissions permissions can view this tab.
To access General Settings & Audit page, perform the following steps:
On the navigation pane, select System Settings.
Select General Settings & Audit.
The page opens on the General Settings tab. The AI Configurations, Audit, Configure Logo, and Transfer Super Administrator tabs appear alongside it.
General Settings
Note
Super Admins and users with General Settings and Audit Modify Permissions permissions can modify these general settings.
The following configuration options are available under the General Settings tab.
Paging
Set the maximum number of records that appear per page in the grid. The maximum value is 100 records per page.
Maximum Login Attempts
Set the maximum number of times a user can attempt to log in before QMetry locks the account.
This is applicable for QMetry authenticated users only.
Idle Session Timeout
Configure how long a user can remain inactive before being automatically logged out.
Idle Session Timout - Off (Default):
QMetry logs the user out only when
The browser closes, (after 15 minutes)
When the connection is lost,
When the user logs in on another browser or device.
Idle Session Timeput - On:
Configure how long a user can stay inactive before QMetry logs them out.
This setting applies to QMetry, LDAP, and SSO authenticated users.
Note
Logout activity is recorded in the Login Summary Dashboard.
Account Reactivation After Failed Login
When the maximum login attempt limit is reached, the user account is automatically locked.
Use Re-activate after setting to specify the duration (in minutes) the account remains locked before it is automatically reactivated.
If your account is locked, wait until the configured reactivation period has elapsed or contact your administrator for assistance.
Password Expiry
Password Expiry Period
Set the number of days after which passwords expire automatically.
Password Expiry Notification
You can also configure the Password Expiry Notification period to email users before their password expires.
Note
Only QMetry-authenticated users receive password expiry email notifications.
The notification period must be shorter than the password expiry period.
If you do not have the Customization app, the system defaults to five days before password expiry.
Edit Execution Time
Turn on Allow manual edit of last executed date/time to make the Executed At field editable on the Execution screen.
Users can then change the date and time for individual test cases or in bulk using Bulk Operations.
Approval and closure workflow
Configure the number of approval levels and users per level for reviewing requirements, approving test cases and test runs, and closing test runs. This setting is available only if the eSignature feature is enabled.
Setting | Description |
|---|---|
Maximum levels | The maximum number of approval levels. You can add up to five levels. Once levels are added, you cannot reduce the maximum below the number of levels already configured. |
Maximum users per level | The maximum number of approvers, reviewers, or closers per level. You can add up to 50 users per level. Once users are added, you cannot reduce the maximum below the number of users already assigned to a level. |
Approver/closer notification frequency | The number of days between reminder emails sent to approvers and closers for pending actions. |
Initially the Maximum Levels is set as 5. Admin has added 4 levels. Now, the Admin cannot make the Maximum Level 3.
Initially the Maximum Users per Level is set as 25. Admin has already added 20 approvers. Now, the Admin cannot make the Maximum Users per Level 15.
Two-step Verification
Make two-step verification mandatory for all users. Turn Mandatory Two-step Verification On to enforce it. This setting does not apply to LDAP or SAML authenticated users.
Generate Embedded URL for Sharing Reports Outside QMetry
Control whether users can generate embedded URLs that let non-QMetry users view reports within a dashboard.
An embedded URL grants unrestricted access to the associated dashboard. Turn Allow Users to Generate Embedded URL for Sharing Reports Outside QMetry On or Off.
When On, the default Super Admin User and Admin roles automatically have this permission. Other roles that have both the Report View and Edit permissions enabled can generate embedded URLs.
When Off, no user or role can generate embedded URLs. Any previously generated embedded URLs are deleted and become inaccessible.
Set API usage alerts
Configure email alerts that fire when hourly or daily API usage exceeds a set threshold. These alerts help you monitor and control usage of the Open API and Automation API.
Configuring email alerts for hourly and daily API usage enables effective monitoring and optimization of API usage.
Note
Total API Utilization Reports are available under Login Summary Dashboard
 |
The super admin and users with General Settings modify permissions can configure email alerts for the following scenarios:
Alert Type | Applies to |
|---|---|
Daily API usage alert | Open API and Automation API. |
Hourly API usage alert | Open API only |
Note
Total API utilisation reports are available in the Login Summary Dashboard. If the Integration app is not subscribed, Open APIs are not available.
To configure daily alerts
Turn on Send email alerts when the daily API counts for Open API or Automation API reach the threshold.
Set the threshold percentage. The threshold must be between 10% and 100%. The default is 90%.
Add the email addresses to receive daily alerts. You must add at least one address. You can add up to ten addresses.
To conflgure hourly alerts
Turn on Send email alerts when the hourly API counts for Open API reach the threshold.
Set the threshold percentage. The threshold must be between 10% and 100%. The default is 90%.
Add the email addresses to receive hourly alerts. You must add at least one address. You can add up to ten addresses.
Select Save.
Note
The super admin receives alerts by default. You can add up to ten additional email addresses per alert type.
Open APIs are available only if Integration app is subscribed.
Audit tab
Use the Audit tab to set how long QMetry retains audit and change logs, and to download logs for a specific date range.
Note
With Audit Compliance View right you can view the Audit Tab and download logs.
With Audit Compliance View and General & SMTP Settings Modify right, you can modify number of days and to enable or disable the toggle.
Only a Super Admin can change the retention period (the No of days field) and the Life Time Audit Retention toggle.
Users with Audit Compliance View permission can download logs by date but cannot change these values.
Retention Policy
The retention policy controls how many days QMetry keeps audit logs, change logs, test result logs, and eSignature logs. This is useful for organisations in regulated industries such as life sciences and pharmaceuticals that must retain records for compliance.
To set the retention period, perform these steps:
Go to System Settings and select Genetal Settings and Audit.
Select the Audit tab.
Under Retention Policy, enter the number of days.
Select Save.
Note
You can set a value between 30 and 1095 days. The default is 180 days.
If you increase the retention period, data from the date of change onwards is retained from the new period.
Data beyond the previous retention limit is not available and cannot be recovered.
Only the Super Admin can change the retention period. A user with Audit/Compliance View but without System Settings Modify can view the value but cannot save changes.
Download Logs
You can download audit logs, change logs, and test result logs as CSV files for any date range within the retention period.
The Audit/Compliance View permission is sufficient to download logs. You do not need View System Settings permission to download logs by date.
To download the logs, perform these steps:
On the Audit tab, select the date range using the calendar.
Select Change Log, Audit Log, or Test Result Log to start the download.
Select the notification icon on the header. A list of activities appears.
Select Scheduled Tasks. The screen shows all completed and queued activities.
Expand the audit log activity to check its progress. Select the Download icon to save the file.
Configure Logo
Add your organisation's logo to PDF and Word exports, system reports, custom dashboards, scheduled reports, and email notification templates.
Note
You need the Customization app to access this feature.
User needs, General & SMTP Settings Modify permission to access and modify Configure logo.
Email notifications always use the logo configured at the instance level, regardless of project-level settings.
Logos uploaded in the past are not preserved when you upload a new one.
Events of upload or change the logo on the Instance or Project level are captured in the Audit Logs
Required Permissions:
Instance Level Settings: You must have the System Settings Modify permission to configure instance-level settings. Only the Super Admin can modify System Settings.
Project-level settings: Admins must first enable project-level configuration at the instance level. After enabling, you must have the Project Modify permission to configure project-level settings.
Note
Project setting are given higher preference than instance preference.
Image Specifications:
The image should have the following characteristics:
JPG or PNG format
Horizontal proportions (Recommended 144 x 50 px)
White or transparent background
1 MB maximum size
Configure Logo at Instance level
To configure logo at instance level, perform these steps:
Under Customization, click General Settings and Audit.
Open the Configure Logo tab.
The QMetry logo is default logo.
Browse and upload your preferred logo to replace the default logo. The screen shows a preview of the logo.
Set the background color of the logo by clicking on the Set Background Color.
Allow Projects to set a different logo for PDF and Word exports: Enable the option to allow users to set the logo at Project level.
Reset to Default Logo: Click the button whenever you want to replace the uploaded logo with the default logo.
Click Save to save the settings.
Configure Logo at Project Level
If permitted by the system admin, project admin can override the default logo configured by the system administrator and add their project logo to the PDF and Word exports for the project i.e. test case export, test executions export, Exploratory Testing, System Reports, Custom Dashboards, and scheduled reports.
Note
Email notifications displays the logo configured at the instance level.
To configure logo, perform these steps:
 |
Under Project Management, click Projects.
Open the Configure Logo tab.
Browse and upload your preferred logo, if you want to replace the default logo with the desired one. The preview of logo is displayed on the screen.
Set the background color of the logo by clicking on the Set Background Color.
Reset to Default Logo: Click on the button whenever you want to replace the uploaded logo with the default logo.
Click Save to save the settings.
Setting API Usage Alerts
Users can set email alerts to notify admins when the hourly or daily API usage for the Open API and Automation API exceeds the threshold.
Use case:
Configuring email alerts for hourly and daily API usage enables effective monitoring and optimization of API usage.
Total API Utilization Reports are available under Login Summary Dashboard.
The super admin can configure email alerts for the following scenarios:
Daily API Usage alters can be configured for both Open API or Automation API.
Hourly API Usage alters can be configured for Open API.
Note
Users having General Settings and SMTP Settings View and Modify permission can modify these settings.
To configure email alerts for API usage:
Enable the Setting
Super admin must turn on this setting to trigger email alerts when daily or hourly API usage for the Open API or Automation API exceeds a specified threshold.
Specify the Threshold
Once enabled by the super admin, specifying a threshold is mandatory.
The threshold can be set between 10% and 100%, with a default value of 90% for both daily and hourly API usage.
Add Email Recipients
At least one email address is required to send alerts. By default, the QMetry Super Admin receives these alerts.
The super admin can add up to 10 additional email addresses to receive API usage alerts.
If the “integration” app is not subscribed, then Open API’s are not available.
Transferring Super Administrator Role
Super admins can transfer their access to another user directly from General Settings, eliminating the need to contact QMetry Support. This facilitates smoother transitions during organizational changes.
Note
Users with Administrative Control Modiy permission can transfer ownership and restore the delete user.
Self-Transfer
A Super Admin can transfer their rights to another user using the Transfer Super Administrator tab under System Settings.
For self-transferring the super admin role, perform the following steps:
Go to System Settings and select General Settings & Audit.
Select Transfer Super Administrator tab.
Select the new super admin from the Select User list.
Only eligible users (active and QMetry-authenticated users) are listed.
Read-only license users will not appear in the list.
Click Yes to confirm the transfer.
Note
The new super admin is granted admin rights across all projects, including archived and active ones.
They receive default access to all custom dashboards and gadgets within the instance.
They have full permissions to manage organization settings, users, projects, and system configurations.
The current Super Admin’s privileges are revoked and replaced with project-level admin access for all existing projects.
Once the transfer is complete, email notifications are sent to both the new and previous super admins.