Overview
Projects are the top-level organizational unit in Glossa. Each project represents a single software implementation, migration, or enhancement effort and contains all related requirements, files, and acceptance criteria.
Creating a New Project
Step-by-Step Process
Creating a project in Glossa follows a guided flow that ensures you capture all necessary information:
Navigate to Projects
Click on Projects in the main navigation
Click Create Project
Name Your Project (Required)
Enter a descriptive name for the project
This name will be used in requirement IDs
Example: "Pawsome CRM Implementation"
Select if the project is a migration (Required)
Check the box if you're moving from one system to another
Keep the box unchecked if you're building within an existing system
Choose Project Stage (Required)
Discovery - Gathering requirements
Design - Planning the solution
Build - Development phase
Test - QA and UAT
Deploy - Going live
Support - Post-implementation maintenance
Set AI Requirements Detail Level (Required if Requirements Style is not set up)
Broad Strokes - High-level requirements for early discovery/sales
Balanced - Standard detail for most discovery work
Granular - Deep implementation details
See the AI Requirements Detail section below for detailed guidance
Set Output Language (Required)
English — generated requirements, acceptance criteria, business outcomes, and refinements are written in English regardless of the source material's language
Same as Input — Glossa detects the language of your source material and generates requirements, acceptance criteria, business outcomes, and refinements in that language
You can change this later from project settings; it only affects content generated after the change
Select or Create Client (Required)
Choose an existing client from the dropdown, OR
Add client information into the fields below Add New Client for this Project to add a new one
See the Clients article for details on client management
Add Systems
For Migrations: Add one or more Source/Legacy systems and one or more Target/New systems
For Enhancements: Add one or more Target/New systems
Choose an existing system from the dropdown, OR
Enter the company name and product name (e.g., "Salesforce Sales Cloud")
You can add multiple systems on either side — useful for consolidations or multi-platform migrations
Select Categories (Optional)
Choose the categories relevant to this project
Glossa uses your selected categories to seed an initial set of Discovery Questions for the project — targeted questions that help you fill gaps in your requirements
Deselect any areas that don't apply so you aren't asked questions about them
You can change focus areas and answer questions later from the Questions page in the project
See the Discovery Questions article for details
Add Data Sources
If you've enabled drive integrations, you can select files and folders from connected drives to add to the project (see the Drive integrations article)
If you've enabled email integrations, you can select emails to add to the project (see the Email integrations article)
You can add files and folders from your local storage to add to the project
You can skip this and add input data later
Click Finish
You can go to the dashboard for the project you just created, or navigate to the list of all projects in the org
Required vs Optional Fields
Required Fields
Project Name - Must be unique and descriptive
Project Stage - Current phase of the project
Detail Level - Granularity and volume level for requirements
Client - Who the project is for
System - At least one target/new system (multiple source and target systems are supported)
Optional Fields
Source/Legacy System - Only needed for migrations
Understanding Project Settings
AI Requirements Detail
The AI Requirements Detail level determines the volume and granularity of generated requirements. It also determines which quality criteria are used to evaluate requirements in the AI Review.
Note: If your workspace has a Requirements Style configured, the Requirement Level setting will be bypassed — Glossa will use your style examples to shape generated requirements instead.
Level | Best For | Detail & Volume | Quality Criteria |
Broad Strokes | Sales discovery, early conversations | Very high level, fewest number of requirements | Clear, Correct, Feasible |
Balanced | Most discovery work, standard projects | Moderate level of detail, about twice as many requirements as Broad Strokes | Traceable, Unambiguous, Testable, Clear, Correct, Feasible |
Granular | Deep technical work, detailed implementation | Extremely detailed, about twice as many requirements as Balanced | All Balanced criteria + Independent, Atomic, Implementation-Free |
Important: You can change the Requirement Level later, but the new level only applies to requirements created after the change.
Output Language
Output Language controls what language Glossa uses when generating requirements, acceptance criteria, business outcomes, and requirement refinements.
English - All generated content is written in English, regardless of source language
Same as Input - Glossa matches the language of the source material for generated content
Important: Changing this setting only applies to content generated after the change — existing requirements, acceptance criteria, and business outcomes are not retranslated.
Project Stage
Stages help you track where you are in the project lifecycle:
Discovery - Gathering and documenting requirements
Design - Creating technical designs and architecture
Build - Active development
Test - QA, UAT, integration testing
Deploy - Release and go-live activities
Support - Post-launch maintenance and enhancements
Stages are informational and don't affect functionality—you can change them as the project progresses.
Migration vs Enhancement
Migration Projects:
Moving from one system to another
Requires at least one Source system and at least one Target system
Often involves data migration, business process replication
Examples: "Migrate from Legacy CRM to Salesforce"
Enhancement Projects:
Building new features in an existing system
Requires only Target system(s) — one or more
Examples: "Add new quote-to-cash flow in existing CRM"
After Creating a Project
Next Steps
Once your first project is created:
Upload Files - Add discovery meeting recordings, documents, emails
Review Generated Requirements - Check the requirements created from your files
Answer Discovery Questions — Open the Questions page to work through Glossa's seeded questions and close gaps in your requirements (see the Discovery Questions article)
Set Up Integrations - Connect Google Meet, Slack, Gmail, etc. (this will make it easier to add input data for all future projects)
Invite Team Members - Add collaborators (all org members can access all projects)
Check Capability Review — After requirements are generated, go to the Dashboard and click Capability Review to review requirements matched against your Library
Accessing Your Project
Navigate to your project from:
Projects tab in main navigation
Project shows all key information on the dashboard
Access Requirements, Files, and Categories from project navigation
Editing Project Settings
You can edit most project settings after creation:
Go to your project
Click More on the top right of the screen, then Edit Project
Modify any settings:
Project name
Project description
Project stage and status
Requirement Detail level (affects future requirements only)
Output Language (affects future generated content only)
Systems
Save changes
Note: Changing the client associated with a project may affect requirement IDs and citations.
Project Limits
Maximum Projects
There is no limit to the number of projects you can create in your organization.
Project Organization
Projects cannot be organized into folders or workspaces—they appear in a single flat list in the Projects view.
Deleting Projects
When to Delete
Delete a project when:
It was created by mistake
The project was canceled before work began
You want to permanently remove all project data
Warning: Deletion is permanent and cannot be undone.
What Gets Deleted
When you delete a project, Glossa removes:
All requirements and acceptance criteria
All uploaded files
All citations and conflict history
All project settings and configurations
What's NOT Affected
Integrations - Org-level integrations are unaffected
Client records - The client remains in your organization
Team members - No user access is changed
Categories - Categories can still be used in other projects
How to Delete
Go to the project
Click More on the top right of the screen, then Delete Project
Confirm deletion
Project is permanently removed
Important: You cannot recover a deleted project. If you're unsure, consider changing the status to inactive rather than deleting it.
Archiving Projects
Glossa does not currently support archiving projects.
If you want to preserve a project but mark it as inactive:
Include "COMPLETE" or "ARCHIVED" in the project name
Change the project status to Completed or Canceled
Simply stop working in the project and leave it in your project list
Best Practices
Naming Projects
Good names:
"Pawsitive - CRM Migration to Salesforce"
"Acme Corp - Q1 2025 Portal Enhancements"
"StateGov - Legacy System Modernization"
Poor names:
"Project 1"
"CRM" (which CRM? which client?)
"New Project" (not descriptive)
Tips:
Include the client name
Describe what's being built or migrated
Include timeframe if relevant (Q1, 2025, Phase 1)
Choosing Requirement Detail Level
Use Broad Strokes when:
You're in early sales conversations
Stakeholders are discussing concepts, not specifics
You need directional requirements for estimation
The project scope is still being defined
Use Balanced when:
You're in active discovery with committed stakeholders
You need testable, specific requirements
Development is planned in the next 1-2 months
This is a standard implementation project
Use Granular when:
You're defining detailed technical specifications
You're getting into implementation nuances
Development teams need atomic, independent requirements
You're working on complex integrations or migrations
Tip: Most projects use Balanced. Start there unless you have a specific reason to use Broad Strokes or Granular.
Project Stage Usage
Update your project stage as work progresses:
Move from Discovery → Design when requirements are complete
Move to Build when development starts
Move to Test when ready for QA
Move to Deploy for go-live activities
Move to Support after launch
This helps teams understand project status at a glance.
Troubleshooting
"Client is required" error
You must select or create a client before creating the project.
Solution:
Choose an existing client from the dropdown, OR
Click "Create New Client" and fill in client details
"System is required" error
Every project needs at least one target/new system.
Solution:
Enter the company and product name for the system, or pick an existing one
For enhancements, just add one or more target systems
For migrations, add at least one source system and at least one target system
I can't find my project after creating it
Check:
Projects tab in main navigation—all projects appear here
Verify the project name you used
Make sure you've refreshed the Projects list view
Solution: Projects cannot be hidden or archived, so if you created it, it should appear in the Projects list.
I set the wrong Requirement Level
You can change it:
Go to the project dashboard
Click More on the top right of the screen, then Edit Project
Change the Requirement Detail & Visibility level
Save changes
Important: The new level only applies to requirements created after the change. Existing requirements are not updated.
Note: If your workspace has Requirements Style configured, changing this setting won't affect generated requirements. Update your style examples in Settings instead.