> For the complete documentation index, see [llms.txt](https://help.genesis.autify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.genesis.autify.com/spaces/manage-spaces.md).

# Manage Spaces and collections

Create and organize Spaces and Collections to hold your structured QA data.

{% hint style="info" %}
This feature is being gradually rolled out to customers.
{% endhint %}

## Create a Space

1. In the sidebar, open the **Spaces** tab.
2. Select **Create Space**.
3. Choose **With AI**, a starter template, or **Blank**.
4. If you chose **With AI**, describe what you want to track. Review and edit the drafted Space name and collections as needed.
5. If you chose a template or **Blank**, enter a name for the Space.
6. Select **Create Space**.

Nothing is created from the AI flow until you confirm. After creation, the Space opens immediately. AI-created Spaces use the collections you reviewed, template-based Spaces start from the chosen template, and Blank Spaces start with a Title field only. From the Space overview, you can also click **Open collection** on each collection to move straight into its full-page view.

## Rename a Space

1. Open the Space you want to rename.
2. Select the Space name menu (⋯) at the top of the sidebar.
3. Select **Rename**.
4. Enter the new name and confirm.

## Delete a Space

1. Open the Space you want to delete.
2. Select the Space name menu (⋯) at the top of the sidebar.
3. Select **Delete space**.
4. Confirm the deletion.

{% hint style="warning" %}
Deleting a Space hides it and all its Collections, but the data is recoverable. Contact support if you need to restore a deleted Space.
{% endhint %}

## Add a collection

1. Open the Space where you want to add a Collection.
2. Select **Add collection** at the bottom of the sidebar.
3. Choose **With AI** when you want the assistant to draft the collection name and columns from a short description. Choose **Blank collection** when you want to define the fields yourself, or **From a file** when you want to create the collection from a CSV or JSON file.
4. If you chose **With AI**, describe what you want to track. The assistant drafts the collection name and columns so you can review and edit them before creating the collection. Nothing is created until you confirm.
5. If you chose **Blank collection**, enter a name for the Collection and confirm.
6. If you chose **From a file**, upload a CSV or JSON file or choose one from the Space's connected **Files**. Review the inferred columns before importing the rows. CSV or JSON artifacts created by workflows connected to the Space also appear in the same list.

## Rename a collection

1. In the sidebar, hover over the Collection name and select the menu (⋯).
2. Select **Rename**.
3. Enter the new name and confirm.

{% hint style="info" %}
In the sidebar, you can drag the handle next to a collection name to reorder collections. The order is saved for your own view.
{% endhint %}

## Archive a collection

1. In the sidebar, hover over the Collection name and select the menu (⋯).
2. Select **Archive collection**.
3. Confirm the action.

{% hint style="info" %}
Archiving hides the Collection and all its rows, but the data is retained and can be recovered.
{% endhint %}

## Viewing connections in a Space

1. Open the Space you want to inspect.
2. On the Space overview, click **View connections**.
3. On the **Connections** screen, review the linked rows and collections in that Space.
4. Use the search box to filter rows or collections.
5. Click the back button to return to the Space overview.

As you trace connections, you can preview the titles of related rows together with the collection each row belongs to.

## Manage workflows in a Space

1. Open the Space you want to work in.
2. In the **Workflows** section on the Space overview, choose one of the following.
   * Click **Create workflow** to start a new workflow that is linked to this Space. In the creation dialog, you can start from scratch, duplicate a template, or import a YAML or `.genesisworkflow` file.
   * Open the add menu next to **Create workflow**, click **Link existing workflow**, and then select a workflow from the current workspace.
3. Review linked workflows from the same **Workflows** section.
4. To remove a linked workflow from the Space, open that workflow's menu and click **Unlink**.

Linked workflows display their labels below the workflow name. Use the **Labels** filter to narrow the list, and edit labels from each workflow row's menu.

## Edit schema (columns)

Customize the columns of a Collection by editing its schema. If you only want to change which fields appear in the table, use **Columns** in the collection view. You can choose the visible fields, including long-text fields, and their order, and that table setting is shared for the collection.

1. Open the Collection whose schema you want to edit.
2. Select **Edit columns** (pencil icon near the column headers).
3. In the schema editor:
   * Select **Use AI** to describe the columns you want to add or change in natural language. Review the proposed columns before saving, and adjust their labels or types manually if needed.
   * Select **Add field** to add a new column. Enter a label and choose a type.
   * Select an existing field to rename it, change its type, mark it as required, or edit its options (for Select fields).
   * Drag a field to reorder it.
   * Select **Archive** on a field to hide it without deleting its data.
4. Select **Save schema** to apply changes.

To link a workspace file from a row, choose **File** as the field type. A File field stores one workspace file, and when you edit a row you can use **Select file** to keep the latest version or pin a specific version. Clear the field when you no longer need the link.

{% hint style="warning" %}
Some schema changes affect existing data. When you save, the editor lists any risks — for example, changing a field's type may cause existing values to display incorrectly, and archiving a sub-collection field hides its nested data permanently (it cannot be restored from the editor). Review these warnings before confirming.
{% endhint %}

## See also

* [About Spaces](/spaces/about-spaces.md)
* [Manage rows](/spaces/manage-rows.md)