Documentation Index
Fetch the complete documentation index at: https://help.loopiq.com/llms.txt
Use this file to discover all available pages before exploring further.
Core Concepts and Glossary
Organization
An organization is the top-level tenant boundary in LoopIQ. Users, teams, settings, workflows, roles, subscriptions, integrations, AI access, MCP access, and most governed records belong to an organization.
If you belong to more than one organization, always confirm which organization is active before reviewing or creating records.
Team
A team is a working group inside an organization. Many operational records are team-specific. If records appear missing, check the active team context first.
User roles and permissions
Roles define what a user can see and do. Permissions control actions such as view, create, edit, delete, approve, import, export, automate, or administer.
A user may have organization-level access, team-level access, direct user permissions, or a combination of these.
New users should be created with at least one role and at least one user permission so they do not land in an unusable state.
Free trial
A free trial gives an organization temporary access to LoopIQ before a paid subscription is selected. Free trial users should not have a paid plan pre-selected, and trial access should allow the product features needed to evaluate LoopIQ, including AI-enabled workflows where available.
Work item
A work item is a record used to plan or execute work. Examples include ideas, stories, tasks, issues, incidents, service requests, change requests, enhancement requests, test records, exceptions, deviations, objectives, approvals, and release certifications.
Workflow and status
A workflow defines the lifecycle of a record. Statuses show where the record is in that lifecycle, such as Backlog, To Do, In Progress, In Review, Approved, Resolved, or Closed.
List views should show human-readable status, priority, category, and severity labels rather than raw internal numeric IDs.
Approval
An approval is a decision point. Approvals may be assigned to named users, roles, managers, requestors, coordinators, service owners, compliance owners, or other configured approver types.
Some records, such as change requests, can have multiple approvers.
Evidence
Evidence is supporting information that helps prove what happened, who approved it, what was tested, what changed, and why a decision was made.
Evidence can include documents, comments, approvals, test results, linked work, integration data, release records, and compliance artifacts.
Release certification
A release certification is a governance record used to assess and approve release readiness. It may include related work items, approvals, test context, risk context, exceptions, deviations, and supporting evidence.
Release Compliance Dossier
A Release Compliance Dossier is an auditable package of release evidence. It connects the release, change context, approvals, test results, risks, exceptions, deviations, deployment context, and supporting records.
Performance Intelligence is LoopIQ’s AI-assisted analysis layer for surfacing delivery, operational, quality, and compliance signals that help leaders understand where execution risk or process drag is emerging.
Automation rule
An automation rule is a configured trigger and action. Rules can help route work, set values, create records, request approvals, enforce process steps, and reduce manual follow-up.
Automation actions can include common fields and module-specific fields, such as service request priority or default requestor where supported.
Integration
An integration connects LoopIQ to an external system such as source control, document storage, security scanning, cloud infrastructure, observability, identity, or GRC-adjacent workflows.
Examples include GitHub, SonarQube, Checkmarx, Google Workspace, SharePoint, OneDrive, Google Cloud, Datadog, and CI/CD systems.
AI agent
An AI agent assists with a specific workflow such as idea analysis, acceptance criteria, work breakdown, estimation, risk review, testing, Performance Intelligence, Release Compliance Dossier preparation, or operational intelligence.
AI output should be reviewed before it is used for production, compliance, or customer-facing decisions.
MCP
MCP stands for Model Context Protocol. LoopIQ MCP tools expose governed LoopIQ actions and context to compatible AI clients. MCP access should be configured carefully and used with the same organization, tenant, and permission boundaries as the main application.