# Admin Options # Admin Options in AIQ **Last reviewed:** September 22, 2026 Admin Options contains administrative controls for users, environment configuration, and operational settings. Changes here can affect many AIQ users. ## Recommended guidance - Limit access to administrators who understand the environment impact. - Document changes that affect users, integrations, or execution behavior. - Use change windows for high-impact settings. ## Validation workflow 1. Identify the setting and the reason for the change. 2. Check current value and capture a rollback plan. 3. Update the setting in Admin Options or the supported configuration path. 4. Validate sign-in, permissions, integrations, or execution behavior as applicable. 5. Record the change in the operations log. **Note:** Do not use Admin Options to work around access-control process requirements. --- Last updated: September 22, 2026 If you have feedback on this topic, contact . # Configure Results Options in AIQ **Last reviewed:** September 24, 2026 Results options control how execution data is retained, displayed, and used for analysis after AIQ runs complete. ## Recommended guidance - Confirm retention settings match customer, compliance, and storage requirements. - Use consistent filters and naming so teams can compare runs over time. - Review results settings after upgrades or major reporting changes. ## Validation workflow 1. Review current results and retention options in Global Options. 2. Confirm the settings with the teams that consume AIQ reports. 3. Run or review a recent execution to validate that results display as expected. --- Last updated: September 24, 2026 If you have feedback on this topic, contact . # Configure Network Emulation in AIQ **Last reviewed:** September 22, 2026 Network emulation helps evaluate application behavior under constrained latency, bandwidth, or packet-loss conditions. ## Recommended guidance - Use network emulation only when the test objective requires it. - Document the network profile used for each run. - Do not compare emulated and non-emulated results without noting the difference. ## Validation workflow 1. Define the target network profile and expected constraints. 2. Apply the profile in the supported AIQ or test-node configuration. 3. Run a small validation to confirm latency/bandwidth behavior. 4. Execute the scenario and label results with the network profile. 5. Disable or reset emulation after the test if it was temporary. **Note:** Leaving network emulation enabled accidentally can invalidate later test results. --- Last updated: September 22, 2026 If you have feedback on this topic, contact . # Configure AIQ Notifications **Last reviewed:** September 24, 2026 AIQ notifications should route execution and platform events to the right owners without creating unnecessary alert noise. ## Recommended guidance - Define which events should notify users, teams, or distribution lists. - Use shared team recipients where possible so ownership survives personnel changes. - Review notification rules after major workflow or environment changes. ## Validation workflow 1. Identify the event types that require action. 2. Configure recipients and message behavior in Global Options. 3. Trigger a test event and confirm the expected recipients receive it. --- Last updated: September 24, 2026 If you have feedback on this topic, contact . # Legacy LoadRunner Administration Settings **Last reviewed:** September 29, 2026 Use this page only when maintaining AIQ administration settings for environments that still execute LoadRunner assets. ## What changed in this article - Marked LoadRunner Admin as legacy administration content. - Added checks for installation path, license availability, execution node access, environment variables, result storage, and permissions. - Connected admin setup to the LoadRunner execution article so configuration is validated with a real test run. ## Validation workflow 1. Confirm the LoadRunner installation and license details with the tool owner. 2. Configure AIQ paths, node access, and environment settings needed for execution. 3. Run a controlled LoadRunner script and verify AIQ can collect the expected results. **Review note:** This page now keeps admin settings separate from script creation and execution guidance. --- Last updated: September 29, 2026 If you have feedback on this topic, contact . # Administer Jira Integration in AIQ **Last reviewed:** September 24, 2026 Use Jira Integration Administration to connect AIQ defects or execution findings to the correct Jira project workflow. ## Recommended guidance - Use Jira Cloud tokens or approved service credentials instead of personal passwords. - Map required Jira fields before enabling issue creation from AIQ. - Test with a non-production issue first to confirm project, issue type, and field mappings. ## Validation workflow 1. Confirm the Jira URL, authentication method, project key, and issue type. 2. Map required fields and defaults in the AIQ integration settings. 3. Create a test issue from AIQ and verify it appears correctly in Jira. **Note:** Keep integration credentials restricted to the minimum permissions needed for issue creation and updates. --- Last updated: September 24, 2026 If you have feedback on this topic, contact . # Manage the AIQ License **Last reviewed:** September 22, 2026 Use this page when reviewing, applying, or troubleshooting the AIQ license for an environment. ## Recommended guidance - Track license expiration, licensed capacity, and environment ownership. - Coordinate renewals before expiration to avoid execution disruption. - Share license files or keys only through approved channels. ## Validation workflow 1. Open the License area in Global Options or the supported admin location. 2. Review expiration, capacity, and status messages. 3. Apply a new license only from an approved source. 4. Validate sign-in and test execution after license changes. 5. Document renewal date and owner. **Note:** Do not paste license keys into public tickets, screenshots, or documentation. --- Last updated: September 22, 2026 If you have feedback on this topic, contact . # Manage Certificates for AIQ Integrations **Last reviewed:** September 22, 2026 Use this page when AIQ integrations or monitored systems require certificates for TLS trust, mutual authentication, or secure connections. ## Recommended guidance - Track certificate owner, expiration date, environment, and usage. - Protect private keys and avoid posting them in documentation or tickets. - Coordinate certificate changes with service restarts and validation windows. ## Validation workflow 1. Identify whether AIQ needs a server certificate, trusted CA, or client certificate. 2. Obtain the certificate and key material through the approved security process. 3. Install or configure the certificate in the supported AIQ/global option location. 4. Restart or reload affected services if required. 5. Validate the connection and document expiration/renewal ownership. **Note:** Certificate changes can break integrations if trust chains or private keys are mishandled. --- Last updated: September 22, 2026 If you have feedback on this topic, contact . # Restart AIQ Services Safely **Last reviewed:** September 22, 2026 Use this page when AIQ services must be restarted for maintenance, configuration changes, or troubleshooting. ## Recommended guidance - Confirm the maintenance window and user impact before restarting services. - Collect relevant logs and symptoms before a restart masks the original issue. - Restart only the affected services when possible. ## Validation workflow 1. Notify stakeholders and confirm no critical executions are running. 2. Record the current service status and collect logs for the issue. 3. Stop and start services using the supported service manager for the installation. 4. Verify service health, sign-in, test node connectivity, and a smoke execution. 5. Document the reason, time, and validation result. **Note:** Avoid using service restarts as a substitute for root-cause analysis on recurring issues. --- Last updated: September 22, 2026 If you have feedback on this topic, contact . # Review Activity Logs in AIQ **Last reviewed:** September 22, 2026 Activity Logs help administrators review important AIQ actions, changes, and troubleshooting evidence. ## Recommended guidance - Use activity logs to support audits, incident reviews, and configuration troubleshooting. - Correlate activity logs with execution logs, system logs, and change records. - Restrict access according to audit and privacy policy. ## Validation workflow 1. Open the Activity Logs area in the supported admin location. 2. Filter by date, user, project, or action when available. 3. Review entries around the time of the issue or change. 4. Export or capture evidence according to support and audit rules. 5. Record findings without exposing sensitive values. **Note:** Activity logs may contain operationally sensitive information. Share them only with authorized recipients. --- Last updated: September 22, 2026 If you have feedback on this topic, contact . # Configure SAML Options in AIQ **Last reviewed:** September 24, 2026 SAML options connect AIQ authentication to an identity provider for single sign-on. ## Recommended guidance - Coordinate changes with the identity-provider owner before updating SAML metadata. - Keep a verified administrator fallback path before enabling or changing SSO. - Track certificate expiration dates and renew them before users are impacted. ## Validation workflow 1. Collect IdP metadata, entity ID, ACS URL, and certificate details. 2. Enter or update the SAML settings in AIQ. 3. Test login with a limited user group before broad rollout. **Note:** Changing SAML can affect user access. Confirm a fallback admin account before saving production SSO changes. --- Last updated: September 24, 2026 If you have feedback on this topic, contact .