1. Docs
  2. Build tests
  3. Analyze
  4. Folders, documents & archive

Folders, documents & archive

The requirement tree holds your folders, main requirements and documents. First-level folders are modules shared with App Map and Automate, so changes here reach those screens too.

7 min read Updated CustomersAdmins

In short

On this page you can

  • Create folders, main requirements and documents from the tree toolbar.
  • Understand why a folder under the project folder becomes a module.
  • Find requirements by name, ID, tag or Severity.
  • Keep specs and notes in Documents and edit them in place.
  • Archive a requirement or folder and restore it from Archive.

How to use it

  1. Click Create Folder under More and name the folder at once.
  2. Drag requirements into it, or use Move to folder in the row menu.
  3. Narrow the tree with Filter By Tags.
  4. Delete with Move to Archive; restore with Restore at the bottom of the tree.

The requirement tree#

The tree has two fixed roots: the project folder (named after the project, badge P) for requirements, and Documents for files. Neither can be renamed, moved or archived.

ItemWhat it is
Folder with MA module: a folder directly under the project folder.
Other foldersSub folders inside a module, for your own grouping.
Requirement rowA main requirement. Its sub-requirements are not rows; open the main to see them.
Document rowA file in Documents, with an icon by type (Word, image, other).
Number on a folderRequirements in this folder: main requirements in the folder and all its sub folders. See Folder count.
Archive (n)Archived items. See Archive and restore.

Tree toolbar#

  • New Requirement creates an empty main requirement in the selected folder, or in the project folder if nothing is selected. Then fill it in: see Create a main requirement.
  • More › Create Folder creates a folder named new_folder_n and puts it in rename mode.
  • More › Add New Document creates an empty New Document. See Documents.
  • Filter By Tags (funnel icon) opens the filter. A dot on the icon means a filter is on. See Find requirements.

Creating a requirement or a document adds one to your licence’s requirement counter. At the limit you see “Company license limit has been reached…”; see the fix.

Find requirements#

  • Search matches folder, requirement and document names (any part, ignoring case) and requirement or document IDs. It does not search sub-requirement names: open the main requirement for those.
  • Include and Exclude tags: only tags that are used in the tree are offered.
  • Severity: Critical, High, Medium, Low. Documents have no severity, so a Severity filter hides them.

Folders are modules#

A folder directly under the project folder is a module. Each module exists in three places at once, kept in sync by SmartestQA:

PlaceWhat the module is there
AnalyzeThe folder that holds the module’s requirements
Discover › App MapThe group of pages that the AI uses when you set Target scope to this module
AutomateThe twin folder where test cases created from this module’s requirements are stored
  • Create and rename travel. A new module folder creates the App Map module and the Automate folder; renaming it renames all three.
  • Names are unique. Two modules cannot share a name (“A module with this name already exists”), and the name cannot be empty.
  • Moving a folder to the top makes it a module. You see “name is now a module: its folder in Automate and its App Map module were created.”
  • Moving a module under another removes the module. SmartestQA asks “Make name a sub folder?”: its pages join the target module in App Map, and its Automate folder moves too. Only an Admin can do this.
  • Deleting a module needs an Admin. Archiving the module folder from the tree (“Archive the module name?”) moves the module, its folders in Analyze and Automate and everything in them to the Archive; its App Map pages go to Unassigned. Where a module is deleted directly instead of archived, SmartestQA refuses while its folders still hold items (“This module can’t be deleted yet…”).

A folder at the top is never “just a folder”

Create Folder with nothing selected creates new_folder_n under the project folder, which is a new module in App Map and Automate. Rename it right away, or select a module first so the new folder becomes a sub folder.

Move and rename#

  1. Move a requirement or folder

    Drag it onto a folder, or open the row menu (⋮) › Move to folder, type in Search folder and pick the target.

    “Moved to folder”.

  2. Rename a folder

    Double-click it, type the name, press Enter. The two roots cannot be renamed. An empty name shows “Name cannot be empty.”

  3. Rename a requirement

    Select it, change Name in the centre and click Save.

Nothing can be moved into or out of Documents: “Items cannot be moved in or out of the Documents folder.”

The Documents folder#

Documents keeps project files next to the requirements: specs, release notes, a glossary. Every project starts with project.md, a template with the sections Overview, Scope, Modules and Glossary. If you rename it, a new project.md is created.

Add a document#

  • Empty document: More › Add New Document creates New Document; write in it in Edit mode.
  • From a file: on the Import tab of any requirement folder, add the file and click Create as Document. The file is saved as a document without AI: “name created as Document”.

The document editor#

  • View / Edit switch at the top. Text documents and Word documents can be edited; save with Save.
  • Word (.docx) files: the text is extracted when you open them. If it is not, click Extract Text in Edit mode.
  • PDF and images are shown as a preview. Other files show “This file cannot be displayed as text. Please download to view.”
  • Download File gives you the original file back.

Rules of the Documents folder#

  • Folders and documents only: “Requirements cannot be created inside the Documents folder.” Sub folders are allowed.
  • No AI wizard: selecting the folder shows “This folder holds project documents only. Document analysis, requirement creation and moving items in or out are disabled here.”
  • Documents cannot be archived: “This item can’t be archived.”

Which documents the AI reads

The AI wizard reads only the files you attach on the Import tab. Documents saved in this folder are not sent to it. An AI assistant connected through MCP can read and write documents; see MCP.

Archive and restore#

Delete in Analyze moves items to the Archive. Nothing is lost until an Admin deletes it for good.

  1. Archive

    Open the row menu (⋮) › Delete. The dialog “Archive name?” lists what moves (folders, requirements), the Pipelines it is removed from and who created it (Created by). Click Move to Archive.

    “name moved to the Archive.”

  2. Restore

    Open Archive (n) at the bottom of the tree (title Archive · Analyze) and click Restore. The item goes back where it was.

  3. Delete for good (Admin)

    Click Delete for good on one item, or Empty archive. This cannot be undone.

When you archive a main requirementResult
Its sub-requirementsArchived with it
Links to test casesKept; the test cases stay in Automate
Pipelines that ran itIt is removed from them. Restoring does not put it back; add it to the pipeline again in Schedule.
Your requirement counterUnchanged: archiving does not free a slot (why)

Removing a sub-requirement is not archiving

Deleting a sub-requirement inside a main requirement and clicking Save deletes it for good, with its test case links. It does not go to the Archive. See Saving.

Who can do what#

ActionUserAdmin
Create, edit, move requirements and foldersYesYes
Archive a requirement or a sub folderOnly if you created everything in itYes
Archive a module, or move a module under anotherNoYes
RestoreWhat you archivedYes
Delete for good, Empty archiveNoYes

Roles are explained in Company Settings › Roles.

Video transcript

The tree starts at the project and has one folder per module, marked M, with a count. Open a module and select a main requirement. Its details open beside the tree: status, severity, dates, linked test cases and comments. Assessment (AI) is the next tab. Further down are the documents: specs and notes that AI generation reads. More adds a folder or a new document. Filter By Tags narrows the tree. Archive holds what you removed, until you restore it.

Module folders, sub folders, the Documents folder, filters and the Archive.

If something goes wrong#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai