---
title: "Get started as a space admin"
canonical: "https://support.appfire.com/space/RS/3391127587/Get%20started%20as%20a%20space%20admin"
format: markdown
---
> Macro (aura-html)

Use this guide to prepare a Appfire QueueZero space for your team.

As a Space admin, you manage the space-level context and configuration QueueZero uses when users generate plans and resolve work items. This includes members, repositories, documentation, indexing, guardrails, and other space settings.

A QueueZero space brings together the Jira work, repositories, documentation, settings, and users QueueZero needs to understand and resolve work. 

For more information about space configuration, see [Set up spaces](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932) and [Space settings](https://appfire.atlassian.net/wiki/spaces/RS/pages/3393486849). 

## Before you begin

Make sure:

- QueueZero is set up for your organization.
- The required tools are connected. At minimum, Atlassian must be connected. If your team wants QueueZero to work with code, GitHub and/or Bitbucket must also be connected. For more information, see [Configure connections](https://appfire.atlassian.net/wiki/spaces/RS/pages/3159457879/Configure+connections?atl_f=PAGETREE).
- A QueueZero space has been created for your team.
- You know which Jira space your team works from. If it is not mapped yet, you can map it to the QueueZero space during setup.
- You have `space-admin` access to the QueueZero space.
- You know which repositories QueueZero should use.

The users who need access have already joined the QueueZero organization. If they have not joined yet, ask an organization admin to invite them. For more information, see [Invite users](https://appfire.atlassian.net/wiki/spaces/RS/pages/3293118641/Invite+users?atl_f=PAGETREE) and [Roles and permissions](https://appfire.atlassian.net/wiki/spaces/RS/pages/3293446483).

## Step 1: Create a QueueZero space

Create a QueueZero Space from the Jira work your team wants to use with QueueZero.

![Start by creating a space in QueueZero](media://4335692f-c592-47c7-bdc7-cd6a5bef0cb9)

1. From the side menu, select **Spaces**.
2. Click **New space**.
3. Search for the Jira area you want to connect by name or key.
4. Select it from the list.  
:note: A QueueZero space inherits its space names and space keys from the Jira space to which it is linked.
5. Continue with the space setup.

For more information, see **[Create a QueueZero space](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932/Set+up+spaces#Step-1%3A-Create-a-QueueZero-space)**.

## Step 2: Review space settings

Open the space settings and review the configuration QueueZero will use for this space.

Some settings inherit organization-level defaults and can be overridden when the space needs a different configuration.

For example, a space may need different AI model settings, different attachment handling, or a space-specific code graph configuration. If you are not sure which settings to use, keep the inherited defaults and confirm with your organization admin.

For more information, see [Space settings](https://appfire.atlassian.net/wiki/spaces/RS/pages/3393486849/Space+settings?atl_f=PAGETREE).

## Step 3: Add space members

In space settings, click the **Members** tab to add the people who need access to this QueueZero space, and use space roles to control what users can do inside the space:

| **Space role** | **Use this role for** |
| --- | --- |
| Space admin | Users who configure space settings, manage space knowledge, and maintain space access. |
| Space member | Users who need to view the space and use QueueZero for work items in this space. |

## Step 4: Add repositories and documentation

As a space admin, you can add and manage repositories for the space from the **Knowledge** tab. Add the repositories QueueZero should use when generating plans and creating pull requests.

Repositories help QueueZero understand the codebase, identify relevant files, plan implementation steps, and prepare code changes. Add all repositories that may be relevant to the work items your team wants QueueZero to handle. For example, if one Jira work item may require changes across multiple services, add each related repository to the space.

1. Open the QueueZero space.
2. Open the space settings.
3. Go to **Knowledge**.
4. Select **Add repository**.
5. Choose GitHub or Bitbucket.
6. Select a repository.
7. Optionally, add a Confluence documentation URL.  
Add documentation sources when QueueZero needs business rules, team processes, architecture notes, or product behavior that is not clear from the code alone.
8. Select **Add repository**.

For more information, see **[Set up spaces](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932/Set+up+spaces#Step-2%3A-Set-up-space-knowledge)**.

> ℹ️ If you want QueueZero to verify generated changes against a repository’s install, lint, and test commands, configure Env Grounding for that repository. See **[Set up Env Grounding](https://appfire.atlassian.net/wiki/spaces/RS/pages/3624304708)**.

## Step 5: Prepare repository context

After adding repositories and documentation, make sure the context QueueZero needs is ready to use.

Depending on the configured source, QueueZero may need to index repository or documentation content, build or update a Code Graph, or prepare other repository context.

Check the status of the configured knowledge sources before running your first resolution.

If preparation fails, review the error and confirm that:

- The connection is still available.
- QueueZero has permission to access the source.
- The repository or documentation location is valid.

After fixing the problem, retry the preparation process.

> Macro (excerpt)
> 
> //removing from view until memory bank is released.   
> Step 6: Create or update the memory bank
> 
> Create or update the memory bank when QueueZero needs reusable space knowledge during plan generation.
> 
> The memory bank helps QueueZero retain space-level knowledge that can improve future plans. Update it when major space context changes, such as architecture updates, new coding patterns, important process changes, or newly added documentation sources.
> 
> For more information, see [Set up spaces](https://appfire.atlassian.net/wiki/spaces/RS/pages/3166076932/Set+up+spaces#2.-Generate-the-memory-bank).

## Step 6: Review space work items

After the space and its context are configured, review the Jira work available to the team.

Open the QueueZero space and confirm that the expected work items are available.

From the work item view, users can search and filter work, open individual work items, and start QueueZero when they are ready to generate a plan or resolve the work.

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

## Step 7: Run a test resolution

Before the team starts using the space regularly, test the setup with a small, well-defined work item.

For the first test, check whether QueueZero:

- Uses the expected repository context.
- Uses the expected documentation.
- Identifies the relevant parts of the codebase.
- Generates a useful implementation plan.
- Surfaces missing context or configuration.

You do not need to merge the resulting pull request during this test. If you want to review the implementation plan before QueueZero continues with execution, turn off the *Single-shot resolution* feature.

For more information, see [Generate the implementation plan](https://appfire.atlassian.net/wiki/spaces/RS/pages/3158507969), [Review and refine](https://appfire.atlassian.net/wiki/spaces/RS/pages/3158213589), and [Using QueueZero in Jira](https://appfire.atlassian.net/wiki/spaces/RS/pages/3159621711).

## Step 8: Keep space context up to date

QueueZero's output depends on the context available to the space, so review it as your team's codebase and processes change.

Update space knowledge when:

- A new repository becomes relevant.
- Architecture or product documentation changes.
- A new documentation source should be available to QueueZero.
- Development or review conventions change.
- Generated plans repeatedly miss important technical or business context.

After updating a repository or documentation source, make sure QueueZero has processed the new context before relying on it in future resolutions.

## Next step

To learn how users run QueueZero on their work items, go to **[Get started as a developer](https://appfire.atlassian.net/wiki/spaces/RS/pages/3330638261)**.