Slack

The Slack integration allows you to capture requirements directly from your Slack conversations by tagging @GlossaBot. This enables you to document important discussions, decisions, and requirements as they happen in your team's natural communication flow.

Unlike meeting integrations that automatically process recordings, the Slack integration gives you granular control—only content you explicitly tag with @GlossaBot is sent to Glossa for processing.

When you tag @GlossaBot in a Slack message or thread, Glossa captures that content and determines whether it contains actionable requirements. If relevant requirements are identified, Glossa automatically creates them in the mapped project with full citations back to the original Slack conversation.

Key benefits:

You'll be redirected to Slack's authorization page where you'll:

After authorization, you'll be redirected back to Glossa.

GlossaBot can automatically access public channels, but if you want to use it in private channels:

Repeat this for each private channel where you want to use Glossa.

After connecting Slack, you need to map Slack channels to Glossa projects:

Important notes about channel mapping:

To send content to Glossa, tag @GlossaBot in your message:

What happens:

When you tag @GlossaBot in a thread, the entire thread content up to the tag is sent to Glossa:

In this example, all three messages would be sent to Glossa as context.

Best practice: Tag @GlossaBot at the end of a discussion thread once the decision or requirement is clear.

If files are attached to a message or thread that you tag with @GlossaBot, those attachments are also sent to Glossa and processed along with the message content.

Glossa uses AI to determine if tagged content contains actionable requirements:

Examples of content that typically generates requirements:

Examples of content that typically doesn't generate requirements:

When requirements are generated from Slack messages:

Citations link directly to the specific Slack message, giving you instant context and traceability.

To see which channels are mapped to which projects:

Option 1: From Integrations

Option 2: From Project Dashboard

To modify channel mappings:

To remove a channel mapping:

Note: Unmapping a channel does not delete requirements or files that were already created from that channel.

Possible causes:

Solutions:

Note that it sometimes takes a minute for GlossaBot to reply.

This is expected behavior when Glossa determines the tagged content doesn't contain actionable requirements. The content is still stored as a source file in your project.

If you believe requirements should have been generated:

Private channels only appear in the mapping interface after you've invited GlossaBot to them:

To fix incorrect mappings:

Moving a channel to a different project doesn't transfer existing requirements—it only affects future tagged messages.

Only tag @GlossaBot when:

Avoid tagging:

When important information is spread across a thread, tag @GlossaBot at the end of the thread rather than on individual messages. This ensures Glossa has the full conversation context.

Consider mapping:

Avoid:

After tagging important Slack content:

Slack works best as one of multiple input sources:

Glossa will automatically detect contradictions across all these sources.