---
title: "Manage organizations"
canonical: "https://support.appfire.com/space/RS/3293446474/Manage%20organizations"
format: markdown
---
> Macro (aura-html)

An Appfire QueueZero organization is the top-level container for your users, spaces, connections, and billing.

## Create your first organization

When you create a QueueZero account, you’re asked to create your first organization.

1. Create your QueueZero account.
2. Verify your email address.
3. Enter an organization name.
4. Create the organization.

The user who creates the organization becomes the organization owner.

## Create additional organizations

Use this when you need to manage separate teams, environments, or customer/demo organizations independently. If you belong to more than one organization, you can use the organization switcher to move between them.

1. Open the organization switcher in the upper-right corner.
2. Select **Create organization**.
3. Enter an organization name.
4. Select **Create organization**.

Once the organization has been created, you are taken to its dashboard. Continue configuring the organization as needed.

## Manage organization settings

When you are active in an organization, QueueZero shows the current organization context in the application.

The **Organization** page includes the following configuration options:

- **General**
  - **Organization name** - Your organization’s name. Update it, then click **Save** to change it.
  - **Organization ID** - *Read-only*. Your QueueZero organization ID.
- **Organization LLM provider** - The LLM provider for your organization; QueueZero currently supports:
  - QueueZero (platform-managed Anthropic key)
  - Anthropic (your Anthropic API key)
  - Vertex AI (your Google Cloud Vertex AI)
  - AWS Bedrock (keyless AWS IAM)
- **Space override controls** - Control whether individual spaces may diverge from organization defaults. Turning a control off locks all spaces to the organization default. Existing space override configurations are kept but ignored until you turn the option back on.
  - **Allow spaces to override the LLM provider** - Enable or disable Space administrators’ ability to configure LLM providers specifically for a space.
  - **Allow spaces to override model tiers** - Enable or disable Space administrators' ability to choose specific model tiers for the various QueueZero tasks.

> ℹ️ Locking the provider or model tiers makes any existing space-level override dormant. Affected spaces use the organization default until the setting is turned back on.

- **Guardrails - **Guardrails are rules applied to QueueZero-generated code. Depending on their configured posture, they can record a finding, flag a run, keep a pull request in draft for human review, or block a push and fail the run.
  QueueZero supports the following guardrail postures:
  - **Observe** - Records the finding.
  - **Warn** - Records the finding and flags the run.
  - **Hold** - Opens the pull request as a draft that must be marked ready by a person.
  - **Block** - Rejects the push before it reaches the repository and fails the run.  
QueueZero also includes locked guardrails that are created for every organization. These rules cannot be disabled, deleted, or edited, but their posture can be changed. See [Configure guardrails](https://appfire.atlassian.net/wiki/spaces/RS/pages/3641376799) for more information.
- **Default AI Models** - Select which models are used for each QueueZero activity. Available models may depend on your organization provider and configuration.   
QueueZero performs a separate code review before a resolution finishes. **Code Review** controls the model used to review generated changes, while **Code Review Fix** controls the model used to address issues identified during that review. For more information, see **[Execution and single-shot resolution](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166273540/Execution+and+single-shot+resolution?atl_f=PAGETREE)**.

|  |  |
| --- | --- |
| **Model slot** | **Used for** |
| **Planning** | Generates the implementation plan from the Jira work item. |
| **Execution** | Writes the implementation based on the approved plan. |
| **PR Description** | Drafts the pull request title and description. |
| **Code Review** | Reviews QueueZero-generated code. |
| **Code Review Fix** | Applies fixes when review flags work items. |
| **Web Research** | Pulls supporting external context when planning needs it. |
| **Summarization** | Summarizes Confluence and linked-page content during context build. |

- **Code Graph** - Configure how the code graph is used for repository detection and indexing.
  - **Smart repo selection** - When enabled, QueueZero uses repository, package, or file information in the work item to determine which repositories are relevant. If the work item does not provide enough information to make a confident selection, QueueZero asks the user to choose instead of guessing. When disabled, QueueZero uses the previous relevance-scoring method. This setting is enabled by default for new organizations.
  - **Dependency-only relevance **-** **When enabled, repository relevance uses only the `package.json` dependency graph.
  - **Code graph enrichment **-** **AI enrichment during indexing improves relevance but increases cost.
  - **Per-step commits **- When enabled, execution can create hosted commits for each completed step.
- **Refine PR** - Optional settings for the Refine PR workflow after a pull request is opened by QueueZero.
  - **Free-text refine guidance** - When enabled, users can add one optional sentence of guidance when refining a pull request. It cannot expand scope beyond selected items.
- **CI auto-fix – **Use **CI auto-fix** to control whether QueueZero can attempt to fix CI/CD failures across the organization. **Allow CI auto-fix** is enabled by default. Individual spaces can turn CI auto-fix off for that space. However, a space cannot enable CI auto-fix when it is disabled at the organization level.
  - When enabled, QueueZero can attempt to fix CI/CD failures in spaces where CI auto-fix is also enabled.
  - When disabled, QueueZero does not start new CI fix attempts anywhere in the organization. This also prevents users from starting manual **Resolve CI failure** requests.
- **Automated fix attempts before the pull request** - The number of attempts QueueZero makes to fix linting or testing errors before continuing. Each attempt consists of a fix followed by a full rerun of the configured commands. If errors cannot be resolved, QueueZero may still open a pull request depending on the **Pull requests when tests still fail** setting.
- **Time limit for a single command** - The number of minutes any one command can run. A command that reaches this limit is stopped without returning a result, and the run continues without that result.
- **Pull requests when tests still fail** - Configure what happens when automated testing still fails after the maximum number of fix attempts. QueueZero can either:
  - Open a draft pull request containing the failing output.
  - Keep the branch without creating a pull request.
- **Warm environment reuse** - Turn on the use of warm environments; subsequent runs on the same repository start with dependencies already installed. This setting applies at the organization level and cannot be overridden per space.
- **Naming templates** - Customize automatic branch names, pull request titles and descriptions, and commit messages generated by QueueZero.
  - **Available variables (read only)** - The first panel lists the variables available for use in naming templates. `{{issueUrl}}`, `{{branchName}}`, and `{{baseBranch}}` are available for PR titles, PR descriptions, and commit messages, but not for branch name templates.
  - **Templates** - Enter the template text QueueZero should use when creating repository entries. Use the variables listed under **Available variables** to control where text specific to each work item is inserted. Changes are saved automatically.   
Templates available include:
    - **Branch name**
    - **PR title**
    - **Commit message**
    - **PR description**

> 📝 Naming templates can be overridden in [space settings](https://appfire.atlassian.net/wiki/spaces/RS/pages/3393486849).

> ⚠️ The naming template variable `{{uniqueId}}` is used when QueueZero creates branch names. Because each run’s branch name must be unique, keep this variable in the branch name template unless you have a specific reason to remove it.
> ⚠️ 
> ⚠️ If it is removed and a resolution is rerun, QueueZero creates a new branch with a sequential number such as `-2` or `-3` appended to the branch name.
> ⚠️ 
> ⚠️ By default, QueueZero creates branches using the `queuezero/execute-plan-{TICKET-KEY}-{id}` pattern.
> ⚠️ 
> ⚠️ QueueZero also writes a `.queuezero/` folder to the repository and uses the following commit identity:
> ⚠️ 
> ⚠️ `QueueZero <queuezero[bot]@appfire.com>`

- **Jira context** - Use **Jira context** to control what QueueZero can use as Jira context. This includes linked issues, attachments, attachment filtering, and whether ZIP archives are unpacked and read. See [Configure Jira context](https://appfire.atlassian.net/wiki/spaces/RS/pages/3668312154) for more information.

> 📝 You add additional Jira fields to context within each space, not at the organizational level. See [Space settings](https://appfire.atlassian.net/wiki/spaces/RS/pages/3393486849/Space+settings#Jira-context) for more information.

- **Delete organization** - Permanently delete your organization and all data associated with it.

> ❌ Deleting an organization cannot be undone!