---
title: "Space settings"
canonical: "https://support.appfire.com/space/RS/3393486849/Space%20settings"
format: markdown
---
> Macro (aura-html)

Use **Space settings** to configure how Appfire QueueZero works for a specific space.

Space settings include Jira mappings, repositories, documentation links, AI model overrides, space members, and space-level defaults.

> 📝 Spaces inherit [organization-level settings](https://appfire.atlassian.net/wiki/spaces/RS/pages/3293446474) unless a space override is configured.

## Who can manage space settings

| **Role** | **Space settings access** |
| --- | --- |
| **Owner** | Can manage organization-level settings and all space settings. |
| **Organization Admin** | Can create spaces and manage space configuration. |
| **Space Admin** | Can manage settings for spaces they have access to, including Jira mappings, repositories, knowledge, members, and space-level configuration.<br>Space Admins can map Jira spaces and add repositories directly from the spaces they administer. These actions do not require Organization Admin permissions. |
| **Space Member** | Can access the space and use QueueZero, but cannot manage space settings. |

## Open space settings

1. Open QueueZero standalone.
2. From the side menu, select **Spaces**.
3. Open the space you want to configure.
4. Click **Settings**.

![image-20260624-025038.png](media://cb91a74e-d854-4f1b-882a-a196d501d459)

Space settings are organized into several tabs. The General tab is documented below. See these pages for each tab

> Macro (children)

## General tab

Use the **General** tab to manage the space's main configuration.

### General settings

- **Name** - The space name shown in QueueZero. This is set when the space is created and cannot be changed.
- **Space key - **The short key used to identify the space. This is set when the space is created and cannot be changed.
- **Log level** - Use **Log level** to control the level of logs QueueZero records for the space. Available levels include statistics, info, debug, and trace.

### LLM provider for this space

Use **LLM provider for this space** to keep the organization default or select a space-specific provider.

> ℹ️ Whether a space can override the organization provider depends on the organization-level override settings.

### Code graph

Controls space-level code graph settings.

- **Dependency-only relevance **-** **When on, 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 on, execution can create hosted commits for each completed step.

### CI auto-fix

Use **CI auto-fix** to control whether QueueZero can attempt to fix CI/CD failures for resolutions in this space. This setting is enabled by default.

When disabled, no CI fix attempts run for this space.

> ℹ️ The organization also has an organization-wide CI auto-fix setting. If CI auto-fix is disabled at the organization level, it cannot run for individual spaces.

### Naming templates

Create templates for QueueZero to use when creating branch names, PR titles, commit messages, and PR descriptions. Spaces inherit naming templates from the organization by default. Editing an inherited template creates a space-level override, and **Reset to default** restores the organization template.

An inherited template appears in the field even when no space-level override is set, and the editor shows whether the current value is inherited or overridden.

### Jira context 

Use **Jira context fields** to control which Jira fields QueueZero reads in addition to the work item description. The configuration screen displays two primary sections - **Ticket context fields** and **Context sources**.

#### Ticket context fields 

Context fields for a space is set to **Detected automatically** unless you add additional fields. When you add additional fields to a Space, it will change to **Configured for this space**. To add additional fields, search for and select them from the **Search your Jira fields** option. 

The fields selected here are also shown on the work item **Details** tab, allowing users to see the same Jira context QueueZero receives. The configuration for added fields are: 

- Reorder the fields in terms of priority using the arrows to the left
- Remove them from context using the **Delete** button to the right
- Edit the display name in the standalone app by selecting the field name and entering a new value

> ℹ️ QueueZero limits the amount of content it reads from Jira context fields. If a field or the combined field content exceeds the supported limit, QueueZero trims the content before using it and indicates that trimming occurred.

Click **Save** to save your changes. After you create a space-specific configuration, use **Revert to organization default** to remove the override and return to the organization-level configuration.

#### Context sources

Context sources set which additional data QueueZero can access when scanning work items. It includes the following options:

> Macro (47fa61b6-fe1c-40c9-b236-623cdbc35833/4d8fa66b-88bf-4899-a37e-5926131c46ac/static/multiexcerpt-fast-include-inline-macro)



### Jira space mappings

Links Jira spaces to this QueueZero space.

### Danger Zone

Lets you delete the space. This process is irreversible.