---
title: "Key concepts"
canonical: "https://support.appfire.com/space/RS/3159753056/Key%20concepts"
format: markdown
---
> Macro (aura-html)

Use this page to understand the main terms used in QueueZero.

## About Appfire QueueZero standalone app

The QueueZero standalone app is where admins set up and manage QueueZero.

Use it to manage organizations, connections, spaces, users, AI settings, usage, and billing.

For more information, see **[QueueZero app overview](https://appfire.atlassian.net/wiki/spaces/RS/pages/3351675003)**.

## Appfire QueueZero Connector for Jira

The **QueueZero** panel in Jira lets users run QueueZero from Jira work items.

Use it to generate plans, execute work, track progress, and review pull requests from the Jira work item workflow.

For more information, see **[Resolve a work item](https://appfire.atlassian.net/wiki/spaces/RS/pages/3159621711)**.

## Organization

An organization is the top-level workspace in QueueZero. It contains users, spaces, connections, billing, and shared settings.

For more information, see **[Manage organizations](https://appfire.atlassian.net/wiki/spaces/RS/pages/3293446474)**.

## Connections

Connections let QueueZero access external tools, such as Atlassian, GitHub, and Bitbucket. QueueZero uses these connections to access Jira work items, Confluence documentation, repositories, and pull request workflows.

For more information, see **[Configure connections](https://appfire.atlassian.net/wiki/spaces/RS/pages/3159457879)**.

## QueueZero space

A QueueZero space groups related Jira work items, repositories, documentation links, settings, and members.

Create a QueueZero space for a team, product area, application, or group of related repositories.

## Jira space mapping

A Jira space mapping connects a Jira space to a QueueZero space.

After a Jira space is mapped, its work items can appear in the QueueZero space and users can run QueueZero from those Jira work items.

For more information, see **[Space administration](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932)**.

## Knowledge

QueueZero uses connected code, documentation, and generated repository context to understand a codebase during planning and execution.

Space knowledge can include repositories, documentation links, and code graphs.

For more information, see **[Set up space knowledge](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932)**.

## Repository

A repository is a code source connected to a QueueZero space.

QueueZero uses repository content and configured repository context to understand the codebase, generate implementation plans, execute changes, and create pull requests.

## Code graph

A code graph represents the structure and relationships within a repository so QueueZero can better understand the codebase.

## Plan

A plan is QueueZero’s proposed implementation approach for a work item. It can include a summary, expected file changes, implementation steps, testing steps, risks, and follow-up notes.

For more information, see **[Review the plan](https://appfire.atlassian.net/wiki/spaces/RS/pages/3158213589)**.

## Execution

Execution is the stage where QueueZero carries out an implementation plan and makes the proposed code changes.

During execution, QueueZero shows progress and records activity for the work item.

## Single-shot resolution

Single-shot resolution lets QueueZero generate a plan, execute it, and create a pull request in one flow.

Use it when the work item is clear enough to proceed without pausing for a separate plan review.

For more information, see **[Execution and single-shot resolution](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166273540)**.

## Pull request

After execution, QueueZero can create a pull request in the connected code provider.

Review the pull request using your team’s normal code review process.

## Refinement

Refinement lets you give QueueZero additional instructions or context to improve a work item, implementation plan, or pull request.

Depending on where refinement is used, QueueZero can update the work item, generate a revised plan, or create additional code changes.

## Guardrails

Guardrails are rules that QueueZero applies to generated changes during execution. 

Depending on their configured posture, guardrails can record a finding, flag a run, require human review before a pull request is ready, or block a push.

## Env Grounding

Env Grounding lets QueueZero prepare and use an environment for validating generated changes before a pull request is created.

## Plan version

A plan version is a saved iteration of an implementation plan.

When a plan is refined or regenerated, QueueZero can create a new version while keeping earlier versions available for comparison or reference.

## Space members

Space members are users who have access to a specific QueueZero space.

Users must belong to the organization before they can be added to a space.

For more information, see **[Space settings](https://appfire.atlassian.net/wiki/spaces/RS/pages/3393486849)** and **[Roles and permissions](https://appfire.atlassian.net/wiki/spaces/RS/pages/3293446483)**.