Skip to main content

Getting Started Guide

Learn the recommended workflow for getting up and running with Glossa quickly and effectively.

Written by Ali
Updated today

Overview

This guide walks you through the essential first steps in Glossa, from creating your first project to reviewing your first AI-generated requirements. Following this sequence helps you experience Glossa's core value quickly without getting overwhelmed by all the available features.

Recommended time: 15-30 minutes to complete your first project setup

Quick Start Workflow

The Recommended Sequence

  1. Create your first project (2 minutes)

  2. Upload a document (1 minute)

  3. Review generated requirements (10-15 minutes)

  4. Set up integrations (later, when you're ready)

Why this order?

  • Gets you to value fastest (see requirements generated)

  • Avoids integration setup friction initially

  • Lets you experience core product before advanced features

  • Builds confidence before tackling more complex setup

Step 1: Create Your First Project

Navigate to Projects

  1. After logging in, you'll land on the Projects page

  2. If not, click Projects in the main navigation

Create a New Project

  1. Click Create Project

  2. Fill in project details:

    • Project name - Use a real project name (e.g., "Acme CRM Implementation")

    • Is this project a migration? - Check the box if your project is moving your client from one tool to another

    • Stage - Discovery, Design, Build, Test, Deploy, or Support

    • AI Requirements Detail - Choose the volume and detail of generated requirements

    • Client - Select existing or create new client

    • Source System (optional) - Legacy system being replaced (for migrations only)

    • Target System - What you're building in, or migrating into

  3. Upload your first file (final step of project creation):

    • Drag and drop your file OR click to browse

    • Select a document, meeting recording, or other source file

  4. Click Finish

Tips:

  • Use a real project, not a test project

  • Use descriptive names

  • Don't worry about perfection - you can edit later

  • Skip integrations for now - we'll do those later

Best first files:

  • Meeting notes from recent discovery call

  • Email thread discussing requirements

  • Existing requirements document (Word, PDF)

  • Project brief or scope document

Avoid for first upload:

  • Templates or blank forms

  • Invoices or administrative docs

  • Very large files (> 100 MB) for first test

What Happens Next

After creating your project:

  • File begins uploading immediately

  • File processes in background (2-6 minutes for most documents)

  • Requirements will be generated automatically

Step 2: Wait for Processing and Review Requirements

Check Processing Status

After project creation, your file is processing automatically.

Where to check:

  • Click Files tab to see processing status

  • Look for status: Pending → Processing → Ready

  • Bottom of Files tab shows: "Files currently processing: [number]"

Processing times:

  • Small documents: 2-6 minutes

  • Large documents or videos: 10-30+ minutes

  • You can navigate Glossa while waiting

Navigate to Requirements

  1. Click Requirements tab

  2. You'll see a table of auto-generated requirements

  3. Each requirement has:

    • ID (e.g., ACM-CRM-0001)

    • Requirement Name

    • Priority

    • Status (Draft by default)

    • Type

    • Category

    • Quality Score

Explore a Requirement

  1. Click on any requirement to open it

  2. You'll see tabs:

    • Reference Data - Citations to source file

    • Acceptance Criteria - Generate ACs here

    • AI Review - Review the requirement quality assessment

Check the Citations

  1. Click Reference Data tab (open by default)

  2. You'll see:

    • Source file name

    • Relevant excerpt or timestamp

    • "Open Preview" link

  3. Click Open Preview or the file name

  4. For documents: See highlighted sections where requirement came from

  5. For audio/video: Jump to timestamp where requirement was mentioned

This is the magic: Every requirement links back to exactly where it was mentioned.

Review Quality Scores

  1. Click AI Review tab

  2. Look at the quality score, key insights, category breakdown, and follow-up questions

    1. Scores indicate completeness, clarity, testability, etc.; lower scores suggest areas needing refinement

  3. Click the Chat with AI button to brainstorm how to improve the requirement with Glossa

Edit Requirements

  1. Click a requirement to open it

  2. Click the three dots menu on the top right corner, then Edit Requirement

  3. Edit title or description

  4. Change priority, status, type, or category

  5. Save changes

  6. All edits are tracked automatically

Need to update multiple requirements at once? Select checkboxes next to several requirements, then click Edit in the toolbar to bulk update Priority, Status, Type, or Category across all of them. You can filter the list first — your selections are preserved when filters change.

Step 3: Explore Additional Features

Generate Acceptance Criteria

You can generate ACs one at a time or in bulk:

Individually: Open a requirement → go to the Acceptance Criteria tab → click Generate Acceptance Criteria

In bulk: From the Requirements tab, click Generate ACs for All Requirements. This will generate ACs for all requirements in the current filtered view, excluding requirements that already have ACs.

Either way, review the generated ACs in all formats (Gherkin, User Story, Checklist, Freeform) and edit as needed.

Check for Contradictions

  1. Go to Requirements tab

  2. Click Conflicted Requirements sub-tab

  3. Review any contradictions Glossa detected

  4. Resolve using Merge, Ignore, or Cancel options

Note that conflicted requirements will only appear after the nightly job has run.

Review Capabilities

  1. After requirements have been generated, go to the project Dashboard

  2. Click Capability Review

  3. Glossa has compared your requirements against your organization's Library

  4. Review suggested matches across three tabs: High Match, Needs Review, and Unmatched

  5. For High Match items, verify the auto-match is correct (click Unmatch if not)

  6. For Needs Review items, choose to adjust the requirement, update the library, create a new capability, or skip

  7. For Unmatched items, decide whether to add to library, keep as project-specific, manually match, or cancel

Once requirements are matched to library capabilities, the corresponding categories appear in your project's Categories tab.

See the Capability Review article for the full workflow.

Step 4: Set Up Integrations (When Ready)

After you've explored the core features, set up integrations:

Meeting Integrations

Google Meet or Microsoft Teams:

  1. Go to Integrations

  2. Enable Google Meet or Microsoft Teams

  3. Connect your account

  4. Add client contact emails to your project

  5. Future recorded meetings will auto-process

Email Integrations

Gmail or Outlook:

  1. Go to Integrations

  2. Enable Gmail or Outlook

  3. Connect your account

  4. Go to project → Files → Add Input Data → Email

  5. Select emails to import

Slack Integration

For Slack conversations:

  1. Enable Slack integration

  2. Connect your workspace

  3. Map Slack channels to projects

  4. Tag @GlossaBot in messages to capture requirements

Jira Integration

For delivery handoff:

  1. Enable Jira integration

  2. Connect to your Jira instance

  3. Configure Jira project settings

  4. Map Glossa project to Jira project

  5. Send requirements to Jira when ready

Why wait on integrations?

  • Takes time to set up each one

  • Can be overwhelming on day one

  • Core value is in requirements generation

  • Better to experience that first

Tips for Success

Start Small

For your first project:

  • Use one real but small project

  • Upload 1-3 documents to start

  • Review and refine requirements

  • Add more files as you get comfortable

Don't:

  • Upload 50 files on day one

  • Try to set up all integrations immediately

  • Expect perfection from AI on first try

  • Overthink it - just start

Review and Refine

AI-generated requirements are a starting point:

  • Always review each requirement

  • Edit for clarity and completeness

  • Add details AI may have missed

  • Merge or delete duplicates

  • Use AI Review to improve quality

Don't expect:

  • 100% perfect requirements without review

  • AI to understand unspoken context

  • Every single detail captured automatically

Use Real Projects

Best way to learn:

  • Use actual project with real requirements

  • Upload actual discovery notes or docs

  • Invite real team members

  • Makes learning immediately valuable

Avoid:

  • Creating test/demo projects

  • Using fake or lorem ipsum content

  • Working solo when you have a team

Invite Your Team

After you're comfortable:

  1. Go to Members tab

  2. Click Add New Member

  3. Invite colleagues

  4. They get immediate access to all projects

  5. Collaborate on requirements together

Ask Questions

Need help?

  • Click chat icon (bottom right corner)

  • Email [email protected]

  • Check docs.glossapro.ai

  • We're here to help you succeed

Common First-Time Questions

"How accurate are the AI-generated requirements?"

Answer: Accuracy depends on source material quality. Clear, detailed discovery notes produce accurate requirements. Vague notes produce vague requirements. Always review and refine.

"Can I delete requirements?"

Answer: Yes! Delete irrelevant or duplicate requirements anytime. Or change status to "Canceled" to keep them but mark as not needed.

"What if requirements are too high-level or too detailed?"

Answer: Adjust the Requirements Detail Level in Project Settings. Choose Broad Strokes, Balanced, or Granular. Then upload files again to see different detail levels.

"Do I need to set up all integrations?"

Answer: No! Only set up integrations you'll actually use. Manual file upload works great for many teams. Start simple, add integrations when needed.

"Can I change project settings later?"

Answer: Yes! Edit project name, systems, granularity, etc. anytime in Project Settings.

"What happens if I upload the same file twice?"

Answer: Glossa will process it twice and create duplicate requirements. Delete one copy of the file to remove duplicates.

Next Steps

After Getting Started

Once you're comfortable with basics:

  1. Upload more source material

    • Meeting recordings

    • Email threads

    • Additional documents

    • Slack conversations (via @GlossaBot)

  2. Refine requirements

    • Review all generated requirements

    • Edit for clarity

    • Add missing requirements manually

    • Resolve contradictions

  3. Generate ACs

    • Create acceptance criteria for requirements

  4. Set up integrations

    • Connect meeting tools (Meet/Teams)

    • Connect email (Gmail/Outlook)

    • Connect Slack for async discussions

    • Connect Jira for delivery tracking

  5. Send to clients or send to Jira

    • Use the Client Portal to share for stakeholder review

    • Send to Jira for development tracking

    • Keep Glossa as source of truth

Troubleshooting

"My file uploaded but no requirements were generated"

Possible reasons:

  • File contains no actual requirements (template, invoice, etc.)

  • Content too vague to extract requirements

  • File processing encountered error

What to do:

  • Check file shows "Ready" status (not "Error")

  • Open file in Glossa to verify content

  • Try uploading more detailed documentation

  • Contact support if file should have requirements

"Processing taking forever"

Normal processing times:

  • Small documents: 2-6 minutes

  • Large documents: 5-15 minutes

  • Long videos: 20-30+ minutes

If stuck longer:

  • Refresh browser

  • Check "Files currently processing" counter

  • If still stuck after 1 hour, contact support

"Requirements don't match my expectations"

Common causes:

  • Wrong granularity level (too broad or too detailed)

  • Source material unclear or incomplete

  • AI interpreted content differently than you expected

What to do:

  • Adjust Requirements Granularity Dial in Project Settings

  • Upload more detailed source material

  • Edit requirements manually

  • Add missing requirements yourself

Related Articles
Google Meet
Microsoft Teams
OneDrive
Jira
Jira workflow best practices
Did this answer your question?