> 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/about-spaces.md). # About Spaces Spaces is a workspace tab for managing structured QA data — test cases, feature lists, scenarios — in typed, editable tables. {% hint style="info" %} This feature is being gradually rolled out to customers. {% endhint %} ## Overview When QA teams collaborate on test design, they often need a shared, structured place to record and track items: which test cases exist, what their status is, which scenarios have been reviewed. Spaces provides that place inside Genesis, alongside the AI Assistant and Workflows, so you can keep structured data close to the AI-powered work that generates and uses it. A Space acts as a container for one or more **Collections** — typed tables of rows. Each row represents a single record (for example, a test case). You can define the columns that each row contains, choose a type for each column, and nest additional data under a row using sub-collections. ## Key concepts ### Space A Space is the top-level container inside the Spaces tab. A workspace can hold multiple Spaces — one per product area, test phase, or any other logical grouping that fits your team. ### Collection A Collection is a typed table of rows inside a Space. Each Space starts with at least one Collection. You can add more Collections to the same Space to hold different categories of data (for example, a Space for "Checkout flow" might contain separate Collections for test cases and for known bugs). ### Row A row is a single record in a Collection. Each row has a set of field values defined by the Collection's **schema**. You can open a row to see and edit all its fields in a detail view, and each save creates a new version in the row's history. ### Sub-collection A sub-collection is a nested table that lives under each row of a parent Collection. It is created by adding a **Sub-collection** field to the schema. For example, a "Test Suites" Collection might have a "Test Cases" sub-collection field, so each test suite row contains its own table of test cases, and each test case row can in turn contain a "Test Runs" sub-collection. ## Field types Each column in a Collection has one of the following types. | Type | Description | | ------------------ | ------------------------------------------------ | | **Text** | Single-line text | | **Long text** | Multi-line text | | **URL** | URL string | | **Number** | Numeric value | | **Yes / No** | Boolean checkbox | | **Date** | Date picker | | **Select** | Single-choice dropdown with custom options | | **Sub-collection** | Nested table of rows (see sub-collections above) | ## Built-in templates When you create a new Space, you can choose from four built-in starter templates or start from scratch. | Template | Description | | ---------------- | ---------------------------------------------------------------------------------------------------- | | **Test Cases** | Flat list of test cases with Title, Description, Steps, Expected result, Priority, and Status fields | | **Test suites** | Three-level hierarchy: Test Suites → Test Cases → Test Runs (all via sub-collections) | | **Feature list** | Lightweight tracker with Title, Summary, and Status fields | | **Blank** | Single Title field; build your own schema from scratch | ## Schema editing You can customize a Collection's columns at any time by editing its schema. From a Collection, select **Edit columns** to open the schema editor, where you can add new fields, rename existing ones, reorder them, change the type, and archive fields you no longer need. Archived fields are hidden from the table and forms but their data is retained. ## Row history Every time a row is saved, a new version is recorded automatically. Open a row and switch to the **History** tab to browse past versions and compare values. You can restore any previous version to roll back a change. ## AI Assistant and Workflow integration Spaces is readable and writable by AI. The AI Assistant can look up rows and report on their contents in a conversation. Workflows have access to the following built-in tools for reading and writing Spaces data. | Tool | What it does | | ------------------- | ------------------------------------------------------------------------- | | List Spaces | Returns all Spaces in the current workspace | | List Collections | Lists Collections under a Space or sub-collections under a row | | Get schema | Returns the active column definitions for a Collection | | List rows | Lists rows in a Collection with title and last-updated timestamp | | Search | Full-text search across rows in a Space or the entire workspace | | Get row | Returns all field values for a single row | | Create row | Adds a new row to a Collection | | Update row | Updates field values on an existing row (merge or replace) | | Create Space | Creates a new Space and its first Collection | | Create Collection | Adds a new top-level Collection to a Space | | Open sub-collection | Opens the per-row sub-table for a sub-collection field and returns its ID | This makes it possible, for example, to run a Workflow that reads your specifications from Resources and Context, generates test cases, and writes them directly into a Spaces Collection. ## See also * [Create and manage Spaces](/spaces/manage-spaces.md) * [Manage rows](/spaces/manage-rows.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.genesis.autify.com/spaces/about-spaces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.