Current Product Notes

​

What this does

This page summarizes current product behavior that administrators and users commonly ask about.

​

Identity and free trials

• ScrambleID is the identity provider for LoopIQ web, Analytics, AI services, MCP OAuth, and Helix Mobile.
• LoopIQ resolves organization membership, roles, and permissions after ScrambleID authentication; identity claims do not replace organization authorization.
• A free-trial applicant first verifies the LoopIQ email address. LoopIQ then provisions the user through the ScrambleID SCIM flow and ScrambleID sends device-activation instructions.
• Existing loopiq.com and fusiononeplatform.com aliases can resolve to the same LoopIQ user where the organization has configured that alias policy.
• MCP supports interactive OAuth and organization-governed, short-lived, resource-bound bot access. Bot access remains subject to creator permissions, scopes, bot status, credential version, and audit controls.

​

Billing and trials

• Free trial organizations should show trial status separately from paid plan status.
• No paid plan should be pre-selected for a free trial organization.
• Free trial access should allow the product features needed to evaluate LoopIQ, including AI-enabled workflows where available.
• Freemium is the ongoing free tier, distinct from a temporary free trial.
• Checkout must match the selected organization, plan, seats and agreed price. Do not substitute a legacy tier if the new price is unavailable.

​

Updated pricing policy

Analytics is an optional $4.99 USD per Analytics user/month add-on to Paid, using the same organization credit wallet. It is not included in the Core seat fee. Credit packs are one-time purchases: 5,000/$50, 20,000/$200, 50,000/$500 and 100,000/$1,000 USD. Usage credits never expire. They are not a third tier. The 71-operation rate card includes 25 credits per generated certification version, Analytics AI operations and approved custom-resource rates: metrics 50 creation + 50 monthly; dashboards 200 creation + 20 monthly.

​

User and access management

• Users shown in Organization Settings should be scoped to the active organization.
• The Grant/Revoke Access view should only show users for the active organization.
• New user creation should require at least one role and at least one user permission.
• A user with no permissions should see a no-access page and should not see organization data.

​

Change request list visibility

A change request should appear in the list view when the current user is one of the following:

• Requestor
• Coordinator
• Approver
• Assignee
• Creator
• Member of the team assigned to the change

​

Notifications and expired sessions

If a user’s token expires while they are working, background notification polling should not create repeated error toasts. The user may need to sign in again before protected data can refresh.

​

MCP organization mode

LoopIQ MCP operates in dynamic organization mode. The organization context is determined from the authenticated user or bot and selected organization, not from a fixed deployment value. If a user belongs to more than one organization, the client or workflow should be explicit about the intended organization before actions are taken.

​

AI terminology

Current AI-facing terminology should use:

• Performance Intelligence
• Release Compliance Dossier
• AI Assistance
• MCP tools

Avoid older names if your screen or documentation has been updated to the current product language.

​

Test-management highlights

Current Test Management behavior includes:

• append-only manual-test revisions, comparison, and restore-as-new-version
• reusable manual steps with impact analysis
• repository folders, tags, saved views, bulk update, clone, archive, and restore
• named baselines and frozen release snapshots containing full manual-test contents
• tester queues, assignment, workload, schedules, estimates, time logging, and overdue indicators
• execution-level and test-run-level defects synchronized with LoopIQ issues
• Playwright, Vibium, WebDriver BiDi, Selenium, Karate, pytest-bdd, and Behave automation
• GitHub migration with dependency discovery, rescan identity, mapping review, and audit history
• versioned CSV datasets with whole-test or selected-step row iteration
• suites, schedules, provider and tunnel selection, normalized evidence, and automation intelligence

​

Integration highlights

• Atlassian synchronization supports Jira, Jira Service Management, Confluence, Compass, Bitbucket, and Assets through a provider-neutral external-resource model.
• Administrators can review connections, product configuration, containers, external accounts, identity links, mapping profiles, traceability proposals, conflicts, outbound delivery, comments, and audit history.
• OpenText Fortify, ArcSight, BrightCloud, Security Operations, Voltage, and OSM data can contribute approved security, privacy, threat, and observability evidence to release governance and analytics.
• Native LoopIQ project management and ITSM remain available when an organization uses connected or hybrid external work modes.

​

Analytics Platform highlights

Current Analytics Platform behavior includes:

• default dashboards for overview, productivity, sprint risk, team risk, release burndown, and object relationships
• built-in query editing for most default dashboards except Object Relationship
• Metric Library with seeded SDLC and compliance-oriented metrics
• Custom Charts with:
  • single-metric and multi-metric chart creation
  • plain-English SQL generation
  • approved schema guidance while writing SQL
• custom dashboards with widget editing and sharing to users or teams within the same organization
• Prediction Center for delivery and compliance risk forecasts
• Operating Reviews with review packs, review artifacts, and executive brief export
• Test Automation Analytics with configurable dashboards and a governed report catalog
• External-resource analytics with connection, freshness, mapping, event-pipeline, and OpenText evidence views