# Glue 101 {% hint style="success" %} Glue has announced our Series A! Read all about it in the [blogpost here](https://glue.ai/blog/20m-to-build-agentic-team-chat). {% endhint %} **Glue is the better way to chat at work, without the noise and channel fatigue.** Replace Slack, Teams, Discord (or whatever work chat you use) with Glue to easily find the right conversations with the right people, every time. **Want to get started right away?** Check out our guides: {% content-ref url="/pages/vcJgKOlg3USWXjbSBVGP" %} [Getting started for admins](/get-started/getting-started-for-admins) {% endcontent-ref %} {% content-ref url="/pages/SLAnGjuM4KEgdpLDJ3qH" %} [Getting started for users](/get-started/getting-started-for-users) {% endcontent-ref %} {% content-ref url="/spaces/2RcaBgLNnK5MMFP9QKUF/pages/RpOBTk6l25rJvtIIAuwW" %} [API quickstart](/developers) {% endcontent-ref %} ## Key Concepts of Glue Glue is designed to make communication flexible and focused through two key organizing principles: **threads** and **groups.**

Threads and chats can be sent to any combination of groups and people.

### Threads **Threads** **contain topic-focused conversations.** They can be shared with multiple groups, individuals and Glue AI. Your relevant threads are tracked in your personal [inbox](/inbox/inbox). Threads are named with subjects, and contain multiple messages and at least one other participant. Thread participants can include groups and individuals within your workspace, and guests (external users). {% hint style="success" %} Any message can be converted into a new thread at any time to keep the conversations organized and relevant {% endhint %} ### Groups **Groups** **organize people and collections of threads** for departments, teams or projects. Each group has its own group chat that is private only to group members. Groups exist within a [workspace](https://docs.glue.ai/workspaces/workspaces), but can include both workspace members and [guests](https://docs.glue.ai/groups/guests) (external users). {% hint style="info" %} You can invite anyone to a Glue thread or group using their email address {% endhint %} ## **A More Organized Work Chat** Glue might look familiar to you at first — and that’s by design. We are not reinventing the entire UI of a work chat app. We are changing how conversations are organized. People and AI have more effective conversations with focused context. Glue threads provide **focused context** for more effective conversations * Quickly find the thread of conversation you need by asking Glue AI * Follow only the threads that are important to you in your inbox * Invite individuals and groups to specific threads instead of an entire channel * Archive threads when you no longer need to follow the conversation * Collaborate with Glue AI directly within a thread — same as interacting with other LLMs like ChatGPT # Getting started for admins Get your Glue workspace up and running smoothly {% stepper %} {% step %} #### Set up your workspace If your company does not already have a Glue workspace set up, you will have the option to create a workspace using your company email domain while you create your account. {% endstep %} {% step %} #### Migrating from Slack? Import your channels to Glue * You can convert public Slack channels into a Glue Thread (recommended for most) or Group * You don't need to bring everything over — we recommend choosing your most important channels so you can have a fresh start in Glue Check out [Slack Import](/for-admins/slack-import) for more information {% endstep %} {% step %} #### Create Groups for your teams * Map out your ideal group structure in advance — groups are for long term collaboration * Create critical groups (like departments) so that team members have spaces to collaborate when they join Glue * Team members can also create their own groups for smaller teams, projects or interest groups {% endstep %} {% step %} #### Bring your team onboard * For larger companies: start with a small pilot group to get feedback and train champions * [Ready to add everyone?](/for-admins/manage-members) Share your workspace's invite link or copy/paste in email addresses. {% endstep %} {% step %} #### Spread the word: Introduce Glue to your company! Let your company know why you've decided to use Glue and how to get started quickly with our training resources. * Customize [this message template](/for-admins/glue-launch-messaging-templates) or write your own * Send the message as a Glue Thread to show your team how to use Glue! * For larger companies: You may decide to send this communication in advance of adding your team. In this case, share the message via email or the chat app you're migrating from to prepare everyone for the change. {% endstep %} {% endstepper %} {% hint style="success" %} **Optional:** Connect applications to your workspace where we have integrations! Once an app is connected to your workspace, team members can add those apps to groups and threads {% endhint %} Refer to our documentation for more details on each of these steps: {% content-ref url="/pages/0wmIBCGLSLAYjW01SFlW" %} [Workspace setup](/for-admins/workspace-setup) {% endcontent-ref %} {% content-ref url="/pages/T36jVpLHQcmMNDKd1oTK" %} [Slack import](/for-admins/slack-import) {% endcontent-ref %} {% content-ref url="/pages/9AbVPJ9WdDNDm0kfB0I4" %} [Group setup](/for-admins/group-setup) {% endcontent-ref %} {% content-ref url="/pages/x5a7eaxQ6iesmHrlD03B" %} [Manage members](/for-admins/manage-members) {% endcontent-ref %} {% content-ref url="/pages/8qnt2uYvypAlhbZkOPus" %} [Glue launch messaging templates](/for-admins/glue-launch-messaging-templates) {% endcontent-ref %} # Getting started for users Start using Glue quickly as a new user! ## Getting your account set up {% content-ref url="/pages/Epz5PIz2HkVf2zR4nOZW" %} [Sign in to Glue](/profile-and-preferences/sign-in-to-glue) {% endcontent-ref %} {% content-ref url="/pages/781cPgaLYlJueGFhkZKY" %} [Download apps](/get-started/download-apps) {% endcontent-ref %} {% content-ref url="/pages/u1PM3nsq9ipY9DraxecI" %} [Push notifications](/profile-and-preferences/push-notifications) {% endcontent-ref %} {% content-ref url="/pages/r0dkChEAsC2vJOxyrkfl" %} [Help & support](/get-started/help-and-support) {% endcontent-ref %} ## Learning Glue - Fundamentals Once your account is setup, learn the core features to get up and running with Glue
Learn about Threads — where focused conversations happen * [What is a thread?](/conversations/threads#what-is-a-thread) * [When and how to create a thread](/conversations/threads/creating-new-threads) * [Managing threads over time](/conversations/threads/managing-threads) * [Benefits of the threaded model](/conversations/threads#thread-benefits)
Join Groups in your workspace — where teams and projects organize their threads * [What is a group?](/groups/groups-overview#what-is-a-group) * [How to find groups to join](/groups/groups-overview#browse-all-the-groups-in-your-workspace) * [Group chat vs Thread - when to use each](/groups/groups-overview#ways-to-interact-with-a-group)
Find what's important in your Inbox — your personalized view of Glue * [**What's in your inbox?**](/inbox/inbox#whats-in-your-inbox) * [Important Threads](/inbox/inbox#what-makes-a-thread-important) * Active [Groups](/groups/groups-overview#what-is-a-group) * Recent [DM’s](/conversations/direct-messages) * **How to know what needs your attention** * **Red badges** - you or a group you're in were directly @ mentioned * **Bolded message** - new activity but you are not @ mentioned
**Test out your Glue powers!** * [ ] Send your first thread to a group, multiple groups, multiple people - whatever combination you like! ## Learning Glue - Leveling Up!
Organize your inbox to personalize your Glue experience **Thread inbox management** * [Sort by unread or recent](/inbox/inbox#sort-threads-by-recent-or-unread) * [Follow / unfollow](/inbox/inbox#unfollow) * [Archive](/inbox/inbox#archive) * [Mark read / unread](/inbox/inbox#mark-read-unread) * [Set reminders](/inbox/inbox#set-a-reminder) * Manage which threads get to your inbox with [Group notification settings](/groups/group-settings/group-notification-settings) [**Star your favorites**](/inbox/inbox#star) Threads, groups, and DMs can be added to a special Starred section in your inbox for easy access
Use Glue AI to answer questions and collaborate with your team * [What is Glue AI?](/glue-ai/using-glue-ai#what-is-glue-ai) * [How to use Glue AI](/glue-ai/using-glue-ai#how-to-use-glue-ai) * 1:1 * Multiplayer with your team
# Download apps Download our mobile app and desktop app for easy access! Glue can also be used in the browser, but our apps will provide the best user experience. **Desktop apps** * [Mac via the App Store](https://apps.apple.com/us/app/glue-groups/id1559943932) * [Windows via the Microsoft Store](https://apps.microsoft.com/detail/9p0bfrbfpcd9) **Mobile apps** * [iOS via the App Store](https://itunes.apple.com/app/id1559943932) * [Android via the Play Store](https://play.google.com/store/apps/details?id=com.gluegroups.glue) {% hint style="info" %} [Enable notifications](/profile-and-preferences/push-notifications#during-account-setup) on desktop and mobile after downloading the Glue app to make sure no alerts are missed! {% endhint %} # Help & support ## Overview Hopefully this guide helps you get started in Glue and answers any questions, but if you have an issue or would like to give feedback you will always be able to reach someone from our team. For the best possible support on an issue, please try to give as much detail as you can on the issue in your first message — what were you expecting to happen in Glue and what happened instead? That will help us get back to you with a resolution faster! ## Ways to get support ### Reach out to us in Glue 1. Click on the Help (Question Mark) icon in the upper right side of the Glue app to expand the menu 2. Click "Contact support" to start a thread with the :zap:Glue Team 3. We will message back and forth about your issue or feedback directly in a Glue thread

Press the ? icon to expand the Help menu

Clicking "Contact support" will open a new thread with the Glue Team

### Reach us via email Send us an email at ### Ask Glue AI Glue AI has been trained on this entire guide as well as frequently asked questions from users. Start a thread with Glue AI or @mention it in an existing thread to get an immediate answer to your questions about Glue! Also when you first submit a support thread in Glue, Glue AI will make a first attempt at answering your question, if it thinks it has the answer, but someone from our team will still always view and repsond to your request! ## Check our status page If there are any incidents or outages to report, we will update our status page — [status.glue.ai](https://status.glue.ai). You can click the "subscribe to updates" button on that page to get emailed if any updates are posted to the status site. # Keyboard shortcuts Glue offers keyboard shortcuts to help you work faster, write better, and stay in flow. This page lists all current shortcuts and how to use them.We'll keep updating these as we roll out new features. *** ### Navigation & Search | Shortcut | Action | | -------------------- | ---------------------------------------------------------------------------------------------------------- | | `⌘ + K` / `Ctrl + K` | Open the [Command palette](/get-started/command-palette) **—** your central hub for navigation and actions | | `⌘ + F` / `Ctrl + F` | Focus the search bar to find messages, threads, people, and more | *** ### Composer & Messaging | Shortcut | Action | | ------------------ | ----------------------------------------- | | `⌘ + Enter` | Send your current message (default) | | `Enter` | Insert a new line in your draft (default) | | `⌘ + ↑ (Up_Arrow)` | Edit your last message. | {% hint style="info" %} You can change the message send behavior in **Preferences > Editor options** if you want Enter to send instead. {% endhint %} *** ### Quick Mentions & Emojis | Shortcut | Action | | ------------------------ | -------------------------------------------------- | | `: + text` | Opens emoji autocomplete (e.g., `:thumbsup:` → 👍) | | `@ + text` or `[ + text` | Mention a user, thread, or group | *** ### What’s Coming We’re actively expanding shortcuts—including admin actions and deeper integrations—so stay tuned! # Command palette The **command palette** is a powerful shortcut tool in Glue that helps you do more with fewer clicks. It lets you jump anywhere and trigger actions using just your keyboard. It’s designed to grow as Glue adds more features—so you’ll see more commands available over time. *** ### What It Is Press: * **macOS:** `⌘ + K` * **Windows / Linux:** `Ctrl + K` This opens a searchable menu where you can type what you want to do—whether that’s navigating, starting a thread, or managing content. ***
### Quick Actions You Can Do Today Here are some examples of what you can accomplish with the **command palette**: #### 🔍 Navigation * Jump to any **group**, **channel**, **direct message**, or **thread** * Go directly to **Settings**, **Search**, or other app areas #### 🧵 Thread Actions * Start a new thread * Rename or archive an existing thread * Pin or unpin a thread * Follow/unfollow threads #### 💬 Conversations * Switch between recent conversations * Open a specific thread or DM instantly #### 📌 Recent Items * See your **recently used threads** and pick one quickly *** ### How It Works * **Type to filter:** As you type, results update in real time. * **Arrow keys:** Use `↑` / `↓` to navigate the list. * **Enter:** Select your command. * **Autocomplete:** Common targets and actions appear first. *** ### 📈 Coming Soon Glue will expand command coverage over time to include: * Group & workspace management * Admin actions (when permitted) * Integration-triggered commands (e.g., `/calendar`, `/zoom`) * Personalized suggestions based on usage # Messaging in Glue Glue is designed to adapt to how your team actually works. Whether you're having a quick one-on-one chat, coordinating with your department, or managing a complex project across multiple teams, Glue gives you the flexibility to communicate in the way that makes the most sense. ### Three ways to communicate Glue offers three core message types, each optimized for different situations: #### Threads Threads are the core of Glue. These are organized discussions with specific participants that you can add or remove as the conversation evolves. **Perfect for:** * Project coordination across multiple people and groups * Discussions that need focused participants * Topics that require organized back-and-forth conversation {% content-ref url="/pages/ybwICBvHEo2gjjLbbzap" %} [Threads](/conversations/threads) {% endcontent-ref %} #### Direct Messages (DMs) One-on-one private conversations between two people. **Perfect for:** * Quick questions that don't need a group audience * Private or sensitive discussions * Following up individually with someone {% content-ref url="/pages/MB5Y3TlEa5RoIbbJxacw" %} [Direct messages](/conversations/direct-messages) {% endcontent-ref %} #### Group Chat Shared conversations where all members of a group can participate. **Perfect for:** * Team announcements and updates * Real-time casual discussion * Information everyone in the group should see {% content-ref url="/pages/NR4i3OpTOFWzWmOjfAsB" %} [Group chat](/conversations/group-chat) {% endcontent-ref %} ### Choosing the right message type Not sure which to use? Here's a quick guide: | Your Situation | Use This | | ------------------------------------------------ | ------------------ | | Coordinating specific people on a topic | **Thread** | | Discussion involves people from different groups | **Thread** | | Need to keep organized records of decisions | **Thread** | | Need to chat privately with one person | **Direct Message** | | Want everyone in a group to see something | **Group Chat** | | Quick informal team conversation | **Group Chat** | {% hint style="success" %} **Flexible by design:** Any message can become a thread! If a conversation in Group Chat or a DM grows beyond its original scope, you can create a thread from that message to bring in additional participants. {% endhint %} *** ### What you can do with messages All message types in Glue support rich features to help you communicate effectively: #### Express yourself * **Text formatting** - Bold, italics, headings, lists, and code blocks * **Emojis and reactions** - Add personality and quick responses * **Attachments** - Share files, images, and documents #### **Voice messages** * Record and send up to 5 minutes of audio, right in the message composer on desktop and mobile. * Tap to start and end, and you can review before you send. * Make sure to accept the prompts to give Glue access to your device's audio settings. You can grant access from your [preferences menu](/profile-and-preferences/preferences#audio). #### Get attention and organize * **@ Mentions** - Notify specific people or reference threads * **Quote replies** - Respond to specific messages with context * **Glue AI** - Get help, summaries, or information by mentioning @Glue AI #### Manage your messages * **Edit messages** - Fix typos or update information * **Delete messages** - Remove messages you've sent * **Search** - Find past conversations and information #### Read Receipts * Check who has seen your most recent sent messages. You can see a list of up to 5 people, and a count of the rest. * This shows up in the lower righthand corner of your most recent message as an avatar pile that you can hover over for more information.
Explore formatting and rich content → {% content-ref url="/pages/MEgJkjUva6IclHPPbFYo" %} [Formatting your messages](/conversations/formatting-your-messages) {% endcontent-ref %} Master mentions and notifications → {% content-ref url="/pages/uQGkARH6OltbWuHgwFuH" %} [Mentions and notifications](/conversations/mentions-and-notifications) {% endcontent-ref %} *** #### **Ready to dive deeper?** Explore: * [Threads](/conversations/threads) - Master Glue's most powerful messaging feature * [Using Glue AI](/glue-ai/using-glue-ai) - Enhance your workflow with AI assistance * [Keyboard shortcuts](/get-started/keyboard-shortcuts) - Work faster with keyboard commands *** # Messaging best practices Glue is built around a simple insight: most conversations start casually but evolve into something more structured. That's why **threads are the core unit of conversation** in Glue, not channels. ## Start with threads **Default to threads for most communication.** Unlike channels where conversations compete for attention in a single stream, each thread in Glue is a focused, organized space that adapts as your work evolves. #### When to use each message type | Message Type | Use For | Example | | -------------------- | ------------------------------------------------- | ----------------------------------------------------------------------- | | **Thread** (default) | Any work discussion, even casual ones | "Quick question about the API", "Let's plan Q4", "Bug in checkout flow" | | **Group Chat** | Announcements, time-sensitive alerts, social chat | "Office closed Monday", "Happy birthday! 🎉" | | **DM** | Private, sensitive one-on-one conversations | Personal matters, confidential feedback | **Rule of thumb:** If there might be a reply or follow-up, start a thread. Group chat is for information that stands alone. #### Why threads work better **Threads vs. Slack channels:** * **Focused** - Each discussion has its own space, not competing in a crowded channel * **Flexible** - Add or remove people as conversations evolve * **Organized** - Clear titles make conversations searchable and easy to find * **Intentional** - People are included because they're relevant, not "just in case" > **💡 Key difference:** In Slack, you @ mention people in channels. In Glue, you **add people as thread participants**. They'll see all messages without individual mentions, and it's clearer who's actively involved. *** ## Creating effective threads #### Write clear thread titles Thread titles are how you'll find conversations later: ✅ **Good:** "Q4 Marketing Budget Review", "Bug: Safari login failure", "Decision needed: Holiday schedule" ❌ **Avoid:** "Question", "Quick chat", "Thoughts?" #### Start small, grow organically Begin with whoever needs to be involved: ``` "Hey @Sarah, quick question about the API design" ``` Add more people as the conversation evolves: ``` "Good feedback—adding @Dev Team for their input" ``` Create new threads when topics shift: ``` "This is getting into deployment—I'll create a separate thread for that" ``` #### Provide context for async work * Include relevant background upfront * Attach necessary files or links * Set clear expectations: "Need input by Friday EOD" * Use @Glue AI to summarize long threads for people catching up *** ## Writing clear messages #### Make messages scannable * **Bold** action items and important information * Use bullet points for lists of 3+ items * Break long messages into short paragraphs (2-4 sentences) * Front-load the most important information **Before:** "So I was thinking about the presentation and noticed the data changed—can you update it?" **After:** "Can you update the presentation deck? The Q3 data has changed." #### Be specific about what you need * ❌ "Thoughts on this?" * ✅ "Does this pricing work for enterprise clients?" * ❌ "Can you look at this when you get a chance?" * ✅ "Can you review this by Thursday EOD?" *** ## Using mentions effectively #### Respect attention Every @ mention sends a notification. Use them intentionally: **DO mention when:** * You need someone's specific input or action * You're asking a direct question * You're adding someone new to a thread **DON'T mention when:** * They're already a thread participant (they'll see it anyway) * It's FYI information without action needed #### Add people to threads, don't just mention them **Better approach:** Add people as thread participants so they see all messages, not just the one where you mentioned them. #### Use group mentions sparingly Only @ mention entire groups for: * True emergencies or critical announcements * Time-sensitive information everyone must see immediately **For most situations:** Create a thread with the group instead—it's visible but less disruptive. #### Link to threads for context Instead of re-explaining, reference related threads: "See the approach we decided on in @Design Review Thread" *** ## Migrating from channel-based thinking If you're coming from Slack, shift your mental model: > **Old:** "I'll post this in #engineering"\ > **New:** "I'll create a thread with the engineers who need to weigh in" > **Old:** "Is there a channel for this?"\ > **New:** "I'll start a thread and include the right people" > **Old:** "Should I DM or post in the channel?"\ > **New:** "I'll start a thread—it's the most flexible option" Think in **conversations**, not **locations**. *** ## Quick reference #### Before sending a message, ask: * [ ] Should this be a thread? (If there might be discussion → yes) * [ ] Is my thread title specific and searchable? * [ ] Have I included the right people as participants? * [ ] Is my message clear and scannable? * [ ] Am I being specific about what I need? * [ ] Are my @ mentions necessary? #### Common scenarios **"Quick question about your code"** → Thread (even "quick" questions often need follow-up) **"Office closed tomorrow"** → Group Chat (pure announcement) **"What do you think about this approach?"** → Thread (discussion needed) **"Can someone help with this bug?"** → Thread (keeps troubleshooting organized) **"Want to grab coffee?"** → DM (personal and social) *** **Remember:** When in doubt, use a thread. It's easier to start organized than to migrate a messy conversation later. **Learn more:** * [Threads](/conversations/threads) - Deep dive into thread features * [Mentions and notifications](/conversations/mentions-and-notifications) - Master @ mentions # Formatting your messages Glue supports rich message formatting to help you communicate clearly and professionally. Use these tools to structure your content in threads, chats, and DMs. ### Content Types Supported Glue messages support the following: * **Attachments:** Share files, images, documents * **Emojis & reactions:** Express tone and reactions * **Links:** URLs automatically become links * **Mentions:** Notify users or groups * **Quote replies:** Reference specific messages * **@Glue AI:** Ask for help, summaries, or information *** ### Text Formatting Glue formatting uses Markdown-style syntax. #### Basic Text | Style | How to write | | -------- | --------------- | | **Bold** | `**bold text**` | | *Italic* | `*italic text*` | | `Code` | `` `code` `` | #### Structured Content
| Structure | Syntax | | ------------------------------- | -------------------------------------------------------------------------------- | | Bulleted lists | `- item` or `* item` | | Numbered lists | `1. item` | | Headings | `# Heading level 1 (h1)`, `## Heading level 2 (h2)` , `### Heading level 3 (h3)` | | Divider (horizontal line break) | `---` | | Blockquote | `> your text here` | {% hint style="info" %} **Tip:** Always include a space after heading markers (e.g., `## Heading text`). {% endhint %} {% hint style="warning" %} **Note:** There is currently not support for sending formatted tables in a message. Only Glue AI can send a table. {% endhint %} ### Block & Inline Code For sharing code snippets, use triple backticks: ` ```console.log("Hello world")``` ` will appear as ``` console.log("Hello world") ``` {% hint style="success" %} Pasting formatted text from another app will carry the formatting over to Glue! {% endhint %} # Mentions and notifications Mentions (`@`) in Glue serve two distinct purposes: **notifying people** and **linking to conversations**. Understanding the difference will help you communicate more effectively. **@ Mentioning users and groups** alerts people and can add them to conversations. When you type `@` followed by a person or group name, you're trying to get their attention or bring them into the discussion. How this works depends on whether you're in a thread, group chat, or DM. **@ Mentioning threads** creates a reference link without notifying anyone. When you type `@` followed by a thread name, you're pointing people to related information. This is useful for connecting conversations or providing context, but it won't ping anyone or send alerts. This guide covers both types of mentions and when to use each one. *** ## Mentioning and notifying users and groups ### @ Mentions in Threads Threads are flexible - you can add and remove participants as conversations evolve. Mentions help manage this. #### **Creating a new thread with @ mentions** When you @ mention someone while creating a thread: 1. They're automatically added to the member list 2. You can remove them before sending if needed 3. Once sent, they'll receive a notification and see the thread in their inbox #### **@ Mentioning in existing threads** The behavior depends on whether the person is already a member: **If they're NOT already on the thread:** * You'll see a prompt asking if you want to add them * By default, they're NOT added automatically * If you choose to add them, they'll be notified when you send the message * If you don't add them, their name appears as a clickable reference (no notification) **If they're already on the thread:** * They receive a notification highlighting your mention * The thread appears prominently in their inbox with a badge #### @ Mentioning Users or Groups in Group Chats or DMs Group chats and DMs are inherently private, so mentioning other users and groups does NOT add them to the conversation if they are not already in the group. Keep this in mind when tagging people! **When @ mentioning a user or group who is not in the Group or DM** * The @ mention will only show up as a reference. **When @ mentioning the user you are DMing or the Group you are Group chatting** * The @ mention will alert the user or Group by putting a red badge next to the chat in their inbox. #### **@ Mentioning an entire group** You can notify all members of a group by @ mentioning the group name in a thread where that group is already a member. This works similarly to `@here` or `@channel` in other platforms. {% hint style="info" %} **Tip:** Group mentions only work when the group is already a member on the thread. {% endhint %} *** ## Mentioning Thread Names Thread mentions let you reference other conversations without sending notifications to anyone involved. Think of them as citations or hyperlinks within your messages. #### How thread mentions work When you @ mention a thread name: * A formatted, clickable link appears in your message * Anyone can click the link to view that thread (if they have access) * **No notifications are sent** to participants on the mentioned thread * The link shows the thread title, making it clear what you're referencing #### When to use thread mentions **Reference related discussions:** "We discussed the timeline in `@Q4 Planning Thread`" **Point to decisions or context:** "See the final approach we agreed on in `@API Design Discussion`" **Connect cross-functional work:** "Marketing details are tracked in `@Product Launch Campaign`" **Avoid repeating information:** Instead of re-explaining background, link to the thread where it was discussed #### How to mention a thread 1. Type `@` in any message 2. Start typing the thread name 3. Select the thread from the dropdown menu 4. The thread link appears inline with your message {% hint style="success" %} **Pro tip:** Thread mentions work in threads, group chats, and DMs - they're a great way to share context across different conversation types. {% endhint %} {% hint style="info" %} **Remember:** Unlike user mentions, thread mentions never trigger notifications. If you need to alert people about the referenced thread, combine the thread mention with user mentions: "Hey @Sarah, can you review the decisions in @Budget Planning Thread?" {% endhint %} # Resource sidebar The resource sidebar helps you connect related conversations and files in one accessible place. It automatically tracks links, threads, and media shared in your conversations, and lets you pin the most important ones for quick access.
*** ## How the sidebar is organized The resource sidebar has three main sections that work together to help you access content: #### Pinned Your most important resources stay at the top. Pin threads, links, media and messages that provide essential context or that you'll reference repeatedly throughout the conversation. Pinned items remain visible even as new content is shared. #### Recent Links Automatically populated as people share threads and URLs in the conversation. See the last 20-30 links shared, with the most recent at the top. This includes both Glue threads and external websites—anything clickable that's been shared. #### Recent Media A visual grid of images and videos shared in the conversation. Quickly browse screenshots, designs, photos, and other visual content without scrolling through messages. Click any item to view full-size or download. {% hint style="info" %} Content appears automatically in Recent sections as it's shared. When something becomes essential to the conversation's context, pin it to keep it at the top {% endhint %} *** ## Benefits of the resources sidebar * See all of your connected discussions — including shared threads — and pin them for long term access * Manage project work or decision trails by linking related threads * Keep important files easily accessible *** ## How to pin a resource
Pin from Recent sections 1. Open the conversation and look for the resource sidebar on the right 2. Find the item you want to pin in Recent Links or Recent Media 3. Hover over the item and click the **+** icon 4. The resource immediately moves to the Pinned section at the top
Manually pin a URL or thread If you want to pin a URL or a thread that hasn't been shared in the conversation yet: 1. Click the **"+"** in the Pinned section of the sidebar 2. Select "Add Link" or "Add Thread" 3. Paste the URL or search for the thread by name 4. Click to confirm—the link appears immediately in your Pinned section
Pin a message from the thread See [Pinning Messages](https://docs.glue.ai/conversations/threads/managing-threads#pinning-messages-in-a-thread)
## What you can pin * **Threads** - Related discussions from anywhere in your workspace * **Files** - Documents, images, and attachments shared in the conversation * **Links** - External websites and resources * **Messages**
What's not supported with pinning * Threads from other workspaces * User profile pages * Group pages * Other non-thread Glue URLs
*** ## Resources FAQ's
Who sees pinned resources? All members of the conversation see the same pinned items in the sidebar. When you pin something, you're making it accessible to everyone in that thread, group chat, or DM.
Can I pin the same thread in multiple places? Yes! A single thread can be pinned to as many other conversations as you need. This is useful when a key discussion relates to multiple projects or topics.
What happens if someone deletes a pinned thread? The pin is automatically removed from all sidebars where it appeared. The reference gets cleaned up within a few minutes, so you won't see broken links.
Can external users see pinned resources? Yes, [external users](https://claude.ai/workspaces/external-users) who are participants in the conversation can see and interact with the resource sidebar just like internal workspace members.
Is there a limit to how many things I can pin? There's no hard limit, but we recommend keeping your sidebar focused. If you find yourself pinning 15+ items, consider whether all of them are truly necessary for quick access.
*** **Related guides:** * [Threads](/conversations/threads) - Learn more about organizing discussions * [Group chat](/conversations/group-chat) - Using the resource sidebar in group conversations * [Direct messages](/conversations/direct-messages) - Managing resources in DMs # Why use the resource sidebar? The sidebar serves two purposes: it automatically surfaces resources shared in the conversation, and it lets you pin the most important ones for easy access. **Automatic tracking:** As your team shares links, threads, images, and videos in conversation, they appear in the "Recent" sections of the sidebar. No manual work required—just look right and you'll see what's been shared. **Strategic pinning:** When certain resources become essential to the conversation, pin them to keep them at the top. Pinned items stay visible even as new resources are shared, making it easy to access key context. \[Screenshot placeholder: Resource sidebar showing three sections - Pinned resources at top, Recent Links in middle, Recent Media grid at bottom] #### **Common use cases:** * **Project coordination** - Link a kickoff thread to all status update threads * **Issue tracking** - Connect a bug fix discussion to the original report and related investigations * **Planning cycles** - Relate Q1 planning to specific department goal threads * **Decision trails** - Link follow-up discussions back to the original decision thread * **Document access** - Keep relevant files and links handy for reference # How to use the Resource Sidebar ## Common scenarios #### Connecting a series of discussions When one conversation leads to another, create a clear trail: 1. Bug discovered in "Production Issues" thread 2. Create "Bug Investigation: Checkout Flow" thread → pin original issue 3. Create "Fix Deployed: Checkout Bug" thread → pin investigation thread 4. Anyone following along can trace the full story #### Managing project work For ongoing projects, link all related threads: 1. Start with "Project Phoenix Kickoff" thread 2. Create weekly update threads → pin kickoff in each 3. Create decision threads → pin kickoff and relevant updates 4. Everyone has quick access to the full project context #### Sharing important files Keep frequently referenced documents accessible: * Pin design specs in implementation threads * Pin meeting notes in follow-up discussion threads * Pin relevant documentation in troubleshooting threads *** ## Frequently asked questions **Who sees pinned resources?** All members of the conversation see the same pinned items in the sidebar. When you pin something, you're making it accessible to everyone in that thread, group chat, or DM. **Can I pin the same thread in multiple places?** Yes! A single thread can be pinned to as many other conversations as you need. This is useful when a key discussion relates to multiple projects or topics. **What happens if someone deletes a pinned thread?** The pin is automatically removed from all sidebars where it appeared. The reference gets cleaned up within a few minutes, so you won't see broken links. **Can external users see pinned resources?** Yes, [external users](https://claude.ai/workspaces/external-users) who are participants in the conversation can see and interact with the resource sidebar just like internal workspace members. **Is there a limit to how many things I can pin?** There's no hard limit, but we recommend keeping your sidebar focused. If you find yourself pinning 15+ items, consider whether all of them are truly necessary for quick access. # Threads Organize conversations into Threads ## What is a Thread? Threads are the core component of communication in Glue. Threads contain multiple messages on a topic between any combination of people or groups of people. Threads provide a structured, yet flexible way to keep conversations on track and bring them to a resolution.
{% tabs %} {% tab title="Thread Features" %} **Named, standalone conversations** Threads are not locked into a specific group (or channel like in other chat apps), but are their own separate unit of conversation. Each thread has a name, making it easy to find and reference. **Multi-addressable** You can include multiple users and groups in a single thread, and add new participants over time. This reduces noise because you do not have to join or create a group just to send one message. **Choose what's in your inbox** You can choose to add and remove threads from your inbox to control what notifies you. Your [important threads](/inbox/inbox#what-makes-a-thread-important) always show up in your inbox. **Automatic app events** When you share a link to a supported app — like a [Linear](/integrations/linear) issue or a [GitHub](/integrations/github) pull request — the thread automatically subscribes to updates. Status changes are posted as system messages, keeping everyone in the thread informed without any extra setup. {% endtab %} {% tab title="Thread Benefits" %} **Organized and results oriented** Topic-focused conversations keep people focused and bring the conversation to a resolution faster. And when it's resolved, you can archive it! **Flexible for when the conversation evolves** * [Fork off a new thread](/conversations/threads/create-a-thread-from-an-existing-message) if a new topic comes up in the conversation. * Edit the name of the thread over time. * Add or remove people or groups as needed. * Archive it when it's done! **Less noise** The clutter of channel based chat apps can really add cognitive load and stress over time. Our threads-first model allows you to have a more streamlined experience — focus on what's important and catch up on the rest at a time that's convenient to you. {% endtab %} {% endtabs %} # Creating new Threads How to start Threads There are multiple ways to create a new thread so you can easily start a conversation wherever you are in Glue.
Pencil icon Hit the pencil icon in the upper lefthand corner of the app to open a new thread draft to send to any combination of people and groups.
In the message composer In the message composer in a group, DM, or thread you can click on the Thread tab (next to reply) to switch from drafting a message to starting a new thread. Glue will suggest a thread name while you are typing, or you can make it your own.
{% hint style="info" %} If you forget to make your message a thread before you send it, don't worry! You can [create a thread off any sent message](#convert-messages-to-threads) after the fact. {% endhint %} ### Thread components There are three main components to a thread to send your first thread message. You can fill these out in any order, but this is a helpful way to get started. {% stepper %} {% step %} **Thread message body** You'll automatically be put into the message editor when you create a new thread. Start typing right away to get a draft going. The thread will automatically update the thread name based on what you are writing. {% endstep %} {% step %} **Members (notify in inbox)** Add the people and groups you want to be notified of the thread in their inbox. You need at least one other member on the thread to be able to send it. {% endstep %} {% step %} **Thread Visibility** All new threads are public to your workspace by default. This means that other members of your workspace can see the thread in their threads feed and search. You can change this to be private only to the people and groups who are members on the thread. {% endstep %} {% step %} **Thread name** Glue will generate a thread name for you, but you can always write it yourself first or edit the suggested name after. Thread names can be updated after they are sent as well — change the name if the topic evolves or update with things like a project status. {% endstep %} {% endstepper %} {% hint style="success" %} **Pro tip:** Start typing out your message first to let Glue generate a thread name for you as a starting point. When you're done writing, modify the thread name to make sure it fits your message topic and purpose. {% endhint %} ### Adding members to threads * **By Name**: Click "notify in inbox" and type the user’s name. * **@Mention**: Mention them in a message and select "Add to thread." * **By Email**: Enter their email address directly in the recipient field. * **External Participants**: Invite users from outside Glue using their email address without needing to add them to your workspace or group. Note: This does not grant them access to your workspace or any other Glue information. # Create a thread from an existing message Adapt to evolving conversations In Glue, you can turn any message into a thread after it’s been sent. This is perfect for organizing the conversation if a message turns into a longer discussion, bringing new people or groups into a conversation, or maintaining focus by forking separate topics out of an existing thread.
#### Any Message in Glue can be turned into a Thread at any time: * Group chat messages * Direct messages (DMs) * Messages in an existing thread #### How It Works: * The original message remains visible in the group chat, DM or thread, with a link to the new thread appearing below it. * The new thread is given an auto-generated name, which you can update anytime to match the topic. * The new thread will automatically include the same recipients - groups or people who the original message was addressed to. You can easily edit the recipients while you're creating the new thread to add or remove groups or people to keep the conversation relevant. * The new thread will show the original message at the top as context, as well as where the message was originally shared. A blue arrow icon indicates that this is a forked thread created from a message.

This is a group chat message that was turned into a thread

New thread has context of original message and where it was sent

{% hint style="info" %} Note that if you create a new thread from a message in an existing thread that the thread will not appear in someone's inbox unless you @mention them, add them directly as a recipient to the new thread or if they have their group notification settings set to be notified of all threads in the group. If someone replied to the prior thread, they will not automatically be notified of the new thread {% endhint %} #### Benefits of Turning Messages into Threads: * **Stay Organized:** Keep conversations on track by separating off-topic or evolving discussions. * **Improve Focus:** Shift deeper discussions into their own space without cluttering the original chat. * **Customize Participation:** Add or remove participants in the thread to ensure the right people are involved. # Public threads launch **Public Threads** are a new way to share information across your workspace without everyone needing to join every group. *** ### How it works Previously, all threads were private to the members on the thread (people and groups). Now, you can **make any thread publicly visible** **to everyone in your workspace.** Public threads are visible in the new threads feed. This means your team can stay informed on what's happening across the organization without being added to every group — and group membership can go back to meaning something: the people who actually need every thread in their inbox.

The new threads feed shows you all public threads and threads in your inbox

A few things to know: * **New threads default to public** (workspace-visible), but you can toggle them to private while drafting. * **The threads feed lets you see all the threads in your inbox plus all public threads in your workspace.** You can filter by group and change your view layout. * **Groups work best as distribution lists:** members should be people who want every group thread in their inbox. Everyone else can follow along in the threads feed. Newly created groups will default to adding every thread to a group member’s inbox. * **Existing threads and groups are** **not affected automatically**. All of your existing threads remain private — that's why you'll notice a lock icon on threads in your inbox now. You can edit the public/private visibility in thread details. Your groups will retain their group notification settings. *** ### What's changed in your inbox The top section of your inbox has been simplified. You'll now see: * A **threads feed** showing all public threads across your workspace that can be filtered by group. * A **lock icon** on any thread that's still private. Public threads will show the standard thread icon. * A consolidated **Directory** view for people, groups and apps
*** ### Recommended actions to see the benefit Here are two things worth doing to make the most of Public Threads: #### 1. Make key threads public Thread owners and admins can change a thread's visibility at any time. **To make a thread public to your workspace:** 1. Open the thread 2. Go to Thread details (either by clicking on the thread name or the ellipsis) 3. Under Visibility, switch from Private to Public
#### 2. Clean up group membership If someone doesn't need every thread from a group in their inbox, they don't need to be a member anymore — they'll still see public threads in the feed. **To remove members from a group:** 1. Open the group — either from the new directory or group chat 2. Open group details — click on the group details button from the directory or click on the name of the group from the chat 3. Go to Members 4. Remove anyone who doesn't need all group threads in their inbox *** ### FAQ **Will my existing threads automatically become public?** No. All existing threads stay private unless you manually change them. You're in control. **What does the lock icon on my thread mean?** It means a thread is private — only thread recipients can see it. You'll now see this on all your existing threads until you start making threads public. **Can I make a thread private after it's been public?** Yes. Thread owners and admins can toggle visibility in thread settings at any time. **What happens to my group notification settings?** Your existing groups will keep their current group notification settings (the default used to be "important only"). New groups will default to "everything" for notifications — all threads will be added to your inbox. # Managing Threads ## Organizing and Editing Threads There are lots of ways to keep your threads organized as your conversations evolve! Here are some of the things you can do to update your Threads over time.
Editing thread name, visibility, members and messages You can **modify the** **thread name** and **members** at any time, allowing for flexibility as discussions evolve. You can also **edit a message** you sent in the thread after you've sent it. **To edit the thread name, visibility or members,** open the thread and either click on the Thread name at the top, or click on the ellipsis in the upper right hand corner and select **"Thread Details."** **Anyone on the thread can add members (groups or users). Only the starter or an admin can** [**remove members**](#removing-users-from-a-thread)**.**
Forking off-topic messages into a new Thread Messages in an existing thread can be [forked into a new thread](/conversations/threads/create-a-thread-from-an-existing-message) when a new topic arises, helping to keep discussions organized and relevant.
Pinning Messages in a Thread Any user in a thread can pin a message for the entire thread. Click the ellipsis next to the message you want to pin to find the drop down menu and pin (or unpin) the message. If there are one or more pinned messages on a thread, a pin icon will show up at the top and you can see the entire list of pinned messages. This makes it easy to save important messages for everyone on the thread to refer back to later. Pinned messages will also show up highlighted in the thread chat stream so you can easily spot important messages and who pinned it. All pinned messages now show up in the sidebar of a thread.
Close the Thread When the conversation is complete, you can mark the thread as closed for everyone. This will send a system message and show the thread name with a strikethrough in your inbox. Anyone can still reopen the thread again if the topic resumes.
## Thread Level Actions There are a lot of actions you can take at the Thread level to manage your threads and thread inbox. Most Thread actions can be taken either from your Thread inbox view or from the Thread menu when you have the Thread open. When the thread is open you can click the ellipsis in the upper right hand corner to pull up the menu.
### Thread Actions to manage your Thread inbox See [more information about your Thread inbox here](/inbox/inbox#threads-in-your-inbox). You can take these actions from the Thread menu or in your Thread inbox view.
Archive ✔️ Archiving a thread marks it done and moves it from your inbox to Archived. The thread will reappear in the inbox if there is a new message sent to the thread. You can always access archived threads by clicking the ellipsis next to Threads and choosing the **See all** option and navigate to the **Archived tab**. To move an archived thread back to your inbox, navigate to the Archived section of your inbox (see above) and simply click the inbox icon to move it back to the inbox. You can also multi-select multiple threads at once to move them to your inbox.
Mute and hide from inbox 🔔 Muting a thread will hide it from your inbox and mute notifications about that thread. You will still have access to the thread and can find it in the Threads feed, in your Groups tab, and through Search. After you've muted a thread, if another user @mentions you or a group you belong to in the thread, it will appear in your inbox again. You can also manually add the thread back to your inbox.
Mark read / unread ✉️ Mark threads read or unread in your inbox depending on their status. Marking a thread unread will make the thread name bold in your inbox and return it to the top of your inbox if your Inbox is sorted by Unread.
Set a Reminder ⏰ If you're not ready to take action on a thread, but still want to keep your inbox clean, you can set a reminder on a thread for a specific time in the future. Setting a reminder on a thread temporarily archives the thread from your inbox and has it reappear in your inbox at the selected time and date of your choosing. ![](/files/YNFcZwo3ijPqH6XGBF2Z)
Star ⭐️ Starring a thread moves it to a special Starred section of the inbox. Starred threads will remain pinned to this section. If there are no starred threads, the Starred section of the inbox is hidden.
### Other Thread Actions * **Summarize Thread** - Glue AI will summarize the messages in the Thread and share a summary that's only visible to you. If you need to catch up on a Thread but don't need everyone else to see the summary, this is a great option! * **Copy Share Link** - Get a link to the thread that you can share elsewhere. Keep in mind that only people who are on the Thread or in a group on the thread will be able to see the Thread when they click on the link. Remember you can also @ mention the name of a thread within Glue for even easier sharing. ## Removing members from a Thread **Only the thread starter and admins (group or workspace admins on the thread) can remove other users or groups from a thread.** The thread starter cannot be removed from the thread. 1. Click into the thread name or thread details 2. Search for or find the user or group 3. Click the X button next to their name 4. Confirm that you want to remove their access to the thread # Advanced thread settings Thread starters and admins can manage permissions, delete, and get the thread's ID Thread starters and admins can access a few things under the advanced menu in Thread details. * Thread permissions * Delete thread * Thread ID - you might need this for help troubleshooting with Glue Support or for targeting a thread with a webhook #### To get to the advanced menu: * Open the thread's detail view by either clicking on the name of the thread when it's open. * Or click the ellipsis on the right hand side and choose thread details. * The advanced menu is at the bottom and needs to be expanded to see the options.
## What are Thread Permissions? Thread permissions let thread starters (the person who created the thread) and admins control who can access and respond to specific threads. Other recipients cannot change these permissions. * Locking changes to the thread details * Prevents new users or groups from being added to the thread * Prevents the thread name from being change * Turning off thread replies to make threads read-only ### How to Modify Thread Permissions Only the thread starter or admins can control thread permissions. * **For new threads:** Set permissions before sending the thread by clicking the ellipsis at the bottom next to thread visibility. * **For existing threads:** Change permissions anytime in the thread details modal by clicking on the advanced section and clicking the thread permissions dropdown. {% hint style="info" %} The **thread permissions drop down is multi-select.** You can choose to lock recipients, turn off thread replies, or both on the same thread. {% endhint %}

Changing thread permissions on a new thread draft

### Thread Permission Options #### Locking a thread Thread starters, group admins, or workspace admins can lock a thread to prevent changes to the thread recipients and name. When a thread is locked: * Only the thread starter and admins can add new recipients or change the thread name. * All other thread recipients can request to add users or groups to the thread, and the thread starter can approve or decline these requests.

Thread recipients can request to add someone to the locked thread

Thread starters will receive a request they can approve or decline

{% hint style="info" %} **Note:** Even if a thread is unlocked, only a thread starter can remove users or groups from a thread. {% endhint %} #### Turning off replies on a thread Thread starters, group admins, or workspace admins can turn off replies for a thread. When replies are turned off: * Only the thread starter and admins can reply or change the thread name. * All other thread recipients can read, react, and share the thread link. {% hint style="info" %} This feature is useful for announcements to a large audience, reducing notification noise. {% endhint %} ### What does a thread look like when replies are turned off? #### Profile Badges When a thread has replies turned off, you’ll see a role badge next to the profile picture for thread starters and admins, both in thread replies and in the thread member list. That way you can easily see who has access to the thread’s permissions. #### Message Editor * **For thread starters or admins:** A banner above the message editor shows that replies are turned off, but you can still reply based on your role. * **For recipients:** The message editor is hidden, and a banner at the bottom states that replies are turned off.

View of a thread with replies turned off as a recipient

View of a thread with replies turned off as an admin (thread starter's view will look similar)

# Group chat The place for quick questions and 🔥 memes ### How Group Chats Work Group chat messages in Glue are private, meaning only members of the group can view and participate. Threads sent to the group can be public, depending on visibility settings. * **Asking Questions or Sharing Problems**: Sending messages to a group chat isn't stressful when you can [turn any message into a new thread](https://www.notion.so/o/XsufMgnMdGDV6LnvD5HN/s/5yStw8wuIeWBdGOh81bd/~/changes/54/conversations/reply-in-new-thread) if needed to keep it organized! * **Inbox Notifications**: Groups with new messages in their group chats will appear in the Groups section of your Inbox with the name bolded, or a red badge if you're @ mentioned. Groups that have been active within the last week will stay in the Groups section of your Inbox. * **Accessing Inactive Group Chats**: If a group chat hasn't been active recently, you can find the group in the **Directory**. Send a message, and it will reappear in your Inbox sidebar as a recent chat. * See the stream of all chats and threads in one place.

Group chats let you have casual conversations and threaded conversations in the same place

# Direct messages Private message another user Direct Messages (DMs) are private conversations between you and one other user. They can include chats and threads. ### **Where to find and view DMs** * Recent DMs will appear in the Direct mesasges section at the bottom of your inbox * Type their name in the [Search bar](https://docs.glue.ai/inbox/search) * Click the **ellipsis** next to the Direct messages section and click **See all DMs** * Go to the **Directory** > People > click the person's profile and click message {% hint style="info" %} DMs will appear in your inbox unless you archive them. If a new message comes in after you after, it will reappear in your inbox. {% endhint %} ### Starting a New DM There are a couple ways to start a new DM. * **Start a thread** — **click the pencil icon** at the top of the app and address it to the specific person * Hover over **Direct messages and click the plus (+)** icon * Click the ellipsis next to Direct messages and choose “New direct message” * Go to the **Directory** > People > click the person's profile and click message
{% hint style="info" %} 💡 **Tip:** You can create 1:1 threads within DMs to keep conversations organized! {% endhint %} You can start a DM with anyone, even if they’re not on Glue yet. All you need is the person's email address to send an invite to Glue. The recipient can choose to accept or decline the invitation. # "Find in" conversation Use **Find in Conversation** to quickly locate keywords or phrases inside the conversation you already have open. This works in: * Threads * Group chats * Direct messages (DMs) **You can open Find in Conversation with:** * **Mac:** `CMD + F` * **Windows:** `CTRL + F`
{% hint style="info" %} This is useful when you already know which conversation contains the information you need and want a faster way to scan messages. {% endhint %} ### How Find in Conversation Works When you enter a keyword or phrase: * Glue searches messages in the currently open conversation only. * Results are not currently exact match only. Partial matches are also included. * The total number of matches appears in the "find" bar and you can arrow up/down to see more results. * The keyword and message containing it are highlighted in the conversation view. ### Navigate Between Matches Use the arrow buttons in the Find in Conversation bar to move between matching messages. * **Up arrow:** Go to the previous match * **Down arrow:** Go to the next match Glue automatically scrolls to each matching message as you move through results. ### When to Use Find in Conversation vs Search | Use Case | Recommended Tool | | ------------------------------------------------------------ | ------------------------ | | Find a keyword inside the conversation you already have open | Find in Conversation | | Search across multiple chats, channels, or people | Global Search or Glue AI | | Quickly jump between repeated mentions in one thread | Find in Conversation | | Discover where a topic was discussed | Global Search or Glue AI | # Groups overview Organize people into groups around teams, projects, or topics in your Glue workspace. ## What is a Group? Groups are a collection of people in your workspace that organize people by team, department, or project, **allowing you to** **send threads to specific audiences**. Groups can be thought of as the improved replacement to a channel. Groups still accomplish the goal of reaching a specific audience of people, but since threads are not specifically locked into group, you do not need to create groups for every specific combination of people. Overall, there should be far fewer groups compared to channels in a channel-based chat system. #### Recommended use cases for groups * **Departments:** We recommend that admins set up a group for each department * **Teams:** Teams can create their own groups as needed * **Projects:** For a multi-quarter project, a group might be helpful, but shorter term projects can be discussed in a thread addressed to the relevant groups and individuals. {% hint style="success" %} Since one thread can be sent to multiple groups and individuals simultaneously, there’s no need to create overly specific groups for every situation. {% endhint %} ## Ways to interact with a Group ### **Private Group Chat** Every group has a [private chat](https://docs.glue.ai/conversations/group-chat) that can be used for quick questions or casual conversations that don't require a thread. You can always turn any message into a new thread after the fact. ### **Threads for Groups** Users can start threads with one or more groups to keep the right people in the loop and keep your conversations organized. The thread will show up in the Groups’ chat and thread list for each Group. ## Group Features Each group has its own hub to interact with the other group members, catch up on current discussions and manage group settings. * **Chat:** The private group chat stream containing individual messages as well as threads * **Threads:** List view of all threads shared in a group — with thread names and a preview to quickly scan for a relevant thread * **Resources:** View of files, media and links shared in the group {% hint style="info" %} Remember, a thread can include multiple recipient groups, so if you belong to several groups added to a thread, you'll see that thread in each group's thread list. {% endhint %} ## Accessing and creating Groups ### Accessing groups you belong to You can access the groups you belong to in two main ways: through your **Inbox** or the **Directory** in the Groups section. ### Creating a new group You can also **create groups in these same spaces.**
Group Creation Flow Here's what you can do when you create a new group: * Choose a group name and emoji * Add workspace members or external guests to the group * Make other members an admin of the group (the group creator is automatically made an admin of the group) * Choose [group access settings](#group-access-settings) - open or ask to join (approval required)
{% hint style="info" %} Anyone in the workspace can create a group. We recommend being thoughtful before creating a new group though. Review which groups exist and consider if a thread will work instead for a short term conversation. {% endhint %} {% tabs %} {% tab title="Groups in your Inbox" %} Recently active (within the last week) and starred groups from any workspace you belong to appear in your **Inbox**. When there are unread messages in a group, the group name will be bolded. If a thread in a group is an [important thread](/inbox/inbox#what-makes-a-thread-important) to you, it will also show up in your thread inbox. To create a new group from the Inbox, click on the Groups header and select the option from the dropdown.
Starred and Recently Active Groups show up in the Inbox
{% hint style="info" %} If you want a Group to always appear in your inbox, you can **Star ⭐️** it to keep it in the "Starred" section of your inbox. {% endhint %} {% endtab %} {% tab title="Groups Tab" %} In the **Groups** tab, you’ll find all the groups you belong to per workspace. If you belong to multiple workspaces or external groups, you will see them all listed here. You can also access your Workspace's [Group Directory](broken://pages/MDoe7byeNtQ9q8sr2KsC). To create a new group, either click "Add groups" at the bottom of your group list or select "Create group" by clicking the workspace name at the top.
See all Groups in your Workspaces and External Groups
Create a Group from clicking on the Workspace name or "+ Add groups"
{% endtab %} {% endtabs %} ### Browse all the groups in your workspace You can see all the groups in your workspace by accessing the groups section of the [Directory](/navigating-the-app/directory#groups). You can browse all group names and view all public threads for a group without joining it. If you need to see all threads and chats, you will need to join the group. A group might be open to join right away, or require you to request access first if it's a closed group. See [group access settings](#group-access-settings) for more details. ## Leaving a group #### For users who want to leave a group 1. Open the group in your app. 2. You can leave the group in two ways: 1. Click the ellipsis icon on the right hand side and open the group menu. The last option is to "leave group." 2. Click on the name of the group at the top, and go to the Settings tab. Select "Leave Group." 3. A pop up will come up asking you to confirm that you want to leave the group. Select "Leave group" again.

Click the ellipsis and find the "leave group" option

Alternatively, click the name of the group and go to the settings tab.

#### For admins who want to leave a group 1. Open the group in your app. 2. Click on the name of the group at the top, or click the ellipsis and select "Group settings." Either way will open the group menu. 3. Navigate to the Settings tab (if opened from clicking on the group name). 4. Scroll to the bottom and select "Leave group." 5. A pop up will come up asking you to confirm that you want to leave the group. Select "Leave group" again.

Leave the group from the Group Settings menu.

# Group settings Learn what settings you can manage for a group based on your role ## Managing Group Settings Each group's settings can be managed individually. What settings you have access to depend on your [role in the group](#role-based-group-settings-permissions) (admin vs member). To open the **Group Settings** details, simply click the **Group name** at the top of the screen when the Group is open in your app. This will open a modal with options to view **members**, **notifications**, and— if you're an admin— **apps** and **settings** for that Group. Alternatively, you can click the **ellipsis (⋯)** in the upper-right corner of the screen. This opens a dropdown menu with the same options mentioned above, and clicking on them will open the modal.

Admin view of Group Settings modal

Non-admin view of Group Settings modal

## Role-based group settings permissions What you can modify depends on whether or not you are an admin who is a member of the group (either group admin or a workspace admin), or a group member. | Permission | Workspace Admins | Admins in the Group | Group Members | | --------------------------------------------------------------------------------------------------------------------------------- | ---------------- | ------------------- | ------------- | | Update the group description | ✅ | ✅ | ✅ | | Update the group name and emoji | ✅ | ✅ | ✅ | | Change the workspace the group belongs to | ✅ | ✅ | | | Change [**group access**](/groups/group-settings/admin-settings-for-groups#group-access) (open vs closed) | ✅ | ✅ | | | Manage [**who can reply**](/groups/group-settings/admin-settings-for-groups#group-replies) in the group (everyone vs admins only) | ✅ | ✅ | | | See and search for group members | ✅ | ✅ | ✅ | | Add and remove group members | ✅ | ✅ | | | Edit role permissions for group members | ✅ | ✅ | | | Manage app integrations | ✅ | ✅ | | | Adjust your individual [**notification settings** for that group](/groups/group-settings/group-notification-settings) | ✅ | ✅ | ✅ | | Leave the group | ✅ | ✅ | ✅ | | Archive the group for everyone | ✅ | ✅ | | | Delete the group | ✅ | ✅ | | Find more information on the following pages: {% content-ref url="/pages/ry56thjHnTK6z9lvqxZy" %} [Admin settings for groups](/groups/group-settings/admin-settings-for-groups) {% endcontent-ref %} {% content-ref url="/pages/2wwNAErxwsqv6qHPmZ4S" %} [Group notification settings](/groups/group-settings/group-notification-settings) {% endcontent-ref %} # Admin settings for groups Important group admin settings to understand Some of the most important group settings that a group admin or workspace admin who belongs to the group can control revolve around who can join a group, who can reply in a group, and archiving the group. Workspace admins can manage any group in the workspace, even if they are not a member of that group. ## Group Access Group or workspace admins can **control who in your workspace can join a group** (open vs closed group). Group content is currently not visible to a user until they join the group, even if the group is open.
Open Group Anyone in your workspace can find and join the group.
Closed Group Anyone in your workspace can find the group, but must request access and be approved by an admin (of the group or workspace).
## Group Replies By default, anyone in a group can send chats and start threads. However, group and workspace admins can turn off replies in group chats to **make a group read-only**, restricting posts to admins only. ### When to Use Read-only groups work best in large companies that might need to make a group just to push announcements, and reduce the notification noise of everyone replying. Most groups should remain open for conversation. Use this setting sparingly to keep communication dynamic.
### Turn off replies in any Group Workspace and group admins can control who can reply in a group: * Go to Group Settings > Group Chat. * Change reply permissions from “Everyone” to “Only admins.”

Group Settings menu to turn off Group Chat replies

{% hint style="info" %} Group members who are not admins will not see these Group chat settings in the settings menu. There are other [visual indicators](#visual-indicators) that will let them if know replies are turned off. {% endhint %} ### Turn off replies in the General Group The General group includes all workspace members automatically. Anyone can post messages here, making it ideal for company-wide updates or discussions. Workspace admins can control who can reply in the General group to make it read-only: * Go to Workspace Settings > General Group Chat. * Change reply permissions from “Everyone” to “Only admins.” {% hint style="info" %} Most companies should leave the General group open for communication, but for large companies that want to reduce notification noise, you can make the General group an announcement-only forum. {% endhint %}

Workspace Settings menu to turn off General Group Chat replies

### What Happens When Group Replies Are Turned Off? #### When a group is made read-only: * Only admins can send chats or threads to that group. * All other group members can still read, react, and share message links. ### Visual Indicators #### Admin Badges When a group has replies turned off, admins will have a role badge appear next to their profile picture both in messages and in the group member list. That way you can easily see who has admin privileges in the group. #### Message Editor * **Admins:** A banner above the message editor reminds you replies are off, but you can still post based on your role. * **Other members:** The message editor is hidden with a banner explaining replies are turned off.

Non-admin view when Group chat replies are turned off

## Removing users from a Group **Only admins (workspace and group admins) can remove users from a group** after they've been added. 1. Go to the group members list (via group settings or clicking on the group name) 2. Search for or find the user you need to remove 3. Click the dropdown arrow that lists them as an admin or member 4. Select "Remove User" 5. Confirm removing the user.
## Archiving or deleting the Group for everyone ### Archiving the group Group admins and workspace admins who belong to a group can archive the group for all members of the group. This keeps your groups view free of the clutter, but allows you to still search and reference the contents of the group. #### Archiving a group will: * Prevent new threads or chat messages from being sent to the group. The message composer will be hidden in the group and a banner will be displayed in its place that says the group has been archived. * Remove the group from the Groups tab for all members of the workspace. * Move the group to an "Archived" section in the [Group Directory](broken://pages/MDoe7byeNtQ9q8sr2KsC). * Display an icon next to the name of the group to show it's been archived. The icon looks like a storage bin. * Allow you to unarchive the group at any time.

Group Directory view of Archived groups

#### How to archive a group * Go to Groups Settings. * Scroll down to the bottom to find "Archive for everyone" and select that. * A pop up will come up confirming if you want to archive the group. Select "Archive group."
{% hint style="info" %} Try to set a cadence for regularly archiving old groups to keep the workspace organized. {% endhint %} ### Deleting the group Group admins and workspace admins who belong to a group can permanently delete the group from the workspace. If you know you no longer need to use or reference the contents of the group, you can delete it. All members of the group will immediately lose access to the thread and message history from the group. This action cannot be undone and the group cannot be restored. #### How to delete a group * Go to Groups Settings. * Scroll down to the bottom to find "Advanced Settings" and click to expand the menu. * Click on "Delete group." * A pop up will come up confirming if you want to delete the group. You will need to type in DELETE to confirm and then click the "Delete group" button.
# Group notification settings Focus on the conversations that matter to you ## **Customizable Notifications** * Glue allows you to control which conversations you want to be notified about in your Threads Inbox. * Decide whether to follow every thread in a group or only Important ones. #### 📌 A thread is considered Important (to show up in your Threads Inbox) when: * You are @mentioned. * You reply to the thread. * You choose to follow the thread. {% hint style="info" %} When joining a new group, the **default is to follow Important threads only** for that group. You can change this setting to follow every thread at any time. {% endhint %} ## **Managing Group notification settings** * **Click the 🔔 icon** at the top right of the group header to adjust your notification settings for that group. * To follow all threads from a group, change your setting to **Everything** in your Inbox. This setting is typically used for groups you are very active in. * **Note:** You cannot change the notification settings for your company’s General group
{% hint style="info" %} If you follow only Important threads from a Group, you will still see all new threads in your Feed and Activity tab, and in the Group view. You just won't follow all threads in your Thread Inbox. {% endhint %} ### **Managing notifications for individual Threads in a Group** * **Following a thread** means it will appear in your Inbox and notify you of new messages. * You can override your group settings by following or unfollowing individual thread notifications. * Click the bell 🔔 icon on an open thread, or from your Inbox when you hover over the thread name to **Follow** or **Unfollow**
{% hint style="info" %} You can also customize when to receive [push notifications](https://docs.glue.ai/account-setup/notifications) about the items in your inbox. {% endhint %} # Inbox One inbox, one place to check ✅ ## What's in your Inbox? Every Glue user's inbox is personalized to them and includes: * Important threads * Recently active groups * Recently active direct messages Every user only has one Inbox, even if you belong to multiple workspaces. ### What makes a thread "important" to you? * Mentioned directly in a thread message - you or the group @ mentioned * Replied to the thread * Started the thread * Selected to add the thread to your inbox Only your important threads show up in your inbox. If you want to see a thread in your inbox that doesn't meet this criteria, you should add the thread to your inbox. {% hint style="info" %} If you would like to automatically see all threads from a particular group in your inbox, you can update the [group notification settings](/groups/group-settings/group-notification-settings). {% endhint %} ## Threads in your Inbox Your important threads show up at the top of your inbox so you can keep track of active conversations. You have full control over which threads appear in your inbox and how you organize it. ### Thread Inbox basics
Sort Threads by recent or unread Users can choose to view their inbox chronologically (by last message sent) or with unread messages appearing first. The default is set to "Recent first." You can switch this view at any time by clicking the ellipsis next to Threads at the top of your inbox, and choosing which sort option you'd like.
See all Threads To see all of your threads in one view, click the ellipsis next to Threads and choose the **See all** option. Here your can toggle between the Threads you are currently following in your Inbox, Archived Threads, Sent Threads and All. This view makes it easy to take bulk actions on multiple, or find a thread you might have accidentally archived. ![](/files/Za2cgDH2eaprWIOHU7qU)
### Thread Inbox actions Users can take the following actions on any thread in their inbox to stay focused and informed. These thread actions only affect your inbox — e.g. archiving a thread will not archive it for everyone on the thread, it will only archive from your inbox. All of these actions can be taken by hovering over the thread name in the Inbox side bar. On the righthand side a check mark will appear next to the thread name, hover over that to see the full thread action menu. If you hover to the left side of the thread name, near the thread icon, a checkbox will appear that lets you select multiple threads.
Archive ✔️ Archiving a thread marks it done and moves it from your inbox to Archived. The thread will reappear in the inbox if there is a new message sent to the thread. You can always access archived threads by clicking the ellipsis next to Threads and choosing the **See all** option and navigate to the **Archived tab**. To move an archived thread back to your inbox, navigate to the Archived section of your inbox (see above) and simply click the inbox icon to move it back to the inbox. You can also multi-select multiple threads at once to move them to your inbox.
Mute and hide from inbox 🔔 Muting a thread will hide it from your inbox and mute notifications about that thread. You will still have access to the thread and can find it in the Threads feed, in your Groups tab, and through Search. After you've muted a thread, if another user @mentions you or a group you belong to in the thread, it will appear in your inbox again. You can also manually add the thread back to your inbox.
Mark read / unread ✉️ Mark threads read or unread in your inbox depending on their status. Marking a thread unread will make the thread name bold in your inbox and return it to the top of your inbox if your Inbox is sorted by Unread.
Set a Reminder ⏰ If you're not ready to take action on a thread, but still want to keep your inbox clean, you can set a reminder on a thread for a specific time in the future. Setting a reminder on a thread temporarily archives the thread from your inbox and has it reappear in your inbox at the selected time and date of your choosing. ![](/files/YNFcZwo3ijPqH6XGBF2Z)
Star ⭐️ Starring a thread moves it to a special Starred section of the inbox. Starred threads will remain pinned to this section. If there are no starred threads, the Starred section of the inbox is hidden.
Select all / multiple threads at once for actions You can take bulk actions on your threads by multi-selecting or selecting all threads. If you hover over the thread icon to the left of the thread name in the inbox, a checkbox will appear. Once you click the checkbox, a new menu will pop up that lets you select multiple threads, or select all at once. Once you've checked the boxes on the threads you want to take action on, you can choose the thread action you want to take — Archiving, Marking read/ unread, Unfollowing, or Starring.
Removing a thread from your inbox (by archiving, muting or setting a reminder) is not the same as deleting a thread. These actions only remove the thread from your inbox. The thread still exists in Glue and can be accessed if you need it. You can still find that thread in any group it was sent to, via search, or by going to "See all" threads in your inbox. And the thread will reappear in your inbox if a new message is sent and the thread fits the "important to you" criteria. {% hint style="info" %} Some people like to archive threads out of their inbox as they address them to reach "inbox zero," and others prefer to keep all their threads in the inbox. You can customize your inbox to your way of working! {% endhint %} ## Other Inbox actions Some inbox actions **can** **also be used on Groups and DMs**. This functionality works in the same way that it does on a thread. * [Star](#star) * [Mark read / unread](#mark-read-unread) # Bulk actions Any of the [inbox actions](/inbox/inbox) can be taken on multiple threads at once by clicking on the avatar of a thread to pull up the bulk action menu. The icon next to each thread name in the inbox will turn into a check box to select — select individual threads, or choose to select all at once. Click "Select All" to select and take action on all items in the inbox - including marking read, archiving, muting and starring.
# Search The information you need at your fingertips Users can search for messages, threads, groups, or people in the search bar at the top of the app. Click into a result to pull up the search result thread list and view each relevant thread, and exit the search results when done. Threads and groups in Glue make search faster and easier, getting you to the right conversation you're looking for. ## Scoped Search You can search specifically within the context of a thread, group chat, or DM to narrow the context window of your search. ### Starting a scoped search **From an open conversation** * Open a thread, group chat, or DM * Start a search by clicking on the search bar * Select **Search within this conversation** from the filter dropdown **From global search** * Type `@GroupName` or `@ThreadName` or `@PersonName` search term in global search — be sure to include the `@` symbol to scope the search. * Add your search term after the mention. ### What is supported in scoped search * Scoped search currently supports searching within — `in:` — a single thread or chat. We will be releasing additional filtering options in future updates! Contact our support team if you are looking for specific filters. * Scoped search is supported on the **desktop and web**. It is not supported on the mobile app. {% hint style="info" %} If you're looking to do a quick keyword search, you can also use `CMD+F` / `CTRL+F` to ["Find in" conversation](/conversations/find-in-conversation) {% endhint %} # Using Glue AI Leverage AI to supercharge your work ## What is Glue AI? Every user has access to AI tools at their fingertips through **Glue AI**, our AI assistant that leverages the power of LLMs. Send a question to Glue AI to find out the status of a project, see who is the right person to ask about a topic, or get a summary of work done to date. {% hint style="success" %} Glue AI is never trained on your data and only has access to the threads and groups that you as a user have access to. It will not answer any questions with information from threads or groups that the person asking does not have permission to see. {% endhint %} ## How to use Glue AI At mention @Glue AI in any message or thread, and ask a question. It will answer leveraging context from your workspace and the web. Here are the best ways to leverage Glue AI. ## Glue AI tab Glue AI has its own section in the app that consolidates all the private threads you've started with Glue AI in one place. Think of it as your personal scratchpad with Glue AI! Any conversation you have here is private to you. You'll also see suggested prompts at the bottom of the composer with queries that you can ask Glue AI. These include questions about groups, users, or threads as well as prompts to analyze a document, provide feedback, or ask Glue AI questions about how Glue works. Click on any of these prompts to automatically add to the composer.
You can change your LLM model directly from the Glue AI tab by selecting the drop down menu in the mesage editor. The model is set to auto by default. ## Collaborate with Glue AI and your team ### Turn your single-player thread into a multi-player one If you'd like to share your 1:1 conversation with Glue AI with others, you can @ mention the person or group in your next message in the thread and select to add them, or use the Add button at the top of the app. Once a Glue AI thread is shared with others, it will be moved out of the Glue AI tab and into your thread inbox. ### Start a session with Glue AI in an existing thread or chat You can also interact with Glue AI in any existing multi-player thread or chat, with the ability to preview the response before sharing it. Once you share the response, everyone in the thread can view and interact in a multi-player prompting experience that is unique to Glue!
#### Starting the session with Glue AI in the message editor * Type `@Glue AI` or click the sparkle ✨ icon in the message editor (in a thread, group chat, or DM) to start the Glue AI session. * The message editor will switch colors to show you're now in the Glue AI editor, and`@Glue AI` appears at the start of the message > 💡 **Tip:** Delete the `@Glue AI` mention to exit out of the session and return to normal messaging #### **Generating your first response** * Write your message and click **Generate** icon. * Glue AI processes your prompt and starts drafting a response. You can cancel while it's still drafting if you need to go back. * You’ll see your original message displayed above the AI’s response preview. #### **Refining your response in the sidebar** Want to iterate before sharing? You don't have to settle for the first response. * Click **Reply to Glue AI** to continue the conversation * A dedicated session sidebar opens * Go back and forth with the AI to refine your ideas * Take as many turns as you need—there's no rush
{% hint style="warning" %} Right now the multi-turn session option is only available in threads, but will be available in all message types soon. {% endhint %} #### **Sharing with your team** When you're happy with the result: * Click **Share** to publish the exchange to the thread * Glue automatically summarizes your conversation for your team * The session closes and your summary appears in the thread #### **What your team sees:** * A concise summary of your AI session — this is color coded to show it's from Glue AI * Highlighted artifacts like code, documents, or key outputs * Click on the summary to view the full exchange in the sidebar
## Best practices for Glue AI prompting {% hint style="info" %} Give Glue AI as much context as you can in the prompt for more relevant answers * Mention the specific group or thread where the information is found, if you know it * Tell it to search the web if you want it to pull in outside sources * Make your questions specific and detailed {% endhint %} ## Find information about Glue AI's response There's an info icon when you hover over a message reply from Glue AI. This opens an information card that includes the model Glue AI used in it's response, as well as the list of sources. You can also leave feedback from this view.
## Give feedback on Glue AI! Let us know how it's going! If there's anything that is confusing about an answer from Glue AI or it isn't clear how to prompt it, we want to hear your feedback! #### **Feedback on responses from Glue AI** Press the thumbs up 👍 or thumbs down 👎 icon at the bottom of the response from Glue AI. The thumbs down button will open a feedback form to give us more details. We really appreciate any detailed feedback you provide in here to help us make Glue AI better!

Select the thumbs up or thumbs down at the bottom of the response

Glue AI feedback form for bad responses

#### **General feedback on Glue AI** [Contact our support team:](/get-started/help-and-support) Start a new thread with us by going to the Help icon next to your profile picture and clicking **Contact Support.** # Glue AI Settings & Support ## Customize your experience with Glue AI You can set your model preferences and [AI Rules](/profile-and-preferences/ai-rules) (currently in the Labs section of your workspace settings) to customize how Glue AI interacts with you. ### Choose your own model Glue AI is powered by several LLMs - and we're testing new models to support! The models currently supported in Glue are: {% hint style="success" %} Anthropic: * Claude Opus 4.5 * Claude Sonnet 4.5 * Claude Haiku 4.5 {% endhint %} {% hint style="success" %} OpenAI: * GPT-5.2 * GPT-5 mini {% endhint %} {% hint style="success" %} Google: * Gemini 3 Pro * Gemini 3 Flash {% endhint %} {% hint style="success" %} Moonshot: * Kimi K2 (US hosted) {% endhint %} The default setting in Glue is Automatic. With "Auto", Glue AI chooses the best model currently available, and will upgrade as new models become available. You can update the model you use on individual threads in the Glue AI tab. Users can indicate their default preferred model by navigating to their **Preferences** and selecting a particular model:
### Leverage AI Rules to personalize your experience Want Glue AI to remember to use a specific tone or always use a specific formatting in your thread names? You can set these preferences in AI Rules! [Check out our AI Rules page](/profile-and-preferences/ai-rules) to learn more. {% content-ref url="/pages/Art45ZqFbcpV2plIwIt8" %} [Agent Personalization](/profile-and-preferences/ai-rules) {% endcontent-ref %} ## What's supported by Glue AI * Glue AI can search the web using Perplexity. * Glue AI can render tables of data in its responses. * Glue AI can analyze file attachments and uses them as additional context to answer user questions. Here are the file types supported by Glue AI's file search: `.eml, .html, .json, .md, .msg, .rst, .rtf, .txt, .xml, .png, .webp, .jpg, .jpeg, .bmp, .heic, .csv, .doc, .docx, .epub, .odt, .pdf, .ppt, .pptx, .tsv, .xlsx` {% hint style="warning" %} We don't support most file links yet for Glue AI file search — you will need to upload the actual file. We're working on this and will have more improvements coming soon! We do have a GDrive integration that allows GDrive links to be searched by Glue AI. [Read how to set up the GDrive integration here.](/integrations/google-drive) {% endhint %} ## What's not supported yet We're making improvements to Glue AI every day, but there are still a few things that are not yet supported. Since Glue AI is an interface that leverages other LLM models, any limitations that these LLMs have will also be limitations of Glue AI. Glue AI can search and generate text like an LLM, but it is not a workflow builder or an agent. Glue AI is not able to take action on behalf of a user or send messages elsewhere in Glue. It can't invite people to your workspace, create a group, send a message in another thread, or remind you to follow up on something. Glue AI is also unable to tell you information about your workspace or group settings, membership, or admins. Glue AI cannot search for and return images that have been shared in Glue. Glue AI cannot access links that are behind a login, like LinkedIn. *\*The exception is* [*GDrive*](/integrations/google-drive) *links because we have an official integration where you can authorize access to your GDrive account.* Glue AI cannot transcribe audio files. ## Other considerations about how Glue AI works * Glue AI will search across messages sent within the last month by default. If you need it to search a wider timeframe, you will need to specify in your prompt how far back you want it to search. * GlueAI can access previous attachments sent in a thread, up to 20 attachments. So in a thread with many attachments, GlueAI can only see the 20 most recent ones when users ask specific questions about files. To ensure that Glue AI is answering a question about the specific file you have in mind, it's best to attach it directly in your prompt. ## Have a support question about Glue AI? Contact our [support team in Glue](/get-started/help-and-support#reach-out-to-us-in-glue) or via [email](/get-started/help-and-support#reach-us-via-email)! # Threads Feed The Threads feed is your workspace's discovery surface for all threads you have access to: threads you are a member of (in your [inbox](/inbox/inbox)) and [public threads](/conversations/threads/public-threads-launch). It shows you what's happening across the workspace — conversations you can read, reply to, and add to your inbox — without requiring you to be subscribed to every thread in advance. Think of it this way: your **Inbox** is for your most important threads that you are actively notified on. The **Threads feed** is everything else you can catch up on in your own time.
*** ### Getting there The **Threads** feed is available on desktop in the left nav, and the Threads tab in the bottom navigation on mobile. *** ### What you'll see Each row in the feed shows a thread with: * **Thread visibility** — whether it's public to the workspace (thread icon) or private to members (lock icon) * **Thread name** and preview (depending on which viewing mode you're in) * **Members** — the groups or people the thread was sent to * **Reply count** and last activity timestamp * **Unread state** — threads with messages you haven't read appear with a bold title *** ### Manage your threads feed view You can control the threads view in multiple ways to find what you're looking for. #### **Searching** Quickly narrow down the threads view without having to go into a full search. Searching in the threads feed currently only matches thread name. If you need to do a deeper full message search you should still use the search bar or Glue AI. #### **Filtering** Filter the threads view to a specific by group to see all public threads sent to that group, or if you're a member of the group you will see all public and private threads. You can also switch between workspace views here. You can change your workspace as well to filter to groups in that workspace.
#### Sorting | Sort option | What it does | | -------------------- | ---------------------------------------------------------- | | **Date created** | Shows threads in the order they were started, newest first | | **Recently updated** | Surfaces threads with the most recent activity at the top | #### Viewing density options You can control how much information each thread row displays using the density toggle in the top-right corner of the feed. There are three options: | View | What it shows | | --------------------------- | -------------------------------------------------------------------------------------------- | | **Comfortable** *(default)* | A balanced view with thread title, recipients, reply count, and a snippet of recent activity | | **Compact** | A condensed list — useful when you want to scan more threads at once | | **Detailed** | An expanded view with detailed cards for each thread. | *** ### Adding threads to your inbox When you find a thread in the feed that you want to stay on top of, you can add it to your inbox. Once it's in your inbox, you'll be notified of new messages on that thread directly. To **add a thread to your inbox**: **press the plus (+) icon** in the threads feed or when you have the thread open you can click the ellipsis to get the thread menu and choose add to inbox. To **remove a thread from your inbox**: in your inbox, hover over the thread name and select **Mute and hide from inbox.** Or, with the thread open, click the ellipsis to get the thread menu and select Mute from inbox. The thread will no longer deliver to you, but it will still be discoverable in the Threads feed. > **Note:** Adding a thread to your inbox doesn't change who can see the thread — it only affects whether new activity on that thread shows up in your personal inbox. *** ### Threads feed vs. Inbox | | Threads feed | Inbox | | ------------------------------------------ | ------------ | ----- | | Discover public threads | ✅ | ❌ | | Browse without committing to notifications | ✅ | ❌ | | Be notified of new messages in threads | ❌ | ✅ | | Personal prioritization | ❌ | ✅ | *** ### A note on thread visibility The Threads feed only shows **public threads** — conversations that are visible to your whole workspace. Private threads (those sent only to specific people or groups you're not part of) won't appear here unless you are a member on that thread. If you're mentioned in a thread, it will be delivered directly to your inbox rather than waiting for you to find it in the feed. # Directory The Directory is a dedicated section in Glue where you can explore everything in your workspace — groups, people, and apps — all in one place. Access it from the sidebar on desktop, or the Directory tab in the bottom navigation on mobile. If you're a member of multiple workspaces, use the workspace switcher at the top right of the Directory to move between them.
*** ### Groups The Groups tab shows all groups in your workspace. You can browse, search, and take action directly from this view: * **Create** a new group * **Join** an open group you're not yet in * **Request to join** a group that requires approval * **Filter to your groups** to see the ones you already belong to * **Open the group's threads** directly into a filtered view in the threads feed * **Access** [**group settings**](/groups/group-settings) Click any group to open its details in a panel on the right. If you've been invited as a guest to groups in another organization's workspace, those groups appear in the workspace switcher under "external groups." *** ### People The People tab shows all members of your workspace. This includes anyone who has joined the workspace — whether they're from your organization or an outside collaborator who's been added as a workspace member. Click any person to view their profile that includes their name, picture, email address, time zone, status and [working hours](/profile-and-preferences/profile#time-zone-and-work-schedule) they have set. You can initiate a new DM from here by clicking message. You can also click on a member's name from inside a group's member list to jump directly to their profile here. *** ### Apps The Apps tab is where you can discover, install, and manage integrations for your workspace. This includes setting up one-click app integrations, MCP connectors, and custom apps and connectors. For a full guide to what's available and how each type works, see our [integrations documentation](/integrations/integrations-overview) and explore the [app directory](https://app.glue.ai/apps?f=All) in Glue. # Activity Activity is your personal notification center in Glue. While your Inbox tracks threads you're subscribed to, Activity surfaces events happening around you — reactions to your messages, mentions, group changes, and more. You can get to Activity from the sidebar (look for the bell icon) or by using the command palette and searching "Go to Activity." ### How Activity is organized Activity is organized into four tabs: * **All** — every notification in one place * **Mentions** — threads and messages where you've been @mentioned * **Reactions** — emoji reactions left on your messages * **Groups** — group-related events like being added to a group or a new group being created in your workspace Click any tab to filter the list. ### What shows up in Activity #### Someone @ mentioned you in a message When someone @ mentions you in a message, it appears as a mention row with a preview of the message and context around the @ mention. Click to jump to the message. #### Someone reacted to your message When someone reacts to a message you sent, you'll see their emoji reaction, their name (and how many others also reacted, if applicable), and a preview of the message. You can also see the full reaction strip inline. #### You were added to a group When someone adds you to a group, you'll see the group name, emoji, member count, and description. Click the row to go directly to the group. #### A new group was created in your workspace When a new group is created in a workspace you belong to, it appears in Activity so you can discover and join it. Shows the group name, members, and description. #### Join requests When someone requests to join a group you manage, a notification appears in Activity. Click it to review and approve or deny the request. ### Marking activity as read A dot will show up next to the Activity section to indicate there is something new. Unread notifications show a blue dot on the row. Clicking a row marks it as read. If you open a thread that has associated Activity notifications, those are marked as seen automatically. Once you navigate out of the activity view, it will count all the activities as read automatically. ### Navigating from Activity Clicking any row takes you to the relevant thread, group, or join request. On desktop, the detail opens in a pane alongside your Activity list so you don't lose your place. # Sign in to Glue The same email address is your login for all Glue workspaces you are a member of. Read on to learn how to sign in to Glue with your email address or Google account. ### Sign in to Glue If you're joining Glue from an invite, click on the email notification to access Glue or navigate to the Glue [web app](https://app.glue.ai/) and sign in. Log into Glue with your work email, using either Google or a code sent to your email address. Once logged in, you'll stay signed in on your device. Glue does not use passwords, so you will not set a password when you login. We wanted to make this as secure and easy to use as possible — don't worry about remembering or resetting passwords! If **single sign-on (SSO)** is required for your workspace or org, authenticate with your company's SSO provider to finish signing in. ### Sign in to your workspace After signing in with your company email, you’ll automatically be connected to your company’s workspace and groups. * If a workspace already exists, you’ll see it right away. * If one hasn’t been created yet, you’ll have the option to [create the workspace](/for-admins/workspace-setup) for everyone with your email domain (e.g. `@gluegroups.com`). ### Set up your Profile, Preferences and Notifications {% content-ref url="/pages/SBQ3JTI2cuHtFLjGX14C" %} [Profile](/profile-and-preferences/profile) {% endcontent-ref %} {% content-ref url="/pages/FABKNXzfOPXIK1ME2qTf" %} [Preferences](/profile-and-preferences/preferences) {% endcontent-ref %} {% content-ref url="/pages/u1PM3nsq9ipY9DraxecI" %} [Push notifications](/profile-and-preferences/push-notifications) {% endcontent-ref %} ### Create your first thread Is there a question you have for someone on your team or an idea that you want to get feedback on? Create a [thread](/conversations/threads) about the topic and see how much better life works with Glue. # Profile Update your profile details to control what details others can see about you in Glue and make it easier to collaborate with your colleagues. ## Customize your profile Click on your profile picture and select the Edit profile option to be able to modify the following details: * Name that will display in Glue (we recommend using your full name) * Title * Profile Picture * Time Zone (can be set automatically) * Location * Work Schedule

Select Edit profile

Edit profile menu — with the work schedule turned off

Edit profile menu with work schedule turned on

### Time Zone and Work Schedule If you choose to share your work schedule on your profile, you can pick and choose the days you are working, with a schedule for each day (in 15 minute increments). You will need to set your time zone as well for this feature to work. #### What others will see on your profile about your work schedule * Within your daily working hours * Green badge that says "Working hours" shows next to Schedule * Outside of your daily working hours * The working hours badge will go away, but your day's work schedule will still be visible * Not scheduled to work that day * It will say "Not Scheduled" This is not the same thing as an online indicator. It is not based on being actively on Glue at that specific time, but rather to show you are within your work day.

Green "working hours" badge indicates this person is within their work schedule for the day

Profile view when someone is not scheduled to work that day

# Preferences Manage your preferences to customize how Glue works for you. Navigate to your preferences menu by going to the upper righthand corner and **clicking on your profile picture and then selecting preferences.** ## Customize your preferences #### Preferences for your account * [Push Notification preferences](/profile-and-preferences/push-notifications) for delivery and sound * Glue AI model default #### Preferences per device * Enaling push notificaitons on the device * Editor default for enter key * Audio permissions * Appearance (light mode vs dark mode) * Font size {% hint style="info" %} You can also see which version of Glue your app is on by scrolling to the bottom of the Preferences menu. {% endhint %}
### Push Notifications Please refer to our Push Notification documentation. {% content-ref url="/pages/u1PM3nsq9ipY9DraxecI" %} [Push notifications](/profile-and-preferences/push-notifications) {% endcontent-ref %} {% content-ref url="/pages/KPfTef71OYjlfLW01A6b" %} [Notification troubleshooting](/profile-and-preferences/push-notifications/notification-troubleshooting) {% endcontent-ref %} ### Editor options #### Enter Key You can change what the enter keyboard command is from starting a new line break to sending a new message. This preference is set per device. We have the default set so that pressing enter starts a new line in the message, this is because Glue is built to optimize for threads first, so it's easier to draft longer form content. If you prefer to change this you can! * **Default: Enter = New Line**, CMD+Enter = Send * Can change it to Enter = Send, CMD+Enter = New Line ### Audio Grant glue audio access to your device to be able to record voice notes.
### Appearance #### Color Scheme Change the color scheme for you Glue app. This preference is set per device. * Default: System Default (match your device's preferences) * Light Mode * Dark Mode ### Font Size Scale the default font size in Glue up or down based on your preferences. Choose between five sizes. ### Glue AI Model Glue AI is set to automatically choose the model that works best for that specific prompt, and you can change the model you are using on each prompt in the Glue AI tab. If you'd like to use a specific AI model as your default for all your Glue AI prompts (e.g. your organization pays for specific model and uses the API keys in Glue, you prefer a specific model, etc) you can do so. You will still be able to change the model used on individual prompts in your Glue AI tab. # Set a status Tell your team you're out of office or in a meeting with a status ### How to set a status 1. Click on your profile picture in the upper right hand corner 2. Choose "set a status" 3. Pick from one of our presets or customize your own status with: * Emoji * Status name * Duration ("Remove status after")
### **Editing or Removing Your Status** Your status will automatically clear when the time you set expires. If you want to change or remove it sooner: **To remove your status manually:** 1. Click your profile picture. 2. Hover over your current status. 3. When the **X** icon appears, click it to clear your status. 4. You can also click on your status to open the status modal, and click **Clear status**.
**To edit your status:** 1. Click your profile picture. 2. Click your status to open the status modal. 3. Update your text, emoji, or duration—or clear it from the modal.
*** # Push notifications Account Level Notifications ## Notification types * **Push Notifications** can be sent for both mobile and desktop if you’ve enabled them on the device. * **Email Notifications** will be sent if all push notifications are disabled. When push notifications are enabled for either desktop or mobile, we automatically disable email notifications to prevent duplicates. * **Badges** will appear in Glue to let you know of new messages. A red badge will show if you or a group are directly @ mentioned. All other new messages will show up bolded. There will also be a badge on the app icon with the number of unread threads. ## Enable notifications on your device {% embed url="" %} If you want to receive push notifications on your device, you will need to enable the notifications per device. The easiest way to do this is by turning on notifications when you first download the Glue apps, but you can check your notification settings at any time in the preferences menu. ### **During Account Setup** When you first download the app and log in, a pop-up will prompt you to enable notifications. *For the best experience, we highly recommend setting up notifications at this point.*
**Press the "continue" button** on the turn on notifications pop up. Make sure to **select allow on any system pop ups** that come up on your device to grant Glue permission to send notifications on your device.

Pay attention for a pop up system prompt — select Allow

### **After Account Setup** If you skipped setting up notifications, you can **enable them later in your preferences** menu under ["Push notifications (this device)."](#push-notifications-this-device) If you disabled your notifications and want to re-enable them, you will need to do so in your device's settings. See specific [instructions](#instructions-for-enabling-device-notifications) for each device type below. *** ## Manage notification preferences in Glue For more granular notification settings, navigate to **Preferences** under your profile avatar. Here you can control which messages you get notifications for, and check if your push notifications are enabled.

Manage notifications from the Preferences menus - types of notifications, sounds and enabled status

### Inbox notifications This **controls which messages you will get push notifications for.** This preference will apply across all of your Glue apps (and email if you do not have push notifications enabled). **Default: All Inbox Messages** * By default, you will get push notifications for all Inbox messages. * Any new message appearing in your [Thread Inbox](/inbox/inbox#what-makes-a-thread-important-to-you) will trigger a push notification. * New threads created or chats sent in Groups you belong to will send a push notification. * DMs will send a push notification. **Mentions, Replies, & Direct Messages Only** * You’ll only receive push notifications for messages where you are directly @mentioned, sent a direct message, or a message you sent is quote replied. * With this notification setting, **you will not get a push notification on every thread in your inbox**, even if you choose to follow the thread. You will only get a push notification unless you or a group you are in get directly @ mentioned. **Nothing** * Choosing this option means you won’t receive push or email notifications for new messages or Threads in your Inbox. * **Exceptions:** You’ll still be notified of invitations or requests to join a workspace, group, or thread, as well as any invites from individuals outside your workspace. {% hint style="info" %} If you want to automatically follow every thread in a specific group, so that you get all notifications about activity in that group, you can manage this in a [group's notification settings](/groups/group-settings/group-notification-settings). {% endhint %} ### Notification Sounds Customize which push notifications will play a sound. The sound itself is managed by your device and cannot currently be customized. Make sure your device's system settings for notifications allow Glue or your Browser to play sounds. **Default: All Notifications** Every message you get a push notification for plays a sound. **Mentions, Replies, & Direct Messages Only** Only mentions, replies (threads created from one of your messages) and DMs will play a sound, even if you get push notifications for everything in your Inbox. **Don't play any sounds** No notification sounds will play, even if you get push notifications. {% hint style="info" %} Note: If you change your notifications preferences from All Inbox to Mentions, Replies, And DMs or None, your sound preferences will automatically adjust with it. {% endhint %} ### Push notifications (this device) **Check if notifications have been successfully enabled on your device from your Preferences menu.** You will see different prompts in this section based on your device's system settings, with relevant instructions based on what action you need to take next. #### ✅ Notifications are successfully enabled for your device If your notifications are actively enabled on your device, you will see the message that **notifications are on** with a green checkmark icon. You will receive push notifications based on the [inbox notification preferences](#inbox-notifications) you've selected. 🔔 You can **send yourself a test notification** to see how a notification displays and confirm it's working.

If notifications are enabled on your device, you will see the green check mark and test notification button

#### 🚫 Notifications are not enabled for your device You will see one of the following two prompts if notifications are not enabled. 1. **Turn on notifications** — This means notifications have never been enabled, and you need to allow Glue to send notifications to your device. Once that connection is established between your device and Glue, notifications can be be enabled and disabled based on your preferences in Glue or your device's system settings. * Press the **"Turn on notifications"** button * When your device asks for permission via a system prompt pop up, choose **Allow**

If notifications have never been enabled, you will see the "Turn on notifications" button

{% hint style="warning" %} **Surprised to see that notifications have not been enabled?** It's possible you missed the system prompt the first time around. Make sure to **select allow on the system prompt** after pressing "turn on notifications" (the prompt will look different depending on the device type). {% endhint %} 2. **To get notifications from Glue, you'll need to turn them on in your System Settings** — This means that Glue is allowed to send notifications to your device, but notifications are currently disabled in your device's system settings. You cannot re-enable notifications from Glue in this scenario, you have to go into your device's notification settings. * Go to your **device’s Settings > Notifications > Glue** * Make sure notifications are **turned on**

If notifications have been setup but disabled, you will see this alert badge with instructions to re-enable in your device settings

{% hint style="warning" %} [Device specific instructions](#checking-your-devices-notification-settings) on re-enabling notifications can be found below. {% endhint %} *** ## Checking your device's notification settings Here are instructions for finding your device's specific notification settings for Glue. If you want to disable your Glue notifications, or re-enable them after disabling, you will need to do so at the device level.
Mac OS Notifications 1. Open the **System Settings** app 2. Tap **Notifications** 3. Under Application Notifications **select the Glue app** 4. Turn on **Allow Notifications** 5. Choose how and where you want to receive notifications
Windows Notifications 1. On Windows 11, open your **Settings app** 2. Open **System** and then **Notifications** 3. Find **Notifications from apps and other senders** 4. **Select the Glue app** 5. Make sure notifications are turned on
iOS Notifications 1. Open the **Settings app** 2. Tap **Notification**s 3. Under Notification Style **select the Glue app** 4. Turn on **Allow Notifications** 5. Choose how and where you want to receive notifications
Android Notifications 1. Open your device's **Settings app** 2. Click on **Notifications** and then **App Notifications** 3. **Find Glue** and make sure **notifications are toggled on** 4. Click on Glue if you want to change other notification settings 5. You can also find your notification preferences from **Settings > Apps > Glue** and making sure **notifications are allowed.**
Web Browser Notifications **To enable notifications for Glue in Chrome:** 1. Click the "View site information" toggle icon in the address bar 2. Toggle Notifications on 3. Note: If you are using Chrome on a Mac, you will also need to go into your Mac system settings > notifications and allow notifications from "Google Chrome Helper (Alerts)" **To enable notifications for Glue in Edge:** 1. Click the lock icon in the address bar 2. Select “Permissions for this site” 3. Find Notifications and select Allow **To enable notifications for Glue in Safari:** 1. Click Safari in the menu bar 2. Select Settings… 3. Click Websites, then Notifications 4. Find Glue (app.gluegroups.com or app.glue.ai) and select Allow
# Notification troubleshooting Something not working as expected with notifications? Check out some troubleshooting tips below. ## Not receiving notifications ### Troubleshooting steps 1. [Check that notifications are enabled in Glue](#check-that-notifications-are-enabled-in-glue) 2. [Check that your device is not in a do not disturb mode](#check-that-your-device-is-not-in-a-do-not-disturb-mode) 3. [Check for additional settings based on your device type](#check-additional-settings-based-on-your-device-type) ### **Check that notifications are enabled in Glue** The first troubleshooting step across devices is to check your notification preferences in Glue. 1. Navigate to your preferences menu and [make sure notifications are enabled](#push-notifications-this-device). This is per device, so even if you have them enabled on one device, they might not be enabled on another. 2. If [notifications have not been enabled for your device](#notifications-have-not-been-enabled-for-your-device), follow the prompts to turn them on. 3. If [notifications are disabled for your device](#notifications-are-disabled-for-your-device), you will need to go into your [device settings](#checking-your-devices-notification-settings) to turn them back on. 4. If [notifications are enabled](#notifications-are-enabled-for-your-device), press the "send test notification" button to see if a notification comes through. 5. Double check what you have [inbox notifications](#inbox-notifications) set to — unless you have push notifications set to "All inbox messages" you will not receive push notifications for every message.

If your notifications are enabled, press the "send test notification" button for testing

### Check that your device is not in a "do not disturb" mode **Make sure your device's do not disturb or focus mode are turned off** - the name of this setting will be dependent on your device type. * **Macs** - make sure Do Not Disturb or Focus settings are off. * **Windows** - make sure Focus Assist and Quiet Hours are off. {% hint style="info" %} **Note for Apple Users:** If you are signed into your Mac and iPhone with the same Apple ID, both devices will enter Do Not Disturb mode if you enable the setting on one of the devices. {% endhint %} ### Check additional settings based on your device type {% tabs %} {% tab title="Mac" %} **Update your macOS notification preferences** 1. Open your computer's **System Preferences**, then click **Notifications**. 2. Select **Glue** from the list. 3. Make sure the **Allow Notifications from Glue** toggle is on and your alert style is set to either **Banners** or **Alerts**. 4. If you do not see Glue as an app in your Notifications settings, try deleting the Glue app and reinstalling it. **Check your macOS Do Not Disturb settings** 1. Click the **toggles icon** in the top right corner of your screen to open the Mac Notification Center. 2. Click **Do Not Disturb** and make sure it’s toggled off. {% endtab %} {% tab title="Windows" %} **For Windows 10 - check your settings for Notifications & Actions** 1. Click the **Start menu**. 2. Select **Settings**, then **System**. 3. From the left sidebar, click **Notifications & Actions**. 4. Ensure **Get notifications from apps and other senders** is enabled. 5. Find Glue in the list and **check if notifications are enabled.** **For Windows 11 - check your settings for Notifications** 1. On Windows 11, open your **Settings app.** 2. Open **System** and then **Notifications.** 3. Make sure the **Notifications are toggled On.** 4. Find **Notifications from apps and other senders.** 5. Find Glue in the list and **check if notifications are enabled.** 6. **If you can't toggle the notification on, check your Edge settings for notifications** for the app.gluegroups.com site. Click the "..." at the top of the app and select app settings. Under permissions click "see permission details." Under notifications, make sure it says "allow." \ **Check your Focus Assist settings** 1. On Windows 10, click the **Start menu**. 2. Select **Settings**, then **System**. 3. From the left sidebar, click **Focus Assist**. 4. Select **Off** to deactivate Focus Assist and resume receiving notifications. {% endtab %} {% tab title="iOS" %} **Force quit the app and restart your device** Sometimes notification issues can be fixed by restarting your phone or tablet. **Update your iOS notification preferences** 1. Open your phone's **System Preferences**, then click **Notifications**. 2. Select **Glue** from the list. 3. Make sure the **Allow Notifications from Glue** toggle is on and your alert style is set to either **Banners** or **Alerts**.\ **Check your iOS Do Not Disturb settings** 4. Swipe down from the upper righthand corner of your screen to pull up your actions menu. 5. Look for the **Focus** button with the moon icon and make sure all focus modes are turned off. **Uninstall and reinstall the Glue app on your phone** {% endtab %} {% tab title="Android" %} **Force quit the app and restart your device** Sometimes notification issues can be fixed by restarting your phone or tablet. **Update your notification preferences** 1. Open your device's **Settings app** 2. Click on **Notifications** and then **App Notifications** 3. **Find Glue** and make sure **notifications are toggled on** 4. Click on Glue if you want to change other notification settings 5. You can also find your notification preferences from **Settings > Apps > Glue** and making sure **notifications are allowed.** 6. **Also make sure that Google Play Services has notifications turned on.** You can also find that under either Notifications or Apps. **Note:** Google Play Services is required to receive notifications on Android. Make sure your [device is supported](https://support.google.com/googleplay/answer/1727131?hl=en). **Uninstall and reinstall the Glue app on your phone** {% endtab %} {% tab title="Browser" %} {% hint style="warning" %} **For all browser types, check your device's system settings** to make sure your browser is allowed to send notifications. {% endhint %} **Chrome** 1. From the Chrome menu at the top of your screen, select **Settings**. 2. Click **Privacy and security** in the left sidebar, then click **Site Settings**. 3. Below **Permissions**, select **Notifications**. 4. Make sure **Sites can ask to send notifications** is toggled on. 5. Make sure [app.gluegroups.com](ionic://localhost/) shows up under "Allowed to send notifications" 6. Note: If you are using Chrome on a Mac, you will also need to go into your Mac system settings > notifications and allow notifications from "Google Chrome Helper (Alerts)" \ **Edge** 1. From the Edge menu at the top of your screen, click the **three dots icon**. 2. Go to **settings.** 3. Click **Cookies and site permissions** in the left sidebar. 4. Below **All permissions**, select **Notifications**. 5. Make sure app.gluegroups.com is included in the **Allow** section. \ **Firefox** 1. From the Firefox menu at the top of your screen, select **Preferences**. 2. Click **Privacy & Security** in the left sidebar. 3. Below **Permissions**, click the **Settings** button next to Notifications. 4. Make sure your Glue workspace is included in the **Notifications Permissions** list. \ **Safari** 1. From the Safari menu at the top of your screen, select **Preferences**. 2. Click **Websites**, then select **Notifications** from the left sidebar. 3. Make sure your Glue workspace is allowed to send notifications. {% endtab %} {% endtabs %} {% hint style="warning" %} **Note:** If you have an external monitor plugged in, the push notification will still appear on your main device, even if Glue is open on the external monitor. {% endhint %} ## No notification sounds Check your notification [sound preferences](#notification-sounds) in Glue, check your device's notification settings and send yourself a test notification! {% tabs %} {% tab title="Mac" %} **Check if sounds are enabled** 1. Open your computer's **System Preferences**. 2. Select **Notifications**. 3. **Find Glue** in the list and make sure **Play sound for notifications** is enabled. 4. **If using a browser,** find the browser in the list and sure Play sound for notifications is enabled. **Check your audio output settings** 1. Open your computer's **System Preferences**. 2. Select **Sound**, then click **Sound Effects**. 3. Next to **Play sound effects through**, check to see if the correct device is selected, then make sure your alert volume is turned up. 4. Make sure the box next to **Play user interface sound effects** is checked. **Send a test notification** 1. Click your profile picture in the upper righthand corner. 2. Select **Preferences** from the menu. 3. Scroll to **Push notifications (this device)** and click the **"Send test notification"** button. {% endtab %} {% tab title="Windows" %} **Check Windows notification settings** 1. **On Windows 10**, click the **Start menu**. 2. Select **Settings**, then **System**. 3. From the left sidebar, click **Notifications & Actions**. 4. Find the Glue app or your browser in the list and check if **Play a sound** is enabled. 5. **On Windows 11,** open your **Settings app.** 6. Open **System** and then **Notifications.** 7. Make sure the **Notifications are toggled On.** 8. Find **Notifications from apps and other senders.** 9. Find **Glue** in the list and click on it. Scroll down and make sure **play a sound when a notification arrives** is enabled. **Send a test notification** 1. Click your profile picture in the upper righthand corner. 2. Select **Preferences** from the menu. 3. Scroll to **Push notifications (this device)** and click the **"Send test notification"** button. {% endtab %} {% endtabs %} {% hint style="info" %} **Note:** If you are using an external monitor, try disconnecting your monitor and then running the test notification to see if the problem persists. {% endhint %} ## Still having issues? If you try our troubleshooting and still have issues, you can [reach out for support](/get-started/help-and-support). Please specify what exactly isn't working in your message — is it not seeing notifications, not hearing the sound, or something else? What were you expecting to happen, and what actually happened? The more detail the better! If you're able to send screenshots or screen recordings too that helps. # Agent Personalization Glue **Agent Personalization lets you personalize Glue AI's behavior,** ensuring that its responses and suggestions align with your unique communication style and preferences. *** ## 📘 What can you personalize? The Agent Personalization feature lets you set user-defined instructions that guide Glue AI's interactions within the platform. Similar to Custom Instructions in other AI tools, these rules are currently set on a per-user basis. There are different types of rules you can set. ### Messaging Rules Messaging Rules **guide how Glue AI interprets and responds to your direct requests** when you message Glue AI or @ mention Glue AI in a message. They allow you to specify preferences regarding tone, formatting, language, and more.
Potential Use Cases for Messaging Rules * Giving Glue AI context on your role at your company. * Ensuring responses maintain a professional tone. * Requesting responses in a specific language or format.
### Suggestion Rules Suggestion Rules customize how Glue AI proposes content within the Glue application, with options to set rules for **thread names, recipient suggestions, and group emojis.**
Potential Use Cases for Suggestion Rules * **Thread naming** - Add prefixes, suffixes or naming conventions based on content * **Thread recipients** - Encourage or discourage recipients depending on thread topic * **Group emojis** - Have some fun and encourage use of certain emojis for team identification
### MCP Server Rules You can also customize how Glue AI should interact with each MCP Server by configuring rules on a server by server basis. You can find more information about [configuring MCP Server rules here.](/integrations/mcp-servers#configure-rules-for-your-mcp-server-for-the-best-experience)
Potential Use Cases for MCP Server Rules * **Store default values or IDs** (e.g., project or user IDs, board names) required when creating or updating items in external tools. * **Define reusable templates** for common task types, messages, or request formats. * **Enforce naming conventions** for tasks, documents, events, etc created via connected tools.
*** ## How to personalize Glue AI
1) Open Glue preferences * Click on your profile avatar in the upper-right corner of the Glue interface. * Select **Preferences** from the dropdown menu.
2) Go Agent Personalization * In the Preferences menu, find and click Agent Personalization
3) Add rules to the Messaging and Suggestion Rules sections * You will see different sections for Messaging rules, and the Suggestion rules (thread naming, thread recipients, group emojis). * Each has a text box where you can define your personal rules. You can enter multiple rules at a time in each text box.
{% hint style="info" %} To [configure rules on an MCP Server](/integrations/mcp-servers#id-4-configure-rules-for-your-mcp-server-optional), go to the MCP Servers tab, click on the installed server and choose "configure rules." {% endhint %} *** ## ✅ Tips for Writing Effective Rules * **Be specific**: Clearly define your expectations and be as direct as possible. * **Use full sentences**: Write rules like you’re giving instructions to a teammate. * **Give context and examples where relevant** * **Stay organized with one rule per line** for clarity (not required, but helpful to have line breaks for reviewing and editing your rules over time). * **Test and revise**: Try out your rules, see how Glue AI responds, and refine them over time. ### Examples of Agent Personalization
Messaging Rules Examples ``` - Respond to all messages in a formal tone, using complete sentences. - When discussing financial reports, assume the audience has a basic understanding of accounting principles. - When summarizing meeting notes, use bullet points. E.g., '• Discussed Q3 targets • Reviewed marketing strategy.' ```
Suggestion Rules Examples **Thread naming** ``` - If a thread context includes a link to a Linear issue or Figma file, prefix the thread name with "Project:" Don't add "Project:" if a user just types the the word "project" or "link". - If the thread is describing a bug that a customer is experiencing or that the team has noticed via logs or reports, prefix the thread name with "🐛 Bug:" ``` **Thread recipients** ``` - If a thread is describing an API bug, suggest the API group. - If the thread is describing a UI bug, suggest the Design group ``` **Group emojis** ``` - Use a different animal emoji for every department group, picking an animal emoji that fits with the team name. ```
*** ## 🧠 Notes * **Scope:** Agent personalization is currently user-specific and cannot be applied at the workspace level. * **AI Interpretation:** Glue AI may not always interpret complex or ambiguous instructions as intended. * **Over-Specification:** Overly detailed rules might restrict Glue AI's ability to provide creative or flexible responses. * **MCP Server Rules:** You can also define rules for MCP server behavior by configuring rules on the server once it’s set up. # Workspaces A workspace connects an organization, community, or team. ## Creating a Workspace * Organizations can set up a workspace for a specific domain (e.g. @acme.com). * Users with that email domain will automatically see the workspace and be able to join when they sign into Glue for the first time. {% hint style="success" %} Once setup, workspace members can: * View and join various groups within the workspace. * Start threads or direct messages with other members. {% endhint %} ## Features of Workspaces ### **Glue AI** Access Glue AI, an AI assistant that has context on everything happening in Glue. Can use 1:1 or in a group where all members can collaborate with Glue AI at the same time. ### **Groups** Organize people and conversation threads into groups centered around teams, projects or topics. ### **General Group** Communicate with your entire workspace with this automatically generated group that includes every user. Ideal for company-wide announcements, shout-outs, and reminders. ### **Guest Access** Communicate with [guests](https://docs.glue.ai/groups/guests) (external users like contracts, customers, or partners) by adding them to a group. They do not need to be added to the entire workspace. {% hint style="info" %} If your company doesn't have a workspace yet, you can [create one](/for-admins/workspace-setup) or [use Glue without a workspace](/workspaces/external-users/using-glue-without-a-workspace). {% endhint %} # Workspace settings View and manage groups, members, apps, and settings for your workspace. ## **Accessing workspace settings** Your workspace settings menu can be found by clicking on your company logo in the upper righthand corner of your app, and then choosing your workspace name. If you belong to multiple workspaces, you will see them all listed in this menu and can pick which workspace you want to view. You can also join another workspace that your email domain has access to or that you have been invited to.

Access your workspace settings by clicking on your workspace logo and choosing the workspace

This opens a modal with details on workspace groups, members and apps. Admins will also see the Settings and Advanced tabs.

Workspace Settings Modal (Admin View)

## **Workspace Settings access by role** Here are the actions you can take from the workspace settings menu, depending on your permission level in the workspace (admin vs member). | Settings section | Action | Workspace Admins | Workspace Members | | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | ------------------------------------------------------------------------------- | | Members | Add new members | ✅ | Not from the workspace settings menu, but you can invite users to the workspace | | Members | Change member permissions to admins and vice versa | ✅ | | | Members | Remove members from workspace | ✅ | | | Members | Search for members in the workspace | ✅ | ✅ | | Groups | Search for, create or join groups | ✅ | ✅ | | Apps | Add apps to the workspace | ✅ | ✅ | | Settings | | ✅ | | | Advanced | Slack Import | ✅ | | | Advanced | Delete the Workspace | ✅ | | | Billing | Manage your billing - *web browser only* (Add CC info, switch plan types, cancel subscription) | ✅ | | ## **Managing Settings (Admins Only)** **Admins can control some more granular settings for the entire workspace including:** * **Change the workspace name** * **Change the workspace logo** * **Control discoverability** * Toggle whether your workspace is visible to anyone signing up with your verified email domain. * **Manage access settings**\ Choose between: * **Open access**: Anyone with your domain can join immediately. * **Closed access**: New users must request to join and be approved by an admin. * **Lock the General group** * Restrict posting in the default "General" group so that only admins can send messages. * **Add API keys for your LLM provider** * Connect your external large language model (LLM) service by securely storing API keys. * Note: Glue AI uses the LLM models, but it doesn't directly use their apps or features (e.g. Glue AI uses OpenAI and Anthropic models, but does not use ChatGPT or Claude and their specific features).
## Deleting your workspace You can delete your Glue workspace at any time from the workspace setting's advanced menu. ### How to delete your workspace manually 1. Go to **Workspace Settings**. 2. Click on the **Advanced** tab. 3. Scroll to the **Delete Workspace** section. 4. Click **Delete**. 5. A confirmation message will appear. Click **Delete** again to confirm. ⚠️ **Important:** This action is permanent and cannot be undone. Once deleted, all workspace data will be permanently removed.
### Automatic workspace deletion after subscription expires If your trial expires or you cancel your subscription: * Your workspace enters **read-only mode** after 7 days. * Your workspace is **automatically deleted** 30 days after that if no action is taken. You don’t need to manually delete your workspace if you simply want to let it expire. # Multiple workspaces Using Glue as a member of more than one workspace A major difference between Glue and other work chat apps is that Glue is set up so you can be a member of multiple workspaces simultaneously without the hassle of switching back and forth. ### **Glue provides seamless access across multiple workspaces** * Glue allows users to be members of as many workspaces as they like. * No need to switch between workspaces; everything is accessible from one place. * Your email address serves as your profile identifier in Glue. {% hint style="success" %} Access all workspaces, groups, and threads directly in the same view without switching. {% endhint %} ### **Inbox and Feed** * [**Inbox**](https://docs.glue.ai/inbox/inbox)**:** Your central hub for all important threads and chats across all workspaces. * [**Feed**](https://docs.glue.ai/feed/feed)**:** Quickly browse and catch up on updates from any workspace you’re a member of. ### **Managing Workspaces** You can view and manage each workspace from the [workspace settings menu](/workspaces/workspace-settings#accessing-your-workspace-settings). > 🔔 **Upcoming Feature:** Glue will introduce filters to help you easily focus on a specific workspace. # External users Collaborate with people outside your company in groups and threads Glue lets you collaborate with people outside your company's workspace—like clients, contractors, and partners—by **inviting them to specific groups or threads as external users**. This way you can easily chat with someone outside your company without giving them access to your entire workspace or asking them to pay for a Glue license. ## What is an External User? **External users** are people who: * **Are not members of your Glue workspace** — they might belong to another Glue workspace or they can set up a [free Glue account](/workspaces/external-users/using-glue-without-a-workspace) with limited access. * **Can be added to specific groups or threads** in your workspace without having access to any other part of your workspace. * **Have a yellow external badge** displayed in their profile and in group members lists. {% hint style="success" %} **External users can join Glue for free**—if someone doesn’t already have a Glue account, they can create one at no cost. They will receive an alert via email when you've added them to a group or thread that gives them a link to sign up. {% endhint %}
What does the external user badge look like? **A yellow external badge** will show up on an external user's profile, in a group's members list that includes external users, and in the group directory for groups including external users or owned by external users. You will not see the badge next to user's names in the chat or next to group names in your inbox.

Yellow external badge in a group's members list

Groups with external users will show the badge in your group directory

You can also see groups owned by external workspaces in your group directory

## Key Benefits **Unlimited external users** * Collaborate with as many external users as you need. * No added cost to your subscription. **Seamless collaboration with customers and partners** * Create dedicated threads for projects, deals, or assignments with external collaborators, rather than lumping all communication together in a channel. * External users can create free Glue accounts with messaging access if they do not want to pay for the full functionality of a workspace. **Clear boundaries and access controls** * External users can only see what you explicitly invite them to. They don’t have access to the rest of your workspace. * External users can be removed at any time and will immediately lose access to the group or thread history. ## Adding External Users to Groups, Threads or DMs To invite an external user: 1. **Go to the group or thread you want to include them in.** 1. If it's a group, access the group members list and click **Add new member**. 2. If it's a thread, click on thread name or access the thread settings. Click into the text box. 2. **Add the user** either with their name or email address, depending on if you've messaged them before. 1. **If you've messaged the user before** or are in a group together, they are now in your contacts list. You can **type in the user’s name.** 2. **If you've not messaged the user before**, type or paste in their **email address.** 3. **Click add.** 3. If they’re not a Glue user yet, they will receive an email notifying them of the group or thread they were added to and inviting them to set up a Glue account. **If you need to remove an external user**, the process is the same as removing a workspace member. See [removing users from a group](https://docs.glue.ai/groups/group-settings/admin-settings-for-groups#removing-users-from-a-group) and [removing users from a thread](https://docs.glue.ai/conversations/threads/managing-threads#removing-recipients-from-a-thread). \ What can an external user do in Glue if they set up a free account? ------------------------------------------------------------------- Free accounts do not have the full functionality of a paid Glue workspace. Click the page link below for more details. {% content-ref url="/pages/rWCAJeGxBS4sKEIVBvj8" %} [Using Glue without a workspace](/workspaces/external-users/using-glue-without-a-workspace) {% endcontent-ref %} # Using Glue without a workspace External users can set up a free, limited use Glue account If someone in a paid Glue workspace has added you to a group or sent you a message (as an [external user](/workspaces/external-users)), you **can setup a free Glue account**. You will receive an email invite with a sign up link to create your free account. This **free account does not come with the full feature capabilities of a Glue workspace,** but you can always create a workspace later if you decide you'd like to upgrade. ### **What can you do in Glue if you are not a member of a paid Workspace?** * Collaborate in groups or threads that you've been invited to. * Send new threads or DMs to Glue users who you have already messaged you. * Connect with anyone by adding their email address to a thread or direct message — once you've messaged them once, you can easily create new threads or DMs with them again by searching their name in Glue. If they do not yet have a Glue account, they will need to sign up. {% hint style="info" %} Threads are a freestanding unit of communication, independent of any workspace or group. So even users without a workspace have the freedom to organize their communication in threads and be added to threads and groups in other company's workspaces. {% endhint %} ### **Limitations of not belonging to a paid Workspace** * **Cannot create groups** to organize any people, projects, or topics. * **No direct access to Glue AI,** our powerful AI assistant. You will be able to see responses from Glue AI in external groups that you belong to, but cannot ask it any questions yourself. We do include a 7 day free trial of Glue AI when you first sign up. * **No access to our app integrations** {% hint style="info" %} You can create a new workspace at any time when you are logged into Glue on a web browser. Click on your workspace logo on the top right corner of the app and select **Add Workspace** from the drop down menu. {% endhint %} # Custom emojis You can create custom emojis to use in your reactions and messages! ## Create a custom emoji 1. Click on the Reactions (emoji) button either in the message editor or when hovering over a sent message.
2. Then click **Add emoji** at the bottom of the emoji picker modal
3. Users have two options when creating a new custom emoji * Upload an image or gif file to create a new emoji * Choose the **Magic** option to have Glue AI generate an emoji based on your description 4. Name your emoji or use the auto generated name 5. If you are in more than one workspace, choose which workspace you would like to add your new emoji to. 6. Save!

Add emoji modal

{% hint style="info" %} A custom emoji will only live in one workspace. People outside of your workspace can see the emoji if you use it on a thread with them, but they will have to add it to their workspace to be able to use it themselves. {% endhint %} ## Manage custom emojis * Click on the Reactions (emoji) button either in the message editor or when hovering over a sent message. * Click **Manage emojis** under the reaction emoji picker modal. * There you will be able to view the custom emojis in any of your workspaces. * Users can delete any emoji that they created. * Workspace admins can delete any custom emoji in their workspace.
# Workspace setup

Create workspace modal

## How to set up your workspace Go to [app.glue.ai](https://app.glue.ai) When logging into Glue for the first time with your work email, click **Create Workspace** during the onboarding flow to create the workspace for your company's domain. The default setting for a workspace for that anyone with your company email address to be able to join when they log in. You can control access by controlling who has an active email address from your domain. If you create a workspace with your personal email, note that common email domains are whitelisted and will not enable anyone with a Gmail, Outlook, Yahoo, etc. email address to join your personal workspace. ### Add your team You can add team members to your workspace during the setup process, or at any time after your workspace is created. {% content-ref url="/pages/x5a7eaxQ6iesmHrlD03B" %} [Manage members](/for-admins/manage-members) {% endcontent-ref %} ### Create groups You can also create groups during your workspace setup, or at any time after your workspace is created. Check out our [group setup page](/for-admins/group-setup) for more advice on creating groups. {% content-ref url="/pages/9AbVPJ9WdDNDm0kfB0I4" %} [Group setup](/for-admins/group-setup) {% endcontent-ref %} # Manage members ## Overview In your Workspace Settings menu under the Members tab, Admins have the ability to manage Glue membership in the following ways: * Search for users to take actions * Add a new user * Resend an invite * Cancel an invite * Make a member an admin or downgrade an admin to a member * Remove a user from the workspace
## **Add Users to the Workspace** #### How to access the "Invite to Glue menu" For admins, this menu can be accessed from your workspace settings menu, under Members. There's a button that says "Add a member." #### **There are two main ways to invite team members** * **Copy and send the invite link** - anyone can join the workspace when they click on the link. * **Copy and paste the email addresses** of your teammates into the **Send to** field to invite them to your workspace. You can paste multiple email addresses at once and there is no limit to workspace size. {% hint style="warning" %} Ensure that the "Add to your workspace" button is toggled to "Yes" if you want people with your email domain to be invited into your workspace rather than just invited to use the Glue app. {% endhint %}
{% hint style="info" %} Anyone in the workspace can invite new members from the Create (+) button by selecting "Invite your team." {% endhint %} ## Remove Users from the Workspace * Search for the user you need to remove * Click the dropdown arrow that lists them as an admin or member * Select "Remove User" ## Enabling SAML-based Single Sign-On (SSO) Admins can connect any compatible identity provider—like Okta or Azure AD—to streamline authentication, automate user provisioning, and maintain full control over access. SSO is only available on our Enterprise plan. You can find SSO setup instructions [here](/for-admins/saml-sso). {% hint style="info" %} If your organization requires SSO for login, please contact the **Glue Support Team** about upgrading to the Enterprise plan. {% endhint %} # Group setup ## When to use groups Groups help organize threads and chats for **long-term collaboration**. Use groups to: * Align teams around **departments**, **teams, or long-term topics**. * Send messages to specific audiences (think of an email listserv). For short-term discussions, we recommend using threads instead of creating new groups. {% hint style="success" %} **Pro Tip:** Start small. You can always add more groups as your team grows or your needs evolve. Threads are perfect for handling temporary or one-off discussions without cluttering your workspace. {% endhint %} ## Recommended Use Cases for Groups ### Functional Teams Create a group for each department, managed team and office location. Any team that needs to be messaged regularly should have a group. Examples include: * Leadership * Product * Sales Operations * San Francisco Office ### **Working groups, long term projects, or special interest groups** For larger companies, it might make sense to set up groups for significant, long-running projects or groups of people who will work together and want an easy way to message the entire group. Groups can always be removed later once the project has completed. Examples include: * Cross functional project teams on multi-quarter projects * Interest groups or ERGs {% hint style="info" %} You can always edit the groups in your workspace, and you'll never lose important context because threads exist independently of a group. {% endhint %} ## Group organization for smaller companies For smaller companies, here are some recommendations we have from our own use of Glue at our company and from working with lots of other small startups. **Create groups for each distinct department** or work stream, even if the same people are in multiple groups. This helps compartmentalize work to reduce noise and keep threads organized. **Use threads to manage your projects**, and include the relevant groups on that thread. This way everyone can have visibility into projects and can contribute when needed, and you're not creating silo'ed groups for every project. Keep communication streamlined and accessible. ## Setting up Groups in your new Glue workspace When setting up your Glue workspace, it’s helpful to plan your group structure before inviting your entire company—especially for larger teams. #### Create core groups first: * Set up key groups that align with your organization’s high level departments and teams. * This ensures people have relevant groups to join as they learn to use Glue. This will also help avoid users spinning up too many new groups if they don't see the groups they need. #### Give your team guidance on when to use groups: * Establish a clear structure and provide guidelines for when and how new groups should be created. * Team members can create their own groups for smaller sub teams or interest groups. #### Add people to groups or let them join on their own: Add teammates to relevant groups or let them explore and add themselves to groups as needed, but make sure to let them know where to go look in the [Group Directory](broken://pages/MDoe7byeNtQ9q8sr2KsC). They will be able to see all group names and can join or request to join depending on the group type. * **Open Groups:** Users can join directly. * **Closed Groups:** Users must request to join and get approval from a group admin or workspace admin. {% hint style="info" %} For detailed instructions on creating groups, refer to the [Creating Groups](/groups/groups-overview#creating-a-new-group) documentation. {% endhint %} # Slack import Admins can bring your Slack channel data into Glue ## **Why Import Your Slack Data?** We highly recommend importing some Slack data as you set up your workspace so you can hit the ground running. Slack import is *optional* if you prefer to start from scratch. **Make the transition seamless for users:** Pre-populate Glue with relevant Groups and messages to speed up onboarding and usage. **Enhance Glue AI with company data**: With access to message history, Glue AI becomes more useful right from the start. {% hint style="info" %} Only admins can run a Slack import for the workspace. {% endhint %} ## **The basics of importing your slack data** 1. **Export your data** from Slack 2. **Download** the zip file Slack sends you via email 3. Upload the file in the **Slack Import tool** in Glue, which will guide you through the process 4. **Choose which channels** you want to bring over, and pick between a Thread or Group [Detailed instructions](#detailed-instructions-for-slack-import) can be found below.
Data included in the Slack export * Channels and their message history * Channel memberships
Data not included in the Slack export * Users * DMs * App Integrations * Workflows * Custom emojis\*\* \*\*There is a separate process for this from the Slack export file. See [detailed instructions](#custom-emoji-export-optional) below.
### How will my Slack channels map to Glue? You can pick and choose which Slack Channels to import, and they can be converted to a Glue Thread or a Group.
Slack Channel to Glue Thread * By default, Slack channels will be imported as named Glue threads. * These threads will be automatically archived so they are easily searchable, but not cluttering the inbox.
Slack Channel to Glue Group * Your most important channels (e.g. channels for specific departments or teams), can be imported as Groups. * Message history and slack threads will show up as chats and threads in the new Glue group. * Group membership will mirror the old channel membership, but no user invites will be sent until you're ready.
{% hint style="info" %} **User accounts are not created during the Slack import**, but the channel memberships are preserved in the corresponding Glue group. When a new user signs up, they will automatically see these Groups in their Glue account. {% endhint %} ## **Preparing for your migration** ### **Consider which channels you want to keep** * Determine which channels are the most critical to create into long term Groups. * The other channels you decide to import will be turned into archived Threads that can still be referenced, but won't be actively used. * While having some history imported from Slack is a great way to come into Glue with some starting data to both see how to use Glue, and be able to ask Glue AI questions, importing all of your Slack history would potentially create more clutter which is hopefully what you're coming over to Glue to avoid. It's a personal decision how much content to bring over, but be thoughtful about giving your team enough of a fresh start! ### **Understand data limitations** You can export your entire history from Slack, but the self service Slack import tool has a **file size limitation of 100 MB** at a time. We **recommend starting with the last 30 days of history** to test if you want to import more. #### **During your free trial** * We **recommend using the last 30 days of Slack history** so you can have an easier import process and still be able to test Glue. * We cannot offer custom imports during a free trial. #### **Glue customers** * If you need assistance uploading a larger amount of data after you've purchased a Glue subscription, you can reach out to or contact us in Glue. ## Detailed Instructions for Slack Import ### **Export your Slack data** 1. Go to your Slack data export page: [Slack Export](http://slack.com/services/export). * Navigate to the workspace settings. This can be accessed by clicking the dropdown next to the workspace and selecting “Tools & Settings”, then “Workspace Settings”. * On the settings page you will see a button on the top-right corner of the page labeled “Import/Export Data”. Click on it. 2. Select the Export tab. Choose a date range and click "Start Export." * We recommend exporting the last 30 days to get your most critical data off Slack. * This may take some time depending on your workspace size. You will receive a slack notification and an email once it is complete. * Once this is done, you can navigate back or just refresh the page, and you will see a download link. {% hint style="info" %} Private channels will not be exported. If you want to include these, make them public first before running the export. {% endhint %}

Select the Import/Export Data button in the upper righthand corner

{% hint style="warning" %} **Make sure to use the "Standard Export."** This is what you will upload to Glue. Do not use the "Channel audit export." {% endhint %} ### **Import Slack data to Glue** 1. Once you have the export zip file, navigate to your Workspace settings underneath your profile avatar at the top right hand of the screen. 2. Click your workspace and navigate to the **Advanced** tab. 3. **Click “Get started”** button in the Slack Import section. Glue will guide you through the upload process with instructions. 4. Drag & drop or choose your zip file to upload. 5. Select the Channels (or select all) you'd like to map over, and indicate any that you want to be a Group (the default option is a Thread). 6. Glue AI will message you about the status of your import! ✨ {% hint style="warning" %} **Reminder:** There is a 100 MB size limitation on self service Slack imports. {% endhint %}
# Custom emoji import Bring your customer emojis from Slack into Glue ## Custom emoji export (optional) Slack’s built-in data export doesn’t include custom emojis, so you’ll need to use a Chrome extension to export them. 1. **Install the Chrome extension** * Download the extension from this link: [Slack Custom Emoji Manager](https://chromewebstore.google.com/detail/slack-custom-emoji-manage/cgipifjpcbhdppbjjphmgkmmgbeaggpc). 2. **Navigate to Slack’s workspace customization page** * Open your Slack workspace. * Click the workspace menu, select **Tools & Settings**, then click **Customize Workspace**. 3. **Download your emojis** * With the Chrome extension installed, you’ll see a “Download All Emojis” button on the customization page. * Click the “Download All Emojis” button to download a zip file containing your custom emojis. 4. **Import into Glue** * Use the downloaded emoji zip file with the Glue CLI to import your custom emojis into Glue.
# Security Our data security and privacy measures ## Overview At Glue, our mission is to give you full autonomy over who has access to what data and when. Admins and thread creators can edit access to workspaces, groups, and threads at any time. Our data is encrypted at rest and in transit and we are constantly making improvements to our processes. You can request your data at any time. No message content or identifiable information is stored externally. You can access our [terms of service](https://glue.ai/terms) and [privacy policy](https://glue.ai/privacy) anytime. ## SOC 2 Type I Certified Glue is SOC 2 Type I certified, demonstrating our commitment to safeguarding customer data through formally documented and independently audited security controls. We are actively working towards our SOC 2 Type II certification. To request a copy of our SOC 2 Type I report, please contact . ## Contact us Please email if you have any questions or requests. # Billing ## Understanding Glue's billing * You are charged for **each member** of your workspace. * You are **not charged** for: * External users (e.g., contractors or clients) added to groups or threads who are **not workspace members**. Billing updates automatically when you add or remove users. * **Monthly plans**: Charges adjust on the next billing cycle. * **Annual plans**: Credits are applied for removed users in the following billing cycle. ## Glue Plan Options Glue currently offers three plan options: | Plan Type | Price | Features | | -------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Startup** |

$6/user/month for annual plan
$7/user/month for monthly

|

First 5 users free​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‌​​‌‌‌‍‌‍​​‍‌‍‌‍‌‍​‍​​​​‌‌‍​‌‌‍‌‌​​​‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‌​​‌‌‌‍‌‍​​‍‌‍‌‍‌‍​‍​​​​‌‌‍​‌‌‍‌‌​​​‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Up to 5 groups​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‌‌​‍‌‌‍​‍​‌‌‍​‌‌‍‌‌​‌‍​‌​​‌​​‍‌‍‌​‌‍​‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‌‌​‍‌‌‍​‍​‌‌‍​‌‌‍‌‌​‌‍​‌​​‌​​‍‌‍‌​‌‍​‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Unlimited threads​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‌‌‍​‌‌‍​‌​‍​‌‍​‌‌‍​​‌​​‌‌‍​‌​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‌‌‍​‌‌‍​‌​‍​‌‍​‌‌‍​​‌​​‌‌‍​‌​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Unlimited message history​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍‌‌‌‍‌​‌‍​​​​‌‍‌‍​‌‍‌‍‌‌​​​‌‍​‌‍​‌‍​​‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍‌‌‌‍‌​‌‍​​​​‌‍‌‍​‌‍‌‍‌‌​​​‌‍​‌‍​‌‍​​‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Unlimited apps & webhooks​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍‌‍​‌‍​‍​​‌‌​‌‍​​‌​‌‍‌‍‌‌​‍‌​‍‌​‌‍​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍‌‍​‌‍​‍​​‌‌​‌‍​​‌​‌‍‌‍‌‌​‍‌​‍‌​‌‍​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Unlimited external users​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​‌​​​‍‌‍​‍​​​​​‍‌‍‌‌​​​‌​​​​‌​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​‌​​​‍‌‍​‍​​​​​‍‌‍‌‌​​​‌​​​​‌​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Open-source AI models​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍​‍‌‌‍‌​​‌​​​​​‌‌‍​‍‌‍​‍​‌​‌‍​‍‌‍​‍‌‍‌​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍​‍‌‌‍‌​​‌​​​​​‌‌‍​‍‌‍​‍​‌​‌‍​‍‌‍​‍‌‍‌​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Public API access​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​​‌‌‍​‌‌‍​​‌​​​‍‌‍‌‌​​​‌‍‌‍​‌​‌‍​‌​‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‌​​‌‍‌‍​​‌‌‍​‌‌‍​‌​​‍​​‌‍​‌‌‍​‍‌‍‌​​‍‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​​‌‌‍​‌‌‍​​‌​​​‍‌‍‌‌​​​‌‍‌‍​‌​‌‍​‌​‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌

| | **Business** |

$12/user/month for annual plan
$14/user/month for monthly

|

All Startup features +​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‍‌​​‌‍‌‌‌‍​‍‌‍‌‌​‌​‌‍​‌​‌‍‌‍​‍​‌‌​​‌‌‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‍‌​​‌‍‌‌‌‍​‍‌‍‌‌​‌​‌‍​‌​‌‍‌‍​‍​‌‌​​‌‌‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Unlimited groups​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‍​​‍‌​‌​‌‍​‍‌‍‌‍​‌‌​‍​​‌​​‍​‌​​​‌‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‍​​‍‌​‌​‌‍​‍‌‍‌‍​‌‌​‍​​‌​​‍​‌​​​‌‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Data imports up to 100mb​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍​‌‌‌‍​​​​‌‌‍‌‌​‌‌​‌‌‍​‌‌‍‌‍‌‍‌​​​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍​‌‌‌‍​​​​‌‌‍‌‌​‌‌​‌‌‍​‌‌‍‌‍‌‍‌​​​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Multiple admins​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​​‌‌​‍​​‌​​​‍‌‍‌‌‌‍‌‍​‍‌​​‍‌‍‌‍​​​‌‍‌​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​​‌‌​‍​​‌​​​‍‌‍‌‌‌‍‌‍​‍‌​​‍‌‍‌‍​​​‌‍‌​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Premium AI models:​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​​‍‌​‌​​‌‌​​‍​‌‍‌‍​‌‌‍​‌‌‍‌‍​​​‌​‌‍‌​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​‍‌‍‌‌​‍​​‍​​​‌‍‌‍​‍​​‌‌​‌​‌‍‌‍​‌‍‌‍‌‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍​​‍‌​‌​​‌‌​​‍​‌‍‌‍​‌‌‍​‌‌‍‌‍​​​‌​‌‍‌​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌

| | **Enterprise** | Contact us |

All Business features +​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​​​‍​​‌‌​​​‌‍​‌​‌​‌‌​‌‍​‌‍​‍‌​‌​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​​​‍​​‌‌​​​‌‍​‌​‌​‌‌​‌‍​‌‍​‍‌​‌​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Unlimited data import​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‍‌‌‍‌‍​‌​‌‍‌‍‌‍‌‍‌​​​‍​‌‍‌‍​‍‌‍​‌​‌‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‍‌‌‍‌‍​‌​‌‍‌‍‌‍‌‍‌​​​‍​‌‍‌‍​‍‌‍​‌​‌‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
SAML & SCIM capabilities​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‌‌‍‌‌‌‍‌​​‍​​​​‌‍​​‍‌‌‍‌​​‌‌​‍‌​‍‌​​‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​‌‌‍‌‌‌‍‌​​‍​​​​‌‍​​‍‌‌‍‌​​‌‌​‍‌​‍‌​​‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
Priority support​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍‌‌​‍‌​​‌​​‍​​‌‍‌​​‌‌​‌​​‌​​‌​‌‍​‌​‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍‌‍‌‌​‍‌​​‌​​‍​​‌‍‌​​‌‌​‌​​‌​​‌​‌‍​‌​‍​​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌
White glove onboarding​​​​‌‍​‍​‍‌‍‌​‍‌‍‍‌‌‍‌‌‍‍‌‌‍‍​‍​‍​‍‍​‍​‍‌​‌‍​‌‌‍‍‌‍‍‌‌‌​‌‍‌​‍‍‌‍‍‌‌‍​‍​‍​‍​​‍​‍‌‍‍​‌​‍‌‍‌‌‌‍‌‍​‍​‍​‍‍​‍​‍​‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‍‌‌‍‍‌‌​‌‍‌‌‌‍‍‌‌​​‍‌‍‌‌‌‍‌​‌‍‍‌‌‌​​‍‌‍‌‌‍‌‍‌​‌‍‌‌​‌‌​​‌​‍‌‍‌‌‌​‌‍‌‌‌‍‍‌‌​‌‍​‌‌‌​‌‍‍‌‌‍‌‍‍​‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‍​‍​​‌‌‍​‌‌‍‌‍​‍​​​‌​​‌‍​‌‌‍‌‍‌‍‌​​​‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‌‍​‍‌‍​‌‌​‌‍‌‌‌‌‌‌‌​‍‌‍​​‌​‍‌‌​​‍‌​‌‍‌​‌‌​‌‌‌‌‍‌​‌‍‍‌‌‍​‍‌‍‌‍‍‌‌‍‌​​‌‌‌‌‌‍‍​‌‍‌‌‌‍‍​‌‍‍‌‌‍​‌‌‍‍‌‍​‌‍​‌​​‌​‌​​​‌‍‌‍‌‌​‌‍‍‌‌‍​‌‌‌‍‌‌‌​​‌‍‍‌​​​‌‌‌‍​‍‌‍‌‌​‌‍‌‌​​‌‍‌‌​‌‌​​‌​‍‌‍‍‌‌‍​‌‍‍‌‌‍‍‌‍‌​‍‌‍‌​​‌‍​‌‌‌​‌‍‍​​‌‌‌​‌‍‍‌‌‍‌‌‌​‍‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‌​​‌‌‍​‍‌‍​‍​‍‌​​​​​‍‌‍​‍​‌​‌‌​‍​‌‍‌‍​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‍‌‍‌‍‌‌‌‍​‌‌‌​‌‌‌‌​‍‌‍‌‌‌​​‍‌‌​‌‌‌​​‍‌‌‌‍‍‌‍‌‌‌‍‌​‍‌‌​​‌​‌​​‍‌‌​​‌​‌​​‍‌‌​​‍​​‍​​‍​‍​​‌‌‍​‌‌‍‌‍​‍​​​‌​​‌‍​‌‌‍‌‍‌‍‌​​​‌​‍‌‌​​‍​​‍​‍‌‌​‌‌‌​‌​​‍‍‌‌​‌‍‌‌‌‍​‌‌​​‍‌‍‌​​‌‍‌‌‌​‍‌​‌​​‌‍‌‌‌‍​‌‌​‌‍‍‌‌‌‍‌‍‌‌​‌‌​​‌‌‌‌‍​‍‌‍​‌‍‍‌‌​‌‍‍​‌‍‌‌‌‍‌​​‍​‍‌‌

| ➡️ See [glue.ai/pricing](https://glue.ai/pricing) for the most current pricing. {% hint style="info" %} ❗ Glue does **not** currently offer a freemium plan. However, all new accounts start with a 30-day free trial, and the Startup plan includes the first 5 users for free. {% endhint %} ## Accessing Your Billing Information You can only view and manage billing from a **web browser**. Billing settings are not available in the mobile or desktop apps. [This link](https://app.glue.ai/?action=upgrade_workspace) should take you straight to your billing settings in a web browser, if you are a workspace admin.
How to View Your Billing Information 1. **Log in to Glue** using a web browser. 2. Click your **workspace name and logo** in the upper left corner. 3. Select your **workspace name** to open **Workspace Settings**. 4. Go to the **Billing** tab.
Making Changes to Your Subscription To update payment info, switch plans, or cancel your subscription: 1. Follow the [steps to go to the **Billing tab**.](#how-to-view-your-billing) 2. Click **"Manage Billing"**. 3. This opens the Stripe customer portal. From here, you can: * Update payment method * Change billing address * Switch between plan types * Cancel your subscription

Find the Billing tab in your Workspace Settings in the web app

Stripe billing portal where you can make changes to your subscription

*** ## Managing Users and Charges ### Adding Users If you add users mid-cycle: * **Monthly plans**: You’ll be billed for those users at the start of the next month. * **Annual plans**: You’ll be billed a **prorated amount** for each new user through the end of your annual term. **Example:**\ If your annual plan ends in March and you add a user in January, you’ll only be billed for **2 months** for that user. > 🧑‍💼 Manage users under **Workspace Settings > Members**. *** ## Canceling Your Subscription ### For Self-Serve Plans (Signed up in Glue) You can cancel at any time to avoid charges for the next billing period. 1. Log in on a browser and go to [**Billing** in your **Workspace Settings**.](#how-to-view-your-billing-information) 2. Click **"Manage Billing"**. 3. In the Stripe portal, click **"Cancel subscription"** and follow the prompts. 4. Make sure you see a **cancellation confirmation** message. > ⚠️ Refunds are not available for unused time during a billing cycle. ### For Custom Contracts If you are on a **custom enterprise contract**, please contact your Glue sales representative to cancel. # Free trial Glue offers a **30-day free trial** of our Business plan when you first create an account—no credit card required. This allows you to explore Glue with your full team before deciding to subscribe. * **Your trial starts immediately** when you sign up. * **No payment details are required** to begin. * **Unlimited users** can be added during your trial, so your entire team can experience Glue. * We recommend centralizing all your communication into Glue during your trial to really see the benefit. ## How to Upgrade During Your Trial You can upgrade at any time during your trial from your billing settings. **To access billing settings:** * Click the **“Manage Workspace”** button in any trial-related pop-up, **or** * Click the alert at the top of the screen that shows how many days are left in your trial to bring up that pop up, **or** * Log in to Glue in a browser, and go to the billing section of your workspace settings, [instructions here.](/for-admins/billing#accessing-your-billing-information) All of these options will get you to the billing section of your workspace settings where you can select a plan and enter your credit card information.
Trial Countdown and Reminders During your trial, you’ll see a countdown banner at the top of your screen indicating how many days you have left. * **Pop-up reminders** appear when you have: * **7 days remaining** * **1 day remaining** These help ensure you have time to upgrade if you wish to continue using Glue.
## **What happens at the end of the trial period?** At the end of your 30-day trial, you’ll be prompted to upgrade and enter your payment details, if you choose. You will need to upgrade within 7 days before access starts to become limited. **If you have less than 5 users in your workspace,** you will be able to continue using Glue for free on our Startup plan until you add your 6th user. You will need to have no more than 5 groups and 1 admin to qualify. You will automatically convert onto our startup plan with no action taken, if your workspace meets the criteria for the free version of the Startup plan. **If you do not want to move forward with Glue, no action is needed** on your end. You do not need to cancel the trial since no subscription has been created.
What happens to the trial workspace if you do not upgrade No action is needed if you decide not to subscribe: * **Day 0** (Trial ends): No automatic subscription is created, a pop-up lets you know the trial ended. * **Day 7**: Your workspace becomes **read-only**. A pop-up lets you know the date your workspace will be deactivated. * **Day 37 (30 days after read-only)**: Your workspace is **deactivated** and all content is **permanently deleted**.
What happens if I change my mind and want to upgrade after the trial ends? You can still upgrade and reactivate your workspace at any point before it is deleted, 37 days after the trial end date. * Use the **“Manage Workspace”** button in the login pop-up, **or** * Click any of the top alerts like: * “Upgrade Now” * “Workspace limited” This will reopen the upgrade pop-up, where you can click the "manage workspace" button and be taken to your billing settings in the browser. In your billing settings, choose between a monthly and annual plan and then click "Sign up" to be taken to the payment page in Stripe.
Deleting your workspace manually If you'd prefer to delete your workspace before the automatic deactivation, you can do this in your **Workspace Settings**.\ [Read more about deleting your workspace →](/workspaces/workspace-settings#how-to-delete-your-workspace-manually)
# SAML SSO Single Sign-on gives members access to Glue through an identity provider (IDP) of your choice. ## SSO Overview Single Sign-On is only included in our Enterprise plan. If you are interested in upgrading, please reach out to ## Set up SAML single sign-on ### Step 1: Enable SSO for your workspace First, you'll need to enable SSO for your workspace. To do so, open your Glue Workspace settings page, and click the "Enable Single sign-on" button to enable SSO.
### Step 2: Configure your identity provider for SAML Once enabled, click the "Configure SSO" button to begin configuring your identity provider.
In this window, select your identity provider, and follow the instructions to set up the connection between your IDP and Glue. Each identity provider will have a different set of instructions — follow the detailed configuration steps in the opened window. {% hint style="info" %} Be sure to complete every configuration step before closing the window. If you accidentally close the window, click the "Manage SSO" button to configure the connection again. {% endhint %}
### Step 3: Confirm Connection Once connected, you should see a screen confirming the activated connection in both the window and in Glue.
If the connection was successful, you will see the Glue Setting status update to "SSO Configured", as seen below!
## What to expect next Once SSO is set up, users logging into Glue will be asked to log in via your IDP sign-in page before they can access Glue. If users are logging in for the first time, users will be prompted to set up their Glue profiles after authenticating. {% hint style="info" %} Note: To keep user management simple, Glue supports the SCIM provisioning standard. {% endhint %} # SCIM Glue supports member provisioning with the System for Cross-domain Identity Management (SCIM) standard. ## SCIM Overview With SCIM enabled, user accounts can be automatically created, updated, and suspended based on your IDP settings—eliminating the need for manual account management in Glue. This integration helps ensure that your team's access stays in sync with your organization’s directory. {% hint style="info" %} SCIM is only included in our Enterprise plan. If you are interested in upgrading, please reach out to {% endhint %} ## Set up SCIM ### Step 1: Enabling SCIM for your workspace First, let's enable SCIM in your Glue workspace to start the configuration. 1. Navigate to Workspace Settings by clicking on your workspace icon in Glue. 2. Navigate to **Single sign-on.** 3. Toggle the option to enable SCIM 4. Once enabled, click the "Configure SCIM" button to begin configuring your identity provider. ### Step 2: Configure your identity provider for SCIM In this window, select your identity provider, and follow the instructions to set up the connection between your IDP and Glue. If you've set up SAML already, these steps will utilize the same application you created there. ### Step 3: Confirm Connection Once connected, you should see a screen confirming the activated connection in both the window and in Glue. ![](/files/GP43ePUkizjIfmfws6pr) ## What to expect next Now that SCIM is set up, Glue will automatically stay in sync with your identity provider. You won’t need to manage users in Glue anymore—just make changes in your identity provider, and the integration will take care of the rest. If users lose access in the identity provider, their Glue access and sessions will automatically end. # Glue launch messaging templates Customize these messages to fit your team's communication style. The portions that are in **\[bolded brackets]** are meant to be edited by you before sending. *** ## **Pre-Launch: send via email** Hi Team, I’m excited to announce that we’re moving to Glue as our new internal messaging platform! The Glue app organizes conversations into **threads** and people into **groups**. **\[Customize this to why you chose Glue – and include any anecdotes if people have been piloting Glue. Example: We have been testing Glue with a small team, and have loved how easy it is to use Glue threads to keep conversations focused, and avoid the noise of other channel-based chat tools.]** Here’s a sneak peek at what you can expect: * **Threads** keep discussions on topic and easy to find * **Groups** organize threads and people around a team or project * **Personalized inbox** focuses on the messages that are important to you * **AI-assisted conversations!** Chat with AI on your own or with your teammates **Launch timing** **\[Customize this to alert your team to when they will use Glue. Example: Stay tuned for more updates, and get ready to start using Glue in the coming weeks! We will be We are officially launching on December 10th, so follow the steps to create your account between now and then.]** **How to get started** 1. **Sign up:** Visit **\[Glue URL -** [**you can find your invite URL in workspace settings**](/for-admins/manage-members)**]** and create your account using your work email. 2. **Install Glue:** Download the Glue apps for desktop ([Mac](https://apps.apple.com/us/app/glue-groups/id1559943932) and [Windows](https://apps.microsoft.com/detail/9p0bfrbfpcd9)) and mobile ([iPhone](https://apps.apple.com/us/app/glue-smarter-work-chat/id1559943932) and [Android](https://play.google.com/store/apps/details?id=com.gluegroups.glue)) 3. **Learn More:** Check out the [Getting Started Guide](/get-started/getting-started-for-users) and [Glue’s Help Documentation](https://docs.glue.ai/) to learn more! **Questions or Feedback?** If you have questions about how to do something in Glue, the easiest thing to do is ask @Glue AI! It’s trained on Glue’s help docs. If you have a question specific to how we use Glue, or have feedback for us, please reach out to **\[Glue Feedback Group – optional to create a group like this for people to ask questions]** or email **\[email alias for your internal support].** Let’s get ready to make our work more seamless and efficient with Glue! **\[Your name]** *** ## At Launch: send via Glue Thread **Group:** your General group (so everyone sees the message) **Thread Name:** Welcome to Glue! We’re officially up and running on Glue! 🎉 Here’s what to keep in mind as you get started: * Always consider **threads** first as the primary way to start a conversation around a short term topic — instead of sending chats or creating a new group * Check out our **groups** to see which ones you want to join! * Explore your **inbox** and learn some [tips to keep your inbox focused](/inbox/inbox#thread-inbox-actions) * Try out Glue AI — it’s here to help with ideas, summaries, and more! Have questions? Ask Glue AI or post in **\[Feedback Group Name]**. Excited to work with you all in Glue! # Slack Connect Connect your Glue account to your Slack Connect channels ## Overview You can now **integrate Slack Connect channels into Glue**, allowing you to continue conversations with clients, partners, and vendors who are inside Slack without ever leaving Glue. This integration is included in your subscription at no extra cost. **Some key points to remember:** * With this integration, you can bring in Slack Connect channels as Glue “external groups” and participate from Glue. * You can already message other Glue users outside your workspace for free. External users can be invited to message with you by using their email address to send them a thread or add them to a group. They will receive an email to create a free Glue account, and they do **not** count toward your subscription cost. *** ## How It Works #### Sync behavior across the apps | **Slack Connect Feature** | **How it integrates with Glue** | Notes / Limitations | | ------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Slack Connect Channel | ✅ External Glue Group | Shown under an “External Groups” section, with a **#** icon and the Slack domain next to the group name | | Message | ✅ Two‑way sync | Messages and files sync in \~1 second | | Reply in thread | ✅ Glue Thread |

Replying in thread in Slack creates a thread in Glue and vice versa
\*Due to slack limitations, the Glue thread cannot have any other recipients (groups or people) on it

| | Mentions | ✅ Limited to mentions of users in that Slack channel | You **cannot** mention users in Slack who are not in the workspace or not part of the Slack Connect channel; and you **cannot** mention Glue groups inside Slack channels | | Emoji reactions | ✅ Two-way sync | | | File sharing | ✅ Two‑way sync | File attachments sync in both directions | | Direct messages (DMs) | ❌ | You cannot DM Slack users from within Glue. If you would like to send DMs you should message them using their email address and they can create a free Glue account! | | Slack user avatar | ✅ Displayed | Users from external Slack workspaces will show their Slack team avatar in the group header and on their message icon | | Channel membership | ✅ | All membership info is imported; a Slack badge appears next to the user’s name | | User profile info | ✅ Partial |

✅ Glue shows name, title, and domain
❌ Slack status messages or online indicator are not brought over

| {% hint style="info" %} Because of Slack’s API limitations, a Glue thread sent to a Slack Connect channel can only address that one channel (i.e. no multi‑group or multi‑user threads). Glue normally supports multi‑recipient threads, but not in this context. {% endhint %} #### Limitations & Gotchas * When using a Glue thread in one of these shared Slack connect channels, you cannot reply to the thread with another thread. You will receive an error message. Only message replies are supported. * You cannot edit group membership or rename/delete the group from within Glue — those actions must be done in Slack. * You cannot mention Slack groups or external users outside the Slack Connect channel. * Threads can only be sent to the one Slack Connect channel, they cannot be multi-addressed to other Glue groups, people or slack channels. There is currently **no limit** on the number of Slack Connect channels you can import and **no known message rate limits** (sync usually completes in ≤1 second). * **Private Channels:** To sync message history from private Slack channels, you must add the **@Glue** app user to those channels. Without adding @Glue to the private channel, message history will not be synced. *** ## Setup Requirements | Requirement | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------ | | Glue plan | All Glue plans include the Slack Connect integration | | Slack plan | Any paid Slack plan works — no special tier required | | Slack licenses | Users must keep their Slack license active to maintain Slack Connect access | | Permissions & roles | To set this up for your workspace, you will need admin access to both Glue and Slack | | User-level authorization | Each user who wants to use Slack Connect channels in Glue must authorize Slack Connect in their Glue workspace settings. | *** ## Setup Guide ### Enabling Slack Connect for your Glue Workspace Admins can set up the Slack Connect integration for their workspace. **You will start in Glue, and follow a guided wizard.** In case you get stuck on any step or need any additional help, you can reference the steps below. Each step is aligned with the number that shows up in the wizard. {% hint style="info" %} You will need to be switching back and forth between Glue and Slack while you set this up, so we recommend having both open in browsers that you can have side by side {% endhint %} #### Step 0: In Glue: Initiate the Slack Connect setup wizard 1. Go to **Workspace Settings** in Glue by clicking on your workspace name in the upper left, and then choosing the workspace you want to set this up for. 2. Click the **Slack Connect** tab. 3. Click **“Get Started”** to launch the integration wizard. 4. Review the overview of the process and then click **“I’m ready”** #### Step 1: In Slack: Create a Slack app 1. Review the Glue wizard instructions and then click next to bring up Glue’s app manifest (you will need this soon). 2. Log in to Slack and go to **Your Apps** (via [api.slack.com/apps](https://api.slack.com/apps)). 3. Click **“Create an App”** → **“From a manifest”**. 4. Choose your Slack workspace and click **Next**. 5. You will see a JSON code manifest that needs to be replaced with the manifest from Glue. #### Step 2: In Glue + Slack: Update the app manifest 1. Copy the **Glue app manifest JSON** (provided by Glue in the wizard). 2. Go back into Slack and paste in the JSON manifest. 3. In Slack, click **“Next”** → **“Create”**. 4. Now you have a Slack app! Next step is to connect it to Glue. #### Step 3: In Glue + Slack: Copy Slack app credentials into Glue 1. In the Slack app’s **Basic Information** page, you will need to copy these values one by one and paste them into Glue. For any value that is hidden, you will need to click “show” before you can copy it. 1. App ID 2. Client ID 3. Client Secret 4. Signing Secret 2. In Glue’s wizard, paste those credentials into the appropriate fields. 3. Click **“save and connect.”** #### Step 4: In Slack: Verify that Glue can receive messages from Slack 1. Go back to Slack and Find the tab on the left panel that says “**Event Subscriptions”** 2. Click **Retry** to verify the webhook. #### Step 5: In Glue + Slack: Authorize the app 1. In Glue, you will now see a status update that the connection was successful. Click **“next.”** 2. Click the “Authorize in Slack” button to authorize the connection between your Glue account and Slack account. This is the step that all users will need to take to authorize their accounts. 3. You will be directed to a Slack authorization page, click **“allow.”** 4. Back in Glue, you will see a confirmation that you are connected and you can click **“Done.”** #### All set! Confirm & Test 1. You will now see your configuration settings under Slack Connect settings in Glue. 2. Go back to your Glue inbox and you will now see Slack Connect channels that you belong to under External Groups in Glue. 1. Message history will not show up in these groups, but any new messages will start to sync right away. 3. Remind all of your workspace users to individually authorize their Glue accounts to use Slack Connect. ### Enabling Slack Connect as a user 1. Go to **Workspace Settings** in Glue by clicking on your workspace name in the upper left, and then choosing the workspace you want to connect with Slack. 2. Click the **Slack Connect** tab. 3. Click “Sign in” 4. You will be directed to a Slack authorization page, click **“allow.”** 5. You will now be able to see all Slack Connect channels you belong to under your Glue Groups. *** ## Removing / Disabling Slack Connect #### As an Individual User 1. Navigate to **Workspace Settings → Slack Connect**. 2. Click **“Sign Out”** to revoke your personal Slack authorization. #### At the Workspace / Admin Level 1. In Glue’s **Workspace Settings → Slack Connect**, click **“Remove”** (only available to admins). 2. After removal, go to Slack → **Your Apps** → find the Glue integration → click **Delete App**. * **Important:** Always remove the integration in Glue **before** deleting the Slack app to avoid a broken state. *** ## FAQ & Troubleshooting #### Should I delete the Slack app directly from Slack when removing integration? No — you must first remove the Slack Connect integration from Glue. Deleting the Slack app prematurely can leave Glue in a broken state. #### I made a mistake during setup. What do I do? 1. Remove Slack Connect from Glue (admin step). 2. Delete the custom Slack app. 3. Re-run the setup wizard from scratch. #### I don’t see a Slack Connect tab / option in my settings. Confirm you have Glue workspace admin permissions to set up the Slack Connect integration. Once the Slack Connect integration is set up, all users in the workspace will be able to authorize their account to access it. #### Why can’t I mention some users or groups? Slack’s API only permits mentions to users who are members of the Slack Connect channel. Mentions of external users or Slack groups are not supported. #### What happens to threads with multiple recipients? Because Slack doesn’t allow threads to span multiple channels or users, Glue will restrict such threads to only the Slack Connect channel itself. # Integrations overview Glue is growing quickly, and we’re actively working on expanding our integrations library! If you don't see the app you want to integrate with available in our pre-built integration options, let us know and we'll do our best to add it. Alternatively, you can easily setup your own lightweight [custom integration](#custom-integrations). {% hint style="success" %} Looking for the API docs? Check our [Glue Developer Docs here](https://docs.glue.ai/developers/). {% endhint %} *** ## **Pre-Built Integrations** Explore our list of integrations and [MCP servers](/integrations/mcp-servers) by navigating to the Apps section of your inbox. When you select one of the apps you will be able to see what you can install — the app integration and/or an MCP Server. Our pre-built integrations allow you to do things like: * Push updates into Glue via messages or threads * Get rich link previews, out of the box, with a single click * Some integrations — like [GitHub](/integrations/github) and [Linear](/integrations/linear) — also support **auto-subscribe**: when you share a link to an issue or PR in a thread, the thread automatically receives system messages whenever that item's status changes. Click into each app to read the full description of what it can do.
Continue here to [#add-integrations-to-your-glue-workspace](#add-integrations-to-your-glue-workspace "mention") ## Custom Integrations Don’t see the integration you need? We have no-code and low-code options, as well as a public API to meet your customization needs. * [Zapier](/integrations/zapier-apps): Offers a huge library of plug-and-play integrations for easy setup. * [Webhooks](/integrations/integrations-overview/webhooks): Requires more technical knowledge, but provides greater flexibility. * [Public API:](https://docs.glue.ai/developers) Build your own fully customized app. Highest level of effort, highest reward!
Stay tuned as we continue to enhance Glue’s integration options! # Add integrations to your Glue Workspace For most integrations, the setup is just sharing a link. For integrations that automate configured notifications to a specific thread or group, it's as simple as adding the integration to the thread. ### Add an integration by sharing a link When you share a link from a supported app in a thread, Glue automatically adds the integration to your workspace. From there, anyone in the workspace can use it. The first time you share a link from an app, you may be asked to authorize it for your own account. Click **Authorize** and follow the prompts. After that, links from the app will unfurl with rich previews in your messages. This includes: * [GitHub](/integrations/github) * [Linear](/integrations/linear) * [Jira](/integrations/jira) * [Notion](/integrations/notion) {% hint style="info" %} You don't need to install anything before sharing the link — Glue handles the workspace setup for you. {% endhint %} ### Add an app to a group or thread for automations Some apps can do more than show link previews — they can create new threads or post messages based on activity in the connected tool. These include: * [GitHub](/integrations/github) * [Typeform](/integrations/typeform) * [ClickUp](/integrations/clickup) * [Monday.com](/integrations/monday.com) * [CircleCI](/integrations/circleci) * [Sentry](/integrations/sentry) To set up automations, first, add the app to the workspace, and add the app to the specific group or thread where you want them to run.
Add the app to your workspace * ✅ Anyone in the workspace can do this. * Go to the Directory section of your inbox and find the Apps tab * Find the app you want to add and click it. * Apps already added will show an "Added" badge. If already added, **skip to step 2.** * Your available workspaces will show up and you can choose where to add the App or MCP Server (availability of these integration types depends on the specific app). * If there is a pre-built integration available, you will see the option to add an App → press the **App + button** and it will be added to your workspace in one click.
{% hint style="info" %} Workspace admins can also add integrations directly from workspace settings. {% endhint %} {% tabs %} {% tab title="➕ Add an app to a group" %} * You must be a **group admin** or **workspace admin**. * Go to **Group Settings → Apps** tab. * Click **Add** next to the app. * Follow any authentication prompts.
{% endtab %} {% tab title="➕ Add an app to a thread" %} * Any thread member can do this. * Go to **Thread Settings → Apps** tab. * Click **Add** next to the app. * Follow any authentication prompts. {% endtab %} {% endtabs %} ### Per-app setup details Some apps are available out of the box, and are available via special menu actions. For specific functionality on each one, see its page: * [Google Drive](/integrations/google-drive) * [Google Meet](/integrations/google-meet) * [Zoom](/integrations/zoom) * [Giphy](/integrations/giphy) {% hint style="info" %} Please refer to the documentation for the specific app you want to set up to see any additional instructions about connecting and authenticating the app. {% endhint %} # Manage your integrations ## Removing an integration from your workspace 1. In Glue, navigate to the **Apps** section of your inbox. 2. Locate and select the app you want to remove. 3. If the app has already been installed in a workpsace, there will be a gear icon instead of a plus sign. Click the app button for the workspace you'd like to remove the app from. 4. A pop up will open. Click **Remove From Workspace.**
#### Removing Custom Apps Because Custom Apps are only available per workspace, these are located in your workspace settings. 1. In Glue, navigate to your workspace settings in the top left corner of your Glue window. 2. Click on Apps. 3. Locate and click on your custom app or webhook. 4. Click "Delete Webhook" or "Delete App" # App Events When you share a link from a connected app in Glue, the thread automatically stays in sync as that work moves forward. No extra setup required — just share the link, and Glue handles the rest. ### Supported apps [GitHub](https://docs.glue.ai/integrations/github) · [Linear](https://docs.glue.ai/integrations/linear) · [Jira](https://docs.glue.ai/integrations/jira) · [Notion](https://docs.glue.ai/integrations/notion) · [Sentry](https://docs.glue.ai/integrations/sentry) ### How it works 1. Paste a link from a connected app into a Glue message 2. A link preview card auto-generates below your text 3. Send the message with the card attached — the thread is now subscribed to events from that specific linked object 4. Status messages appear in the thread as the work progresses, without badging you

Send the message with the preview card attached to subscribe the thread to app events

### What updates look like Updates appear as system messages — visually distinct from regular user messages so you can scan what changed at a glance. A few examples of what you might see: * *PR #4421 merged by fyang* * *Linear issue API-1594 status changed to Done* * *Sentry alert resolved* The preview card itself also stays current, reflecting the latest status in real time.
### Managing app event subscriptions **Don't want to subscribe?** Click the X on the preview card before sending to remove it. The message will send without subscribing the thread. **Want to stop updates later?** Open the resource sidebar, click the ellipsis (•••) next to the specific link, and select **Stop updates**. Any thread member can do this at any time.
### App-specific details Each integration page covers which events are supported for that app. * [GitHub](https://docs.glue.ai/integrations/github) * [Linear](https://docs.glue.ai/integrations/linear) * [Jira](https://docs.glue.ai/integrations/jira) * [Notion](https://docs.glue.ai/integrations/notion) * [Sentry](https://docs.glue.ai/integrations/sentry) # Webhooks ### Overview Webhooks allow you to send messages and create threads inside of Glue by making a simple POST to the webhook endpoint. Here is a basic example that sends a message to the group chat for the group with ID `grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk`. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "text": "New bug reported!" }' \ "https://app.gluegroups.com/webhook/wbh_123.../456..." ```
### Create a webhook In Glue, navigate to the **Apps** section of the workspace settings. Locate **Webhook** in the list and click **Add**. Enter a name and description, and then click **Create**. After creating, you can see and copy the URL for the webhook. ### Obtain a target ID In order to send a webhook, you'll need the ID of a group or thread. To do this, navigate to the appropriate group or thread, open the menu, and then select **Copy share link**. Paste the link and then look for an identifier in the URL. Group IDs start with `grp_...` and thread IDs start with `thr_...` If you are using the app from your browser, you can also look for these values in the URL bar. Note that at times, multiple IDs may be present depending on what you're viewing. In this case, you can see the group ID of `grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk` in the following URL: {% code overflow="wrap" %} ``` https://app.gluegroups.com/grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk?t=Chat ``` {% endcode %} Use this value in the `target` field of your webhook payload. ### Specify the target in the URL If you can't control the body of the request — for example, when pasting a webhook URL into a third-party tool like an alerting, monitoring, or deployment service — you can put the target directly in the webhook URL as a query parameter: ``` https://app.gluegroups.com/webhook/wbh_123.../456...?target=grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk ``` When `target` is included in the URL, you can leave it out of the body. The webhook will send to the thread or group identified by the query parameter. {% hint style="info" %} If `target` is present in both the URL and the body, the value in the body wins. {% endhint %} This makes it easy to drop a Glue webhook URL into any "paste a webhook URL here" integration without needing to customize the request body. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "text": "Deploy finished!" }' \ "https://app.gluegroups.com/webhook/wbh_123.../456...?target=grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk" ``` ### Webhook payload Here are the fields that you can send to the webhook endpoint. These fields should be sent as JSON with Content-Type `application/json` .
FieldDescription
textRequired. The text of the message to send. By default, this is treated as markdown.
target

Required, unless you specify the target as a query parameter on the webhook URL (see Specify the target in the URL). The ID of a thread or group to send to.

For a group, a message will be sent to the chat unless a threadSubject is specific - in this case a thread will be created in the group instead.

For a thread, a message will be sent to the thread. When specifying a thread target, you cannot create threads by specifying a threadSubject.

Note: For the workspace wide, "General" group, the workspace id (wks_...) functions as the group ID. Use the full ID including "wks_".

threadSubject

If specified, a thread will be created instead of just sending a message.

The target must be a group if a subject is specified.

uniqueBySpecify a value here to be able to update this message after it is created. If you call the webhook again with the same value, it will update the existing message instead of generating a new one.

The uniqueBy value should be unique for the the thread or chat that the message is sent to.
threadByIf specified, the webhook will send follow up messages to created threads with the same value. The first message will create the thread and then the following messages will be appending to that thread.
### Examples At a minimum, you must specify a `target` and `text` to send a message via a webhook. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "thr_2hTJ4DGsxUAeEhKOyJ2PMePFL0c", "text": "New bug reported!" }' \ "https://app.glue.ai/webhook/wbh_123.../456..." ```
The additional examples below demonstrate more advanced functionality.
Example: Sending and updating a message To send a message, simply provide a `target` field with a thread or group ID and a `text` field with the message text. Optionally, you can pass a `uniqueBy` value that you can use to update the message by calling the webhook again with the same value. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "thr_2hTJ4DGsxUAeEhKOyJ2PMePFL0c", "text": "New bug reported: [BUG154](https://example.com/BUG154)", "uniqueBy": "BUG154" }' \ "https://app.glue.ai/webhook/wbh_123.../456..." ``` ![](/files/glE8cWtGDS8g4lQUwDFZ) To update the previously sent message, call the webhook again with the same `uniqueBy` value. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "thr_2hTJ4DGsxUAeEhKOyJ2PMePFL0c", "text": "New bug reported: [BUG154](https://example.com/BUG154) \n\nResolved by Jason", "uniqueBy": "BUG154" }' \ "https://app.glue.ai/webhook/wbh_123.../456..." ``` ![](/files/tk28X2VRUYclVv4JXONp) To generate a new message, simply provide a new `uniqueBy` value, or omit the `uniqueBy` value if you do not need to update the message.
Example: Formatting messages Glue uses markdown to format messages. The following features are supported: * Text styling * Bold * Italics * Strikethrough * Links * User mentions * Inline code * Code blocks * Blockquotes * Paragraphs * Lists * Ordered * Unordered These features are described in detail below. **1. Text Styling** **Bold** To make text bold, wrap it with two asterisks (`**`) or two underscores (`__`). For example: ``` **This is bold text** __This is also bold text__ ``` Displays as: ![](/files/C5zgwt9FHr0OiPgQoq2J) **Italics** To italicize text, wrap it with one asterisk (`*`) or one underscore (`_`). For example: ``` *This is italic text* _This is also italic text_ ``` Displays as: ![](/files/xJmWCo1apunlkReWBr6V) **Strikethrough** To strikethrough text, wrap it with two tildes (`~~`). For example: ``` ~~This text is strikethrough~~ ``` Displays as: ![](/files/TbAGETgCWhLxon3q86RP) **Bold and Italics Combined** You can combine bold and italics for even more emphasis. For example: ``` ***This is bold and italic text*** ___This is also bold and italic text___ ``` Displays as: ![](/files/9pDKw6psA5d8VN2SiiBz) **2. Links** To create a hyperlink, use square brackets `[ ]` to set the text and parentheses `( )` to set the URL. For example: ``` [Glue](https://glue.ai) ``` Displays as: ![](/files/JpmIj99v47mo1z24V76T) **User Mentions** To mention a user in our chat app, use the following format: ``` [Jason Yonker](glue:usr_2PtTG7GFSgcgwfpeDOBGEQtyB24) ``` Displays as: ![](/files/EqQL7spn5Qucd84YdsJD) **3. Inline Code** To include inline code, wrap your text with backticks (\`). For example: ``` Here is some inline code: `print("Hello, World!")` ``` Displays as: ![](/files/rYIubgBZkyYWaObDX9a5) **4. Code Blocks** For longer code snippets, use triple backticks (\`\`\`) before and after your code block. You can also specify the language for syntax highlighting. For example: ```` ```python for i in range(10): print(i) ``` ```` Displays as: ![](/files/ymmABTSbSqbjzsJVCN7h) **5. Blockquotes** To create a blockquote, use the greater than (`>`) symbol followed by a space. For example: ``` > This is a blockquote. ``` Displays as: ![](/files/IrowQ0EDWUi8ypKGY1mP) **6. Paragraphs** To create paragraphs, simply separate your text with one or more blank lines. For example: ``` This is the first paragraph. This is the second paragraph. ``` Displays as: ![](/files/60ksLTAOL36lpPw517Q0) **7. Lists** **Unordered Lists** To create an unordered list, use `-`, `*`, or `+` followed by a space. For example: ``` - Item 1 - Item 2 - Subitem 1 - Subitem 2 * Item 3 + Item 4 ``` Displays as: ![](/files/WrpsAaF7Aw1oEghFe78Q) **Ordered Lists** To create an ordered list, use numbers followed by a period and a space. For example: ``` 1. First item 2. Second item 1. Subitem 1 2. Subitem 2 3. Third item ``` Displays as: ![](/files/olr757hkd3Lx2gQsOxG7)
Example: Creating threads To create a thread instead of just sending a message, specify a `threadSubject` and ensure that the `target` value is a group. This will result in a thread created in the group with the subject of `threadSubject` and starter message from `text`. The `threadBy` and `uniqueBy` values are optional values that let us update this message (`uniqueBy`) and post more messages to the thread (`threadBy`). ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "threadSubject": "New crash in main.js", "text": "ReferenceError: reference to undefined property x", "threadBy": "BUG268", "uniqueBy": "BUG268-starter-message" }' \ "https://app.glue.ai/webhook/wbh_123.../456..." ``` ![](/files/U8jz857ItOSwPiykMcnm) When you specify a `threadBy` value, you can send follow up messages to the thread by calling the webhook again with the same `threadBy` value. In this case we're using the value `BUG268`. The value is normally and identifier from the external system that is generating the message. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "threadSubject": "New crash in main.js", "text": "Jason, can you look into this?", "threadBy": "BUG268" }' \ "https://app.glue.ai/webhook/wbh_123.../456..." ``` ![](/files/MGFjyMuRiRf9cVoaVPgG) Because we specified a `uniqueBy` value for the starter message, we can call the webhook again to update that starter message (rather than send a new message). Here we're using `"uniqueBy": "BUG268-starter-message"` which is the value we passed in the first webhook to start the thread. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "threadSubject": "New crash in main.js", "text": "ReferenceError: reference to undefined property x \n\nAssigned to: Jason", "threadBy": "BUG268", "uniqueBy": "BUG268-starter-message" }' \ "https://app.glue.ai/webhook/wbh_123.../456..." ``` ![](/files/mThL3im4Q39Ezy9qo6Lw) To create a different thread, send a new `threadBy` value or, if the thread by value is omitted, a new thread will alsways be created. ```bash curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "threadSubject": "New crash in index.js", "text": "ReferenceError: reference to undefined property y", "threadBy": "BUG269", "uniqueBy": "BUG269-starter-message" }' \ "https://app.glue.ai/webhook/wbh_123.../456..." ``` ![](/files/4SOIYNQ40EK1n3bYgPfw)
Example: Attachments To send a message with an attachment, start by uploading the attachment. To do this, append `/attachment` to the end of your webhook URL and make a PUT request. The body of the request should contain the raw contents of the file you are uploading. The following headers are required: 1. `Content-Length`: The length of the file/body of the request 2. `Content-MD5`: The MD5 computed from the contents of the file 3. `X-File-Name`: The name of the file to be uploaded. A PUT request is required. POST is not accepted. Also `multipart/form-data` is not accepted. ``` FILE="yourfile.pdf" FILENAME=$(basename "$FILE") CONTENT_LENGTH=$(wc -c < "$FILE" | tr -d ' ') CONTENT_MD5=$(openssl dgst -md5 -binary "$FILE" | openssl base64) curl -X PUT "https://api.gluegroups.com/webhook/wbh_123.../456.../attachment" \ --data-binary @"$FILE" \ -H "Content-Length: $CONTENT_LENGTH" \ -H "Content-MD5: $CONTENT_MD5" \ -H "X-File-Name: $FILENAME" ``` You will receive a JSON response back with the `id` of the file that was uploaded. ``` {"id":"fil_2ymM4HRuRY4A7ed8OvVaUYxQ812"} ``` To send a message with the uploaded file attached, simply include an `attachments` field with an array containing the file IDs you want to attach. You can attach up to 10 files per message. ``` curl -s -X POST \ -H "Content-Type: application/json" \ -d '{ "target": "thr_2kbzWHxtQvfVEgwEdQduuxRTYG3", "text": "New report available!", "attachments": ["fil_2ymM4HRuRY4A7ed8OvVaUYxQ812"] }' \ "https://api.gluegroups.com/webhook/wbh_123.../456..." ```
### Coming soon * Automatic link parsing * Link previews * Option to send plain text instead of markdown for the `text` field # Using Glue with Claude Connect Claude (or any MCP-compatible AI client) to your Glue threads. Once connected, Claude can search your threads, read full transcripts with attribution, and answer questions grounded in your team's actual conversations — without leaving the AI client you're already using. {% hint style="info" %} **New to MCP?** Model Context Protocol is an open standard that gives AI assistants a uniform way to read external data and use external tools. The Glue MCP server is the bridge that lets Claude (and similar clients) access your Glue threads on your behalf. {% endhint %} The Glue MCP server is currently in **design-partner preview**. Read-only for now — write tools (create thread, send message) are coming soon. #### How it works When you connect Claude to the Glue MCP server, Claude gains five read-only tools: * **Search your threads** by topic, time range, or recipient * **Read full thread transcripts** with per-message attribution * **Look up users and groups** in your workspace You authenticate once with OAuth, scoped to your own Glue user. Every tool call respects the thread permissions you already have in Glue — Claude can only see what you can see. {% hint style="success" %} **Pro tip:** Ask Claude to summarize a long thread before you scroll through it yourself. *"Summarize the planning thread from last week"* is faster than reading top to bottom, and Claude will link you back to the exact messages it pulled from. {% endhint %} #### Setting up the Glue MCP server The Glue MCP server runs at: ``` https://mcp.glue.ai/mcp ``` {% tabs %} {% tab title="Claude Desktop" %}
Step 1 — Open Connector settings In Claude Desktop, open **Settings → Connectors**.
Step 2 — Add the Glue MCP server Click **Add custom connector** and paste the server URL: ``` https://mcp.staging.glue.ai/mcp ``` Click **Add**.
Step 3 — Authorize Glue Claude opens the Glue consent screen in your browser. Review what's being requested (read access to your threads, users, and groups) and click **Allow**. {% hint style="warning" %} In current Claude releases, the browser tab sometimes doesn't auto-close after you authorize. The connection still works — just switch back to Claude manually. {% endhint %}
Step 4 — Try it In a new Claude conversation, ask: *"Use Glue to summarize the most recent project thread I've been on."* Claude will call the Glue MCP tools and answer with links back to the source thread.
{% endtab %} {% tab title="Claude.ai (web)" %}
Step 1 — Open Connector settings Open the profile menu in the top right, then go to **Settings → Connectors**.
Step 2 — Add the Glue MCP server Click **Add custom connector**, paste the server URL, and click **Add**: ``` https://mcp.glue.ai/mcp ```
Step 3 — Authorize Glue Sign in to Glue when prompted and click **Allow** to grant Claude read access to your threads, users, and groups.
Step 4 — Try it Start a new conversation and try a prompt like *"In Glue, what did we decide about \[topic] in the \[thread name] thread?"*
{% hint style="info" %} If you don't see **Add custom connector** in your settings, your Claude workspace may have custom connectors restricted to admins. Ask your admin to add Glue at the workspace level, or install it on your personal Claude account. {% endhint %} {% endtab %} {% tab title="Workspace admin install" %} To make Glue available to everyone in your Claude workspace:
Step 1 — Open Workspace settings Sign in as a Claude workspace admin and go to **Workspace settings → Connectors**.
Step 2 — Add the connector Click **Add custom connector** and paste the Glue MCP server URL.
Step 3 — Save {% hint style="warning" %} Make sure to click **Add** at the end of the dialog. It's easy to half-complete the flow and not realize the connector wasn't saved. If team members report Glue isn't appearing in their connector list, the most common cause is an unsaved admin install. {% endhint %}
Each team member still authenticates individually via OAuth — admin install just makes the connector *available* for them to connect. {% endtab %} {% tab title="Other MCP clients" %} The Glue MCP server is standard MCP. We've tested it working with: * **Claude Desktop** (Mac and Windows) * **Claude.ai** (web) * **Claude API and Claude Code** * **The MCP test client** at [mcpplaygroundonline.com](https://mcpplaygroundonline.com/mcp-test-client) For any other MCP client, the pattern is the same: paste the server URL, complete the OAuth flow, and the Glue tools become available. {% hint style="info" %} **ChatGPT custom connectors** work in theory, but OpenAI requires admin-enabled "developer mode" and the setting location varies by ChatGPT release. We've seen flakiness on OpenAI's side during testing. {% endhint %} {% endtab %} {% endtabs %} #### What you can ask Claude Once Glue is connected, you can ask questions like: * *"Summarize the last week of the Q2 roadmap thread."* * *"What did we decide about API rate limits in the infrastructure thread?"* * *"Find every thread where we discussed authentication and tell me where things landed."* * *"Pull the thread Sadia and I were debating last Friday and give me the three open questions."* * *"What groups am I in?"* Claude returns answers with attribution and links back to the source messages in Glue. {% hint style="success" %} **Pro tip:** If Claude seems unsure who you are, paste your Glue user ID once at the start of the conversation. Claude can identify the connected user automatically, but explicit instruction never hurts. {% endhint %} #### Limitations {% hint style="warning" %} The Glue MCP server is in design-partner preview. Expect some limitations, specifically: * **Read-only.** Write tools (`create_thread`, `send_message`) are not yet available. * **Search caps at 50 results.** Broad queries in large workspaces may truncate. * **Activity-ranked sorting is not supported.** Coming soon. * **No real-time subscriptions.** Reading a thread reflects its current state; there's no change feed yet. * **Enterprise SSO is not yet supported.** Currently under investigation. {% endhint %} **Coming soon** We're working on the following next: * **Write tools** — `create_thread` and `send_message` so Claude can take action on your behalf * **Activity metrics on threads** — message count and latest-message timestamp, so activity-ranked queries work * **Listing in Claude's connector directory** — so you can install Glue without pasting a custom URL * **Per-connector scope controls** — so you can grant Claude access to a subset of your workspaces rather than everything you see Stay tuned as we continue to enhance Glue's MCP server! #### Troubleshooting
Claude says it can't find Glue Nine times out of ten, the OAuth flow didn't fully complete, or an admin who installed Glue at the workspace level didn't click the final **Add** button. Open Claude → **Settings → Connectors**. If Glue isn't listed, re-add the connector and walk through the OAuth flow end to end.
The browser tab didn't auto-close after I authorized Known Claude-side issue, reproducible with other MCP servers too. The connection has still worked — just switch back to your Claude window manually. Glue should now show as connected.
Claude says "authentication required" even after I authorized Most likely the token expired or the grant was revoked. Disconnect Glue from Claude's connector settings and re-add it. If that doesn't help, check **Glue → Settings → Authorized Apps** to make sure Claude is still listed.
Claude returned a thread but it's the wrong one Search ranks by relevance to your query. If multiple threads share similar subjects, Claude may pick the wrong candidate. Try: * Including a person or time range: *"the planning thread Sadia and I were on last week"* * Asking Claude to list candidates first: *"Show me the threads matching X, then ask me which one"*
Claude says it can't find an answer that I know is in the thread A few possibilities: * The answer is further back in the thread than Claude paged. Ask: *"Keep paging — it's older than that."* * Search returned a different thread than the one you meant. Name the thread explicitly. * The answer is implied rather than stated. Claude is conservative on read — it prefers *"I don't see an explicit answer"* over inference. This is a feature for trust, but it sometimes means you need to ask more directly.
Claude appears to be making things up This is the failure mode we care about most. Please flag any examples via or in the *MCP Server Feedback* thread, with the prompt, Claude's response, and the thread URL Claude cited (or didn't). We'll investigate.
I want to revoke Claude's access immediately In Glue, go to **Settings → Authorized Apps → Claude → Revoke**. This invalidates the OAuth tokens server-side. For belt-and-suspenders, also disconnect Glue from Claude's connector settings.
#### Privacy and access Claude only sees Glue threads that your authenticated user can already see — the MCP server enforces the same permissions as the Glue UI. There is no admin-mode bypass. If you want Claude limited to a subset of your workspaces, the current workaround is to authenticate with a Glue user whose access is already scoped. Per-connector scope controls are on the roadmap. For technical details on authentication and tool schemas, see the [Glue Developers](https://docs.glue.ai/developers/) section. *** ## Agent Instructions: 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: ``` GET https://docs.glue.ai/~/changes/251/ai/using-glue-with-claude.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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. # Glue API Looking for Glue's API documentation? Check out the Developer Docs here! # GitHub Receive updates on GitHub Issues and PRs in Glue. The GitHub integration makes it easy to follow GitHub work without leaving Glue. When you share a GitHub link, Glue shows a rich preview with the latest details and keeps the conversation up to date as issues and pull requests change. ### GitHub Link Previews GitHub link previews in Glue automatically display rich information when you share GitHub links in conversations. These previews show key details about repositories, pull requests, issues, commits, and files without requiring you to leave the conversation. Statuses will update in real time in these previews. When you paste a GitHub URL into any Glue conversation, the system automatically detects it and generates a rich preview.
### Auto-Subscribe to GitHub Updates When you share a GitHub issue or pull request link in a thread, Glue automatically subscribes the thread to updates for that issue or PR. Whenever the status changes (e.g., an issue is closed or a PR is merged), a system message is posted to the thread so everyone stays informed.
{% hint style="info" %} You don't need to add the GitHub app to a thread to auto-subcribe to updates— just share a link with the link preview. If you do not want your thread subscribed to updates, remove the link preview before sending. {% endhint %}
### Trigger new threads or messages based on GitHub activity Add the app to a Group or Thread
Add the GitHub app to a group* or thread The GitHub app can be added to either a group or a thread: * Group: When adding the GitHub app to a group, it can be configured to either create new threads or send updates to the Group chat. * Thread: The GitHub app will send notifications to the thread. To add the GitHub app to a group, navigate to the group and then choose **Apps** from the menu to open the Apps tab of the group settings. ![](/files/jfelRZ7SFd0UpVKcEtbD) To add the GitHub app to a thread, navigate to the the thread and then choose **Thread Settings** from the menu. With the settings open, choose the **Apps** tab. ![](/files/GyUAuCYpMB9BqAdZXtQW) From the **Apps** tab of either a group or thread, click to add GitHub. ![](/files/0pOxxpk2127czEmcsoE6) A modal will appear where you can connect a repository.
Connect a repository After adding the GitHub app to a group or thread, you will need to choose and configure GitHub repositories that you want to receive updates for. Start by clicking **Connect a Repo** ![](/files/BjYPhjoGQIQ9W6mGSKoR) When connecting your first repository, you'll be ask to sign in to GitHub. Click **Authorize.** ![](/files/GchXgDhWKs9iP7F5BOSW) A window will appear where you can log in to GitHub. Click **Authorize** to let Glue access your account. ![](/files/QdBU6C6G34MUErmvIl9Q) After logging in, you'll be asked to install the Glue app for GitHub to you GitHub organization. Click **Install.** ![](/files/iO4Ee3egDNqmLydzBtp2) A window will appear where you can choose a GitHub organization. When choosing repositories, make sure to choose all of the repositories you want to use with Glue, not just the ones you want to use with the selected group or thread. You won't receive updates for any repos until you configure them later in Glue and you can configure different repositories for different groups/threads. When you're done, click **Install**. ![](/files/tqIiXVErNgQuM3hmh5Xn) After signing in and installing the app, choose a Repo from the list and then click **Add** ![](/files/hOuN11vvJbmg4Vd3Fz0q) Choose which events you want to receive messages for and then click **Next**. ![](/files/SazJKZ8AhTziYW0DgtVe) If you're connecting a repo to a group, you'll be asked whether you want to send all updates to the group chat or create threads for each Issue, PR, etc. ![](/files/G2gol79kIM4LGW7rDJvC) The repo you added will now appear in the list of repos connected to the group or thread you selected. From here you can connect another repo to this thread or **Remove** any previously connected repos. ![](/files/B8rAEY3RNa0K8OqXXE2p) To manage this list in the future, go back to the **Apps** section of the group or thread and click the edit button next to GitHub. ![](/files/R6z6b49bf8P0aPjDNRer)
Choose which events on Pull Requests or Issues trigger a notification in Glue Choose which events you want to receive messages for and then click **Next**. ![](/files/SazJKZ8AhTziYW0DgtVe) If you're connecting a repo to a group, you'll be asked whether you want to send all updates to the group chat or create threads for each Issue, PR, etc. ![](/files/G2gol79kIM4LGW7rDJvC) The repo you added will now appear in the list of repos connected to the group or thread you selected. From here you can connect another repo to this thread or **Remove** any previously connected repos. ![](/files/B8rAEY3RNa0K8OqXXE2p)
*\*Note that to add an app to a group, you must be a group admin or workspace admin. Anyone can add an app to a thread.* ### Setting up the GitHub Integration
Step 1: Add the GitHub app to your workspace See instructions for [installing an app in your workspace.](/integrations/integrations-overview/add-integrations-to-your-glue-workspace#add-app-to-workspace)
Step 2: Authorize GitHub Each user will need to authorize access to their GitHub account once. You will be prompted to authorize the first time you paste a Github link into a message. * Paste a GitHub link into any message in Glue. * A prompt will appear asking you to authorize Glue to access GitHub. Click **Authorize**.
### GitHub requirements To use GitHub link previews, your organization needs: 1. **OAuth authentication**: Proper permissions to access GitHub data 2. **Team access**: Appropriate permissions to view the linked GitHub resources ### Troubleshooting
Link previews are not appearing * Verify GitHub app is installed * Check repository permissions * Confirm you have access to the repository
I do not want my thread auto subscribed to app updates * Just remove the link preview before sending and your thread will not be subscribed to updates.
App updates are not sending for a link I sent * Make sure you include the rich link preview when you send the link to the thread. If you removed the link preview, the thread will not be subscribed. * App udpates are only supported in threads, not in other chat types.
How do I unsubscribe my thread from an app update * This is coming soon.
# Linear Get rich link previews and auto-subscribe threads to Linear updates The Linear integration makes it easy to track work from Linear without leaving Glue. When you share a Linear link, Glue shows a rich preview with the latest details and keeps the conversation up to date as the issue changes. ### Linear Link Previews With this integration, Glue can unfurl Linear links, making it easy to see issue details, project information, and team context without leaving the conversation. Statuses will update in real time in these previews. ### Auto-Subscribe to Linear Updates When you share a Linear issue link in a thread, Glue automatically subscribes the thread to updates for that issue. Whenever the issue's status changes, a system message is posted to the thread so everyone stays in the loop — no manual setup required. Just send your link with the link preview, and the thread will be automatically suscribed to updates.
### Setting up the Linear integration To set up Notion, just paste a Notion link into any message in Glue and send the message. The first time you do this: * A prompt will appear asking you to connect Notion to Glue. Click **Connect**.
* A popup up with then appear asking you to authorize Glue to use Notion. Click **Authorize**.
* A browser pop-up will open, redirecting you to Notion. Depending on your browser, the messaging may vary slightly. If you're already logged into Notion, the authorization will complete automatically. If not, you'll be prompted to enter your Notion credentials to proceed. * You will see a confirmation message once Notion is successfully connected.
{% hint style="info" %} You don't need to add the Linear app to a thread to auto-subscribe to updates — just share a link with the link preview and the app will be added to the workspace automatically. If you do not want your thread subscribed to updates, remove the link preview before sending. {% endhint %} {% hint style="warning" %} If the Linear app is removed from the workspace, an admin will need to re-add the integration manually to re-enable functionality. {% endhint %} ### Supported Resource Types | Resource Type | Preview Format | Example | | ------------- | ------------------------------- | --------------------------------------- | | **Issues** | `Issue • TEAM-123: Issue Title` | Issue • API-456: Fix authentication bug | | **Projects** | `Project • Project Name` | Project • Q3 Mobile Redesign | | **Teams** | `Team • Team Name` | Team • Engineering | #### Troubleshooting
I do not want my thread auto subscribed to app updates * Just remove the link preview before sending and your thread will not be subscribed to updates.
App updates are not sending for a link I sent * Make sure you include the rich link preview when you send the link to the thread. If you removed the link preview, the thread will not be subscribed. * App updates are only supported in threads, not in other chat types.
How do I unsubscribe my thread from an app update * Open the thread resource sidebar * Locate the shared link resource and click the 3 dot menu * Click "Stop updates"
# Jira Get rich link previews and auto-subscribe threads to Jira updates The Jira integration makes it easy to track work from Jira without leaving Glue. When you share a Jira link, Glue shows a rich preview with the latest details and keeps the conversation up to date as things change. ### Jira link previews With this integration, Glue can unfurl Jira links so you can see issue details, status, and assignees right in the conversation. Statuses update in real time in these previews, so the information stays accurate as work moves forward. ### Auto-subscribe to Jira updates When you share a Jira issue link in a thread, Glue automatically subscribes the thread to updates for that issue. Whenever the issue's status, assignee, or key fields change, a system message is posted to the thread so everyone stays in the loop. If you don't want your thread subscribed to updates, remove the link preview before sending. ### Setting up the Jira integration To set up Jira, just paste a Jira link into a thread in Glue and send the message (with the link preview attached). The first time you do this: * The Jira app is added to your workspace automatically. * A prompt will appear asking you to connect Jira to Glue. Click **Connect**. * A browser pop-up will open, redirecting you to Jira. If you're already logged in, the authorization will complete automatically. If not, you'll be prompted to enter your Jira credentials and choose the Jira site you want to connect. * You will see a confirmation message once Jira is successfully connected. Each person will be prompted to authorize their own Jira account once. Once setup is complete, the thread will be subscribed to updates from the Jira link you sent. {% hint style="info" %} You don't need to add the Jira app to a thread to auto-subscribe to updates — just share a link with the link preview. If you do not want your thread subscribed to updates, remove the link preview before sending. {% endhint %} {% hint style="warning" %} If the Jira app is removed from the workspace, an admin will need to re-add the integration manually to re-enable functionality. {% endhint %} ### Supported resource types | Resource Type | Preview Format | Example | | ------------- | ------------------------------ | ----------------------------------- | | **Issues** | `Issue • KEY-123: Issue Title` | Issue • WEB-482: Fix login redirect | | **Epics** | `Epic • KEY-123: Epic Title` | Epic • WEB-400: Checkout redesign | | **Projects** | `Project • Project Name` | Project • Website Relaunch | | **Boards** | `Board • Board Name` | Board • Mobile Sprint Board | **Troubleshooting**
Link previews are not appearing * Make sure the Jira app is installed in your workspace. * Confirm you've authorized your Jira account. * Check that you have access to the linked Jira project or issue.
I do not want my thread auto-subscribed to app updates * Just remove the link preview before sending and your thread will not be subscribed to updates.
App updates are not sending for a link I sent * Make sure you include the rich link preview when you send the link to the thread. If you removed the link preview, the thread will not be subscribed. * App updates are only supported in threads, not in other chat types.
How do I unsubscribe my thread from an app update * Open the thread resource sidebar * Locate the shared link resource and click the 3 dot menu * Click "Stop updates"
# Notion Get rich link previews and auto-subscribe threads to Notion page updates The Notion integration makes it easy to track work from Notion without leaving Glue. When you share a Notion link, Glue shows a rich preview with the latest details and keeps the conversation up to date as page properties change.
### Notion Link Previews With this integration, Glue can unfurl Notion links — making it easy to see page context without leaving the conversation. Statuses will update in real time in these previews. ### **Auto-Subscribe to Notion Page Updates** When you share a Notion page in a thread, Glue automatically subscribes the thread to the page's property updates. If you're using Notion to track projects or tasks, this feature is for you. Whenever a page's property changes, a system message is posted to the thread so everyone stays in the loop — no manual setup required. Just send your link with the link preview, and the thread will be automatically subscribed to the page's updates. ### Supported Resource Types | Resource Type | Preview Format | Example | | ------------- | -------------------------- | -------------------------- | | **Pages** | `Page • Page Title` | Page • Q2 Launch Checklist | | **Databases** | `Database • Database Name` | Database • Product Roadmap | ### Setting up the Notion integration To set up Notion, just paste a Notion link into any message in Glue and send the message. The first time you do this: * A prompt will appear asking you to connect Notion to Glue. Click **Connect**. * A popup up with then appear asking you to authorize Glue to use Notion. Click **Authorize**. * A browser pop-up will open, redirecting you to Notion. Depending on your browser, the messaging may vary slightly. If you're already logged into Notion, the authorization will complete automatically. If not, you'll be prompted to enter your Notion credentials to proceed. * You will see a confirmation message once Notion is successfully connected. {% hint style="warning" %} If the Notion app is removed from the workspace, an admin will need to re-add the integration manually to re-enable functionality. {% endhint %} ### **Troubleshooting**
Page updates are not sending for a link I sent * Make sure you include the rich link preview when you send the link to the thread. If you removed the link preview, the thread will not be subscribed. * Auto-subscribe currently applies to Notion page and database links. * Notion page update events only fire for changes to page properties. Changes to the page content itself will not send app updates. * Sharing a database link subscribes the thread to updates for all pages in that database. * Notion events can take up to a minute or two to appear in Glue, so a short delay is expected.
How do I unsubscribe my thread from a page update? * Open the thread resource sidebar * Locate the shared link resource and click the 3 dot menu * Click "Stop updates"
# Cursor {% hint style="warning" %} The Cursor app is currently in **beta**. Behavior and setup may change as we refine the experience. {% endhint %} ### What is the Cursor integration? The Cursor integration lets you mention **@Cursor** in any thread to start a [Cursor Cloud Agent](https://cursor.com/docs/cloud-agent) without leaving Glue. The agent reads the thread for context, runs in the cloud, and reports back with its progress and results — right where your team is already talking about the work. You can use Cursor in Glue to: * Kick off bug fixes, refactors, and small features from a thread where the work was already being discussed * Keep the conversation, the agent's progress, and the final PR all in one place * Share the agent's results with your team so the whole thread stays in the loop ### Setting up the Cursor integration
Step 1: Add the Cursor app to your workspace Locate Cursor in the App Directory, and click "Add app" to add Cursor to your workspace. If you don't see it in your directory, check with your Admin.
Step 2: Set a default repository in Cursor Cursor sessions in Glue run against the default repository configured in your [Cursor Cloud Agents dashboard](https://cursor.com/dashboard/cloud-agents). Set this up before you start your first session. * Go to the [Cursor Cloud Agents dashboard](https://cursor.com/dashboard/cloud-agents). * Set the repository you want Cursor agents to work in as your default. {% hint style="info" %} Cursor uses your default repository each time a session is initialized in Glue. You can't switch repositories mid-session — if you need Cursor to work in a different repo, update the default in your Cursor dashboard before starting a new session. {% endhint %}
Step 3: Create a Cursor User API Key In the same dashboard from the prior step, find the "User API Keys" setting and click "Add" to create a new API key. Copy the generated token, you will need it in the next step.
Step 4: Authorize Cursor Each user will need to connect their Cursor account once. You'll be prompted the first time you mention **@Cursor** in a thread. * Mention **@Cursor** in a thread and send the message. * A prompt will appear asking you to connect Cursor to Glue. Click **Connect Cursor**.
* Glue will prompt you for an API key — paste in the generated token from the previous step. Click **Authorize.**
* You will see a confirmation message once Cursor is successfully connected.
### Starting a Cursor session in a thread Cursor works inside **agent sessions** — a back-and-forth side conversation with the agent that lives alongside your thread, similar to how Glue AI sessions work. You can iterate with Cursor and share results with your team when you're ready. 1. Open any thread where you want Cursor to help. 2. Type `@Cursor` in the message editor, followed by a prompt describing what you want it to do. For example: *"@Cursor fix the timezone bug described above and open a PR."* 3. Click **Send** to start the session. Cursor will read the thread for context, spin up a cloud agent against your default repository, and begin working. The session sidebar will open automatically so you can follow along. {% hint style="info" %} Give Cursor as much context as possible in your prompt. The more specific the ask — the file, the bug, the expected behavior — the better the result. Cursor will also read the thread, so earlier messages can help set the scene. {% endhint %} {% hint style="warning" %} Image attachments are not currently supported in Cursor sessions. {% endhint %} ### Going back and forth with Cursor Once a session is running, you can keep the conversation going in the session sidebar, just like you would with a teammate. * Ask follow-up questions as the agent works * Send clarifying instructions if it's heading in the wrong direction * Review intermediate progress before sharing anything with the rest of the thread ### Sharing Cursor's results with the thread When Cursor finishes a piece of work — for example, opening a PR or producing a summary of what it changed — you can share the result with the thread so your team can see what happened. * Click **Share** at the top of the session sidebar to publish the exchange to the thread. * Glue summarizes the session for the thread and highlights key artifacts, like the PR link or any outputs Cursor produced. * Clicking the summary opens the full session sidebar so anyone in the thread can read the details. If Cursor opens a PR in a connected GitHub repo, the PR link will unfurl into a GitHub link preview in the thread so the team can follow its status. ### Tips for working with Cursor in Glue {% hint style="success" %} **Start Cursor sessions in threads where the work is already being discussed.** Cursor uses the thread for context, so replying to an existing bug report or feature discussion gives the agent a running start. {% endhint %} * Be specific about the outcome you want (e.g., *"open a PR that adds a test for X"*) rather than vague goals. * Mention the file, function, or area of the codebase if you know it. * Set your default repository in the [Cursor Cloud Agents dashboard](https://cursor.com/dashboard/cloud-agents) to the repo you work in most often, since Cursor will use it for every session you start in Glue. * For longer or riskier changes, review the PR in GitHub before merging, the same way you would for any teammate's work. ### Troubleshooting
Cursor isn't responding when I mention it * Confirm you've authorized Cursor for your user account by mentioning **@Cursor** in a thread — you should see a **Connect** prompt if you haven't. * Make sure you have a default repository set in your [Cursor Cloud Agents dashboard](https://cursor.com/dashboard/cloud-agents). Without one, Cursor won't be able to start a session. * Agent sessions can only be started in threads. Try starting the session from a thread rather than a group chat or DM.
Cursor is working in the wrong repository Cursor uses the default repository set in your [Cursor Cloud Agents dashboard](https://cursor.com/dashboard/cloud-agents) for every session. You can't switch repositories after a session has started. * To change repos, update the default in your Cursor dashboard, then start a **new** session in Glue.
Cursor didn't see the image I attached Image attachments aren't currently supported in Cursor sessions. Describe the issue in text, paste relevant error messages or logs, or link to the code you want Cursor to look at instead.
How do I give feedback on the Cursor integration? Cursor is in beta, so your feedback helps shape where it goes next. You can contact our support team by opening the Help icon next to your profile picture and clicking **Contact Support**.
# Typeform Notify Glue when a form is submitted.
Step 1: Add the Typeform app to your workspace See [instructions for installing an app in your workspace.](/integrations/integrations-overview#steps-to-set-up-one-of-the-pre-built-integrations-in-your-glue-workspace)
Step 2: Add the Typeform app to a group* or thread * To receive Typeform submissions in a Group Chat, navigate to the group and then choose **Apps** from the menu to open the Apps tab of the group settings. ![](/files/jfelRZ7SFd0UpVKcEtbD) * To receive Typeform submissions in a thread, navigate to the the thread and then choose **Thread Settings** from the menu. With the settings open, choose the **Apps** tab. ![](/files/GyUAuCYpMB9BqAdZXtQW) * From the **Apps** tab of either a group or thread, click to add Typeform. ![](/files/UU06fztpXDdy04yzG500) * When you first add Typeform to a group or thread, you'll see a modal where you can configure the app. Initially there will be no Typeform forms connected. Click **Connect a Form** to connect one. ![](/files/LMq8ir6HfuExUOdF7XPd) * When connecting your first form, you'll be ask to sign in to Typeform. Click **Authorize.** ![](/files/6LTOx1SQWFCmAAiKnoeh) * A window will appear where you can log in to Typeform and then click **Accept** to give access to Glue. ![](/files/xmN05N8zzz8B52QAhRT2) * After signing in, choose a Form from the list and then click **Add** ![](/files/i8ZwKCMV8jP6Ai9cXSPS) * The form you added will now appear in the list of forms connected to group or thread you selected. From here you can connect another form to this thread or **Remove** any previously connected forms. * To manage this list in the future, go back to the **Apps** section of the group or thread and click the edit button next to Typeform. ![](/files/t8mqJSHiaMlrdRNvTK0H) For both groups and threads — whenever a form you connected is submitted, you'll see a message inside Glue. ![](/files/KaVLSBsTYE82Ro6glW2j)
*\*Note that to add an app to a group, you must be a group admin or workspace admin. Anyone can add an app to a thread.* # ClickUp Notify Glue when tasks are created or updated.
Step 1: Add the ClickUp app to your workspace See [instructions for installing an app in your workspace.](/integrations/integrations-overview#steps-to-set-up-one-of-the-pre-built-integrations-in-your-glue-workspace)
Step 2: Add the ClickUp app to a group* or thread The ClickUp app can be added to either a group or a thread: * Group: When adding the ClickUp app to a group, it can be configured to either create new threads or send updates to the Group chat. * Thread: The ClickUp app will send notifications to the thread. To add the ClickUp app to a group, navigate to the group and then choose **Apps** from the menu to open the Apps tab of the group settings. ![](/files/gvV8EdHhDoUIg9RrlEdC) To add the ClickUp app to a thread, navigate to the the thread and then choose **Thread Settings** from the menu. With the settings open, choose the **Apps** tab. ![](/files/DI9cwbhYYkmNhxJoHl8G) From the **Apps** tab of either a group or thread, click to add ClickUp. ![](/files/xzYwJEwktTHwxVHcgxXt) A modal will appear where you can connect a space, folder, or list.
Step 3: Connect a Space, Folder, or List After adding the ClickUp app to a group or thread, you will need to spaces, folders, and lists that you want to receive updates for. Start by clicking **Create Connection** ![](/files/Tsudc4QjdUedX1J2MiyR) When making your first connection, you'll be ask to sign in to ClickUp. Click **Authorize.** ![](/files/e51emzmU9wV2AVsvcn5D) A window will appear where you can login and choose one or more ClickUp workspaces. When you're done, click **Connect Workspace**. ![](/files/JgFXRAqsffxCPP5l7eC7) Next, choose a space that you want to receive updates for. ![](/files/yPgUzieLGaygXWIFJjm7) If you want to receive updates for all tasks in the selected space, click **continue.** Optional: If you want to limit the updates you receive to a folder or list, you can choose one from the second drop down. If you choose a folder, a third dropdown will appear giving you the option to choose a list within that folder. Click **Continue** at any point when you're done. ![](/files/0z4oVlXAKuGMBPsL4PKg) Choose the events that you want to receive Glue messages for. You'll receive messages when a new task is created and for any events that you enable here. ![](/files/laqQAlHjQ7E98izo2b5X) If you're connecting to a group, you'll be asked whether you want to send all updates to the group chat or create threads for each task. ![](/files/oWvhvjpvtPVAOGmKW4nj) The item you added will now appear in the list of items connected to the group or thread you selected. From here you can connect another item to this thread or **Remove** any previously connected items. ![](/files/Jfmat8ucPzHmi5ANyqwb) To manage this list in the future, go back to the **Apps** section of the group or thread and click the edit button next to ClickUp. ![](/files/xl5yTSBw9WpmAYIgfggb)

*\*Note that to add an app to a group, you must be a group admin or workspace admin. Anyone can add an app to a thread.* # Monday.com Receive notifications from your Monday.com workspace
Step 1: Add the Monday.com app to your workspace See [instructions for installing an app in your workspace.](/integrations/integrations-overview#steps-to-set-up-one-of-the-pre-built-integrations-in-your-glue-workspace)​
Step 2: Add the Monday.com app to a group* or thread The Monday.com app can be added to either a group or a thread: * **Group:** When adding the Monday.com app to a group, it will create a new thread for each event you set it up for (e.g. new item added to a board). * **Thread:** The Monday.com app will send notifications to the thread. To add the Monday.com app to a group, navigate to the group and then choose **Apps** from the menu to open the Apps tab of the group settings.![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yStw8wuIeWBdGOh81bd%2Fuploads%2FnKi7s5GdKYXNEl5xd0VK%2Fimage.png?alt=media\&token=23cd0d5c-33a4-4dc2-9482-ee7cfa016372)​ To add the Monday.com app to a thread, navigate to the the thread and then choose **Thread Settings** from the menu. With the settings open, choose the **Apps** tab.![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5yStw8wuIeWBdGOh81bd%2Fuploads%2FdWAQEdN7x3KCwxUlPlRx%2Fimage.png?alt=media\&token=7beb71e4-347f-4ead-a175-531c468ff4b1)​ From the **Apps** tab of either a group or thread, click to add Monday.com
Step 3: Authorize Monday.com and Connect a Board #### Install the app 1. If you are the first person setting up Monday.com with your Glue workspace, you will need to **install the Glue app in Monday.com.** You will see the prompt below. Click **continue.**
{% hint style="info" %} If you instead see a pop up that asks you to authorize, you can skip to the authorization steps below. {% endhint %} 2. **You will be taken to Monday.com** - what you see will depend on if you've already installed another Glue workspace to Monday. 1. **If you’ve installed Glue before (for another workspace you belong to):**\ You’ll see an option to **Update** the app. Use the dropdown in the upper right corner to select the correct Monday workspace. ![](/files/FKqJFmBz4OO3L9dwY6Zi) 2. **If this is your first time installing any Glue workspace to Monday:** You’ll see the **Install Glue** page, where you can choose the Monday workspace(s) to install to. Click **Install**. ![](/files/7lvdKd6Wk1DHnSqZwwhZ) 3. After installing or updating, close the Monday pop-up and return to Glue. You’ll see a confirmation message—click **Continue** to move to the authorization flow, where you’ll connect Monday to Glue.
#### Authorize the app 1. You will need to authorize Glue to use Monday.com the first time you are setting up an integration with a Glue thread or group. Click **Authorize.**
2. A browser pop up will appear asking you to continue. **Select continue.**
3. If you are not logged in, a window will appear where you can **login to Monday.** Once you are logged in, you will see the screen below to Authorize Glue. Select **Authorize.**
#### Connect a board 1. After authorizing, you will be returned to Glue to **select a Monday.com board to connect.** {% hint style="info" %} Note: If you want to connect multiple boards, you will need to do so one at a time. {% endhint %}
2. **Choose the events** that you want to receive Glue threads or messages for. You'll receive messages when a new item is created and for any events that you enable here.
3. The board you added will now appear as a connection in your group or thread when you click on the Monday app. From here you can connect another item to this thread or **Remove** any previously connected items.
#### Managing the app To manage your Monday connections in the future, go back to the **Apps** section of the group or thread and click the edit button next to Monday.com. You will be able to create or remove connections. ![](/files/sRyg4uNH3NOTsAGHf4qH)
*\*Note that to add an app to a group, you must be a group admin or workspace admin. Anyone can add an app to a thread.* # CircleCI We have published a CircleCI orb that allows you to easily update your CircleCI jobs to post to Glue. To get started, check out the [orb listing](https://circleci.com/developer/orbs/orb/gluegroups/glue) on CircleCI and our [wiki](https://github.com/gluegroups/circle-orb/wiki) on GitHub. # Sentry Receive Sentry alerts in Glue
Step 1: Add the Sentry app to your workspace See instructions for [installing an app in your workspace.](/integrations/integrations-overview/add-integrations-to-your-glue-workspace#add-app-to-workspace)
Step 2: Add the Sentry app to a group* or thread * Add Sentry to a group in order to send messages to a group chat or to create a thread in a group. Navigate to the group and then choose **Apps** from the menu to open the Apps tab of the group settings. From there **Add** Sentry from the list. ![](/files/jfelRZ7SFd0UpVKcEtbD) ![](/files/FMG4F3iTIDVSrGYJJOld) * Add Sentry to a thread in order to send messages to that existing thread. Navigate to the the thread and then choose **Thread Settings** from the menu. With the settings open, choose the **Apps** tab, then **Add** Sentry from the list. ![](/files/Q3srkOp7Zm9CkTwKOtOd) ![](/files/lKRvcBCoWmVLoG6haXF4) * If you have not yet added the Glue app for Sentry, you'll be prompted to add it at this time.
Step 3: Create an alert in Sentry * In Sentry, navigate to **Alerts** and click "Create Alert Rule". * Choose what you want to be alerted about and then click "Set Conditions". * On the conditions screen under "THEN perform these actions", select Glue. ![](/files/rRSPwTCHX8vsO8p94kBC) * On the newly create Glue item, Click Settings ![](/files/F1vC5muGlGFCI7YFLX6f) * Choose the Glue action you want to perform and then choose the Glue group or thread that you want to send the alert to. You can only select Groups or Threads that the Sentry app has been added to in Glue. ![](/files/IRehAxyKpKY0TzqPm3Ko)
*\*Note that to add an app to a group, you must be a group admin or workspace admin. Anyone can add an app to a thread.* # Zoom Start or join a Zoom call from any thread or chat With the Zoom integration for Glue, you can quickly and easily start a Zoom meeting from anywhere inside of Glue (Thread, Group or DM). When you start a Zoom meeting inside Glue, a message will be generated containing a link to the meeting that others can use to join.
Step 1: Add the Zoom app to your workspace See [instructions for installing an app in your workspace.](/integrations/integrations-overview#steps-to-set-up-one-of-the-pre-built-integrations-in-your-glue-workspace)
Step 2: Start a call from Glue * In any thread or chat, click the thread action button on the compose box or type the back slash "/ " to get a list of possible thread actions.
* Choose **Start a Zoom call**
* After choosing this action for the first time, you will be prompted to authorize Zoom. ![](/files/CjVEqhJKGpOqZpmaowlq) * Click **Authorize Zoom**. A new window will appear with the Zoom login screen. Click **Allow** to give consent. * Return to Glue and repeat the action to **Start a Zoom call**. A link to the call will be sent to the thread and all participants can click the link to join.
# Google Meet Start a Google Meet space from any thread or chat With the Google Meet integration for Glue, you can quickly and easily start a Google Meet Space from anywhere inside of Glue (Thread, Group or DM). When you start a Google Meeting inside Glue, a message will be generated containing a link to the meeting that others can use to join.
Step 1: Add the Google Meet app to your workspace See [instructions for installing an app in your workspace.](/integrations/integrations-overview#steps-to-set-up-one-of-the-pre-built-integrations-in-your-glue-workspace)
Step 2: Start a Google Meet space from Glue * In any thread or chat, click the thread action button on the compose box or type the back slash "/ " to get a list of possible thread actions.
* Choose **Create a Google Meet space**
* After choosing this action for the first time, you will be prompted to authorize Google Meet. ![](/files/eZdf8wL8dtKCjuFZXj0L) * Click **Authorize**. A new window will appear with the Google Meet login screen. Log in to your account and then click **Allow** to give consent. ![](/files/EvXhadZjuK22suxAxqlQ) * Return to Glue and repeat the action to **Create a Google Meet space**. A link to the space will be sent to the thread and all participants can click the link to join. ![](/files/EVATLt6Fd3ph4zRtqkfK)
*** # Google Drive This is phase one of our Google Drive integration. With this integration, Glue can access Google Drive links you share in chats just like file attachments. This allows Glue AI to analyze and summarize linked GDrive documents without having to change link permissions. We have more planned for this integration, so stay tuned!
## Setting up the Google Drive integration
Step 1: Add the Google Drive app to your workspace See [instructions for installing an app in your workspace.](/integrations/integrations-overview#steps-to-set-up-one-of-the-pre-built-integrations-in-your-glue-workspace)
Step 2: Authorize Google Drive Each user will need to authorize access to their GDrive account once. You will be prompted to authorize the first time you paste a GDrive link into a message after the app has been added to your workspace. * Paste a Google Drive link into any message in Glue. * A prompt will appear asking you to authorize Glue to access Google Drive. Click **Authorize**. ![](/files/auHnUlFQ36WMPFFTiT1h) * You will then be asked to sign in to Google to give Glue access. Choose which Google account you want to connect with Glue, and then click **Continue**. * You will then see a screen that says what access Glue will have to your GDrive. Click **Allow.** ![](/files/Rm4gyB4jywSExj78wc5Z) * You will see a confirmation message once GDrive is successfully connected. * Once authorized, Glue AI can analyze and summarize linked documents.
{% hint style="info" %} You do not need to change link sharing permissions in order for Glue AI to access a shared GDrive link, but if you're sharing it with others on your team, make sure you update the link settings! {% endhint %} {% hint style="warning" %} **Important:** Do not remove the link preview when sharing a Google Drive link. The preview is what allows Glue AI to reference the document as an attachment. {% endhint %} ## Current limitations of the integration * You **cannot** **search for Google Drive files** directly within Glue. * Glue AI **cannot** **access your entire Google Drive**—only the specific links shared in threads or groups you have access to. * Glue AI **cannot analyze a Google Drive file larger than 50MB** in size. It will return an error message if the file is larger than the size limit. ## Troubleshooting * If our RAG is taking a while to index the document, you might see a message from Glue AI saying it's taking a while to analyze the attachment and to try again in a few minutes. Send another message in a few minutes and ask Glue AI to try again! You do not need to reattach the document.
# Giphy Quickly send GIFs in your messages 1. **To start, you will need to add Giphy to your workspace.** * See [instructions for installing an app in your workspace.](/integrations/integrations-overview#steps-to-set-up-one-of-the-pre-built-integrations-in-your-glue-workspace) 2. Search for GIFs to send in any message using: * The **slash command**: just type `/` and pick "Send GIF" * Or tap the **slash icon** in the message composer 3. You will be able to shuffle between GIF options that fit your prompt and then send your choice!
If you’ve already found your perfect GIF elsewhere, **you can also upload GIFs in the message editor:** * On the Mac app, you can drag and drop in a GIF straight from the [Giphy](https://giphy.com/) site. * On all of our apps, you can upload GIFs you have saved on your device via the attachment icon or dragging and dropping. # Zapier apps Connect with any of the integrations supported by Zapier
Notion/files/wNLI1Y3x694qKEstcEVLhttps://zapier.com/apps/notion/integrations/glue
Google Sheets/files/fTqoo6PAAzYPodftQTsWhttps://zapier.com/apps/google-sheets/integrations/glue
Asana/files/Pwa4StIDGshGtIO7uL1nhttps://zapier.com/apps/asana/integrations/glue
Step 1: Add the Zapier app to your workspace * In Glue, navigate to workspace settings --> **Apps** tab ![](/files/wnXpAMctuGXwYV0xfgKh) * Locate the Zapier app and click **Add** ![](/files/1YY03eI5EN8hcvN3pZRZ) * Click **Add to Workspace** ![](/files/oG3nj9eMbXsBRcmwlqyN)
Step 2: Add the Zapier app to a thread or group * Add Zapier to a group in order to send a message to a group chat or to create a thread in a group. Navigate to the group and then choose **Apps** from the menu to open the Apps tab of the group settings. From there **Add** Zapier from the list. ![](/files/jfelRZ7SFd0UpVKcEtbD) ![](/files/5zTdp1hU3lkYFTvjTMgv) * Add Zapier to a thread in order to send a message to a thread. Navigate to the the thread and then choose **Thread Settings** from the menu. With the settings open, choose the **Apps** tab, then **Add** Zapier from the list. ![](/files/GyUAuCYpMB9BqAdZXtQW) ![](/files/3cGMGjO398CXlac61q4J)
Step 3: Create your first Zap * Sign into your Zapier account and create a new zap to connect Glue to any other supported tool. ![](/files/oeDzGmoyh1ZLsOnp5sPj) * Connect your third party account to Zapier as the trigger ![](/files/k2itV5nvw6kHNw4e7kPp) * Choose Glue as the app taking action and select one of the following: * Send Message: Use this action to have Zapier send a new message to a group chat or thread each time the Zap is triggered. * Create Thread: Use this action to have Zapier create a new thread in a chosen group each time the Zap is triggered. You must add Zapier to a group in order to use this action. ![](/files/9ugiGhCVTW0PfWBwHzzf) * Connect your Glue account to Zapier ![](/files/RDWoHavSR5M2xuX5KukX) * In a pop up window, click to allow Zapier to send a message in thread ![](/files/lhXgIxZ44cS8pGW3iGlP) * When you reach the Action section of the Zap set up, you'll need to where you'd like to receive updates: * For **Send Message**, you can group chats from groups that Zapier has been added to as well as any threads. * For **Create Thread**, select a group that Zapier has been added to. ![](/files/9FuCWm8SbL9SAixuTyG2) * Fill out the subject and message using data fields from your trigger. You can use Markdown to format the message. ![](/files/Aev4IwmFs1piTPEWMa0C) * Advanced: If you are using the **Create Thread** action, you can group multiple messages into a thread using the **Thread By Value**. The first Zap that runs with a given value will create the thread associated with the **Thread By Value** and then whenever another Zap runs with the same value, it will add a new message to the thread instead of creating a new thread. ![](/files/65aBx4ws081olUVOqJjR) * **Test** your Zap action and then **Publish**! ![](/files/QS1JdTRbNXJleXJIYSpo)
# MCP Servers Connect MCP Servers to Glue **Glue AI can now act as an MCP client**, allowing it to **integrate with applications** that expose an **MCP server.** When an MCP server is connected to Glue, Glue AI can understand your natural language requests and translate them into API-level operations within your connected applications. MCP servers are installed for your entire workspace, so you only need to configure it once for every team member to benefit. {% hint style="success" %} **If you’re new to MCP:** Model Context Protocol is a new open standard that gives language models a uniform way to access external data and tools. This means Glue AI’s capabilities will automatically expand as the MCP ecosystem expands. [Learn more about MCP here](https://www.anthropic.com/news/model-context-protocol). {% endhint %} *** ## 🧠 How Glue works with MCP Glue uses **MCP (Model Context Protocol)** to connect with third-party applications through a standardized interface. ### Key Roles * **Glue AI** acts as the **MCP client**, sending requests. * The **connected application** have an **MCP server**, which receives and responds to those requests. ### Types of MCP Servers To connect an application to Glue, it must have an available MCP server. These come in two forms:
TypeDescriptionSetupExamples
Remote ServerRemotely hosted and maintained by a 3rd party app.Easy/pages/MpK6SIIzudEGCScMwBk7
Open Source Community ServerMust be installed and hosted locally on your device.DifficultFigma, GMail, Hubspot - and more can be found here
{% hint style="info" %} 🔍 **Don’t see a server for the app you need?** Some apps may not yet offer MCP, but more are being developed and released regularly. {% endhint %} *** ## 🔧 Step-by-Step Setup Guide ### Start with the Easy Route — Check the Glue apps directory 1. Go to the **Apps** tab in your Glue inbox. 2. Search for your app in our directory — we’ve already tested and built one-click installs for many popular servers. 3. If you find it, click the name of your app, click the "MCP" button to install. 4. Click **Sign in** and follow the quick authorization flow to connect.\ ✅ *If your app is listed here, you’re done! That’s the easiest setup path.*
### Check other MCP directories for additional servers There are new servers being spun up everyday! Just because one is not listed in our Apps directory doesn't mean there is not an available MCP server. You may need to go through a more manual setup process.
1) Find a compatible MCP server for your app * **Remote / hosted servers** – if the app has an official remote MCP server, we recommend using that over a community server. Glue supports the SSE (Server-Sent Events) transport and streamable HTTP. * **Community servers** – look for one that supports Streamable HTTP, SSE or stdio transport. You can use a proxy to translate stdio to SSE—see below. * Helpful directories: * [**MCP Servers Repository**](https://github.com/modelcontextprotocol/servers) - Complete collection of reference implementations and community servers * [**Awesome MCP Servers**](https://github.com/punkpeye/awesome-mcp-servers) - Curated list of MCP servers {% hint style="warning" %} Many servers are already deprecating SSE support, so we recommend using Streamable HTTP when you can. {% endhint %}
2) Choose how you will run the MCP server The setup steps differ based on the type of MCP server you're using — remote or locally hosted community servers with either Streamable HTTP, SSE or stdio transport support.
ScenarioWhat you needGlue transport
Remote, hosted serverJust the server’s public URL (from the provider)

Streamable HTTP ➜ connect directly

SSE ➜ connect directly

Local, community server (Streamable HTTP or SSE)Run the server + ngrok

Streamable HTTP ➜ connect via ngrok

SSE ➜ connect via ngrok

Local, community server (stdio)Run the server + mcp-proxy + ngrokstdio ➜ mcp-proxy ➜ connet via ngrok
*** #### ☁️ Using a remote/hosted MCP Server (Streamable HTTP or SSE) These are hosted by the third party application itself. Setup is minimal. 1. Follow the provider's setup instructions. 2. Copy the server’s **URL** (e.g. ). 3. Skip to [**Step 3 · Connect the MCP Server to Glue**](#id-3-connect-the-mcp-server-to-glue)**.** #### 🖥️ Using a local community MCP Server (Streamable HTTP, SSE or stdio) Each community server will have an open source instructions list that needs to be followed and will vary based on the app. These are the general steps that will be required. 1. **Install the MCP Server to your local machine** * Follow app-specific instructions (usually in their GitHub README). * Prerequisites may include tools like `Node.js`, `Homebrew`, etc. ```sh # Example: Linear MCP server delivered via npx # replace with the command shown in the server’s README npx @ibraheem4/linear-mcp ``` 2. **Install & launch server via mcp-proxy (stdio only)** – converts stdio ⇄ SSE ```sh brew install uv # light Python runtime used by mcp-proxy uv tool install git+https://github.com/sparfenyuk/mcp-proxy # --pass-environment → passes your shell’s env vars (API keys, etc.) to the server # --sse-port 9000 → local port on which mcp-proxy will expose an SSE endpoint # everything after that is the *command* to start the MCP server mcp-proxy --pass-environment --sse-port=9000 \\ npx @ibraheem4/linear-mcp ``` 3. **Expose your local MCP endpoint to Glue** (Glue cannot reach `localhost`) * Install a proxy like [ngrok](https://ngrok.com/downloads) if you have not already * ngrok shows a forwarding URL like `https://.ngrok-free.app4` ```sh # Install & authenticate ngrok brew install --cask ngrok # Forward the SSE port (9000) with basic auth ngrok http 9000 --basic-auth="YOURUSER:YOURPASS" ``` 4. **Form the Glue-compatible URL** * This URL will allow Glue to route requests securely to your MCP server. ```sh example for SSE :YOURPASS@.ngrok-free.app/sse ``` {% hint style="success" %} 💡 Pro Tip: Choose a unique username/password (must be at least 8 characters).\ Glue will use this to authenticate securely. {% endhint %}
3) Add the MCP Server to Glue 1. Open the Glue app. 2. Click your **profile image** → click **Preferences**. 3. Find the **Labs** section → click **MCP Servers**. 4. Click the **Add MCP server** button. 5. **Name** your MCP server. 6. Paste the **MCP server URL** into the Server URL field. 1. Reminder: If connecting to a local MCP server, use the `ngrok` URL 7. Click **Add server** or follow any additional instructions to sign in and authorize the third party app, as prompted. > ✅ Glue AI is now connected to the app via its MCP server. You will be taken to a details screen where you can [**configure custom rules for the server**](#id-4-configure-rules-for-your-mcp-server-optional-but-recommended) (see step 4).

See the servers that have already been set up and click "Add MCP server" to add more

Example of setting up the official Linear MCP remote server

{% hint style="danger" %} If you paste in your Server URL before naming the Server, you will get an error message and need to press the retry button after you input a name. {% endhint %} {% hint style="info" %} Note: You cannot edit the MCP server configuration once it’s added, simply remove it and re-add if you want to make changes to the URL. {% endhint %}
### Configure Rules for your MCP Server for the best experience Glue AI needs to know certain identifiers about the tool you are calling via MCP to be able to take the action appropriately, like your workspace or team ID. To make the interactions seamless, store this information in the Server's Rules so Glue AI always has access without having to request it each time. {% hint style="info" %} If you've just set up your server, you will be automatically taken to the server details page where you can set rules. {% endhint %} 1. To navigate back to the server rules later, go the Apps section of your inbox, search for the specific app and click on it. 2. Click on the MCP button (it will show a gear icon if it's already been installed). 3. You can set both workspace wide rules under "Shared AI rules" as well as personal ones just for you. These inform how Glue AI should interact with the server. Examples include storing IDs, naming conventions, and templates. 4. Click **save**.
{% hint style="info" %} Do not store any sensitive data in your server rules, like passwords, tokens, or any other authentication-related secrets. OAuth will prompt users to authenticate directly with the MCP server, and securely store the resulting credentials, so there is no need to store them anywhere in Glue. {% endhint %} Here is an example of the rules we have set on our workspace's Linear MCP Server. 
- Web (WEB) team ID: ABC-123
- API (API) team ID: DEF-456
- Glue (GLU) team ID: GHI-789

When creating issues:
- Infer the teamId from context:
    - For issues relating to the API, glue-api, or Glue AI, use the API Team ID.
    - For issues relating to the native app, client, or glue-web, use the Web Team ID.
    - If you do not know, always default to the Glue (GLUE) Team ID.
- Add detailed description in the `description` param, using Markdown where helpful.
- Issue priority should be 3 (Normal) unless otherwise specified.
*** ## 💬 What Can You Do With Glue + MCP? ### **Once connected, Glue AI can** * Make real-time queries to your connected app * Trigger actions via natural language (e.g., “Create a new issue in Linear”) * Use the rules you've set for the server to customize how the server is called
{% hint style="warning" %} Each command requires your confirmation before being executed. {% endhint %} *** ## ⚠️ Support & Limitations | Capability | Supported | | ---------------------------------- | ------------------------------------------------------------------- | | OAuth Support | ✅ | | Header-based auth | ❌ | | Bearer token auth | ❌ | | SSE (Server-Sent Events) Transport | ✅ | | Streamable HTTP Transport | ✅ | | MCP Client Features |

❌ Resources
❌ Prompts
✅ Tools
❌ Sampling
❌ Roots

| | Multi-step tool use | ✅ 5 consecutive tool calls can be made in the same reply | # MCP Server Best Practices ## 📌 Glue AI prompting tips for MCP * Mention the name of the MCP server you want to take action with * Use clear, very specific instructions * *e.g. "Update the status of Issue ID 12345 in Linear to 'In Progress'.”* * Note: You may need [ID numbers](#save-time-by-storing-default-ids-in-server-rules) in order to run specific tasks, which you can [store in the server's custom rules](https://docs.glue.ai/labs/mcp-servers#id-4-configure-rules-for-your-mcp-server-optional-but-recommended) for future requests. * Break a complicated request into multiple parts * e.g. ask Glue AI first to fetch data, then ask it to take action on the data in a separate request * Avoid asking for multiple actions in a single prompt * Specify the format you want the output to be in, such as a table or list — or better yet, save your preferences in AI Rules! *** ## Optimize your experience by configuring rules ### Save time by storing default IDs in server rules When connecting a tool via an MCP server, you often need to provide IDs that identify where or how an action should happen — for example, which **project**, **board**, **database**, or **repository** to create something in. By saving these IDs in your [server's rules](/integrations/mcp-servers#configure-rules-for-your-mcp-server-for-the-best-experience), you can save yourself the step of manually providing IDs each time — Glue AI will do it for you. **Here’s how to discover the necessary IDs:**
Read the tool's MCP manifest or docs Most MCP-exposed tools will document their parameters. Look for: * Required fields (e.g., `project_id`, `repo_name`, `board_id`) * Default-able fields (i.e., things you can pre-fill with a rule) * Example payloads
Use the tool in Glue to see what it asks for Try manually triggering the tool from a thread. If Glue prompts you for a value, that’s a strong hint you can set it ahead of time. > Example: If Glue AI ask *“Which Linear project ID should this go into?”*, that means you could write a rule that injects `"project_id": "proj_abc123"`.
# MCP Server Directory Easily set up your favorite MCP Servers in Glue with just one click Below is a curated list of officially supported MCP servers hosted by trusted third-party apps. Each server includes a quick-install button that will automatically configure it in your Glue preferences—no manual setup required (except for Zapier, which requires a separate process). {% hint style="success" %} Pro tip: You can now set up MCP servers with one click right in the app — look for the Apps section in your inbox and filter by MCP servers. {% endhint %} {% columns fullWidth="false" %} {% column width="50%" %}
#### [Asana](https://developers.asana.com/docs/using-asanas-mcp-server) Create, update, and manage tasks and statuses in Asana’s work management platform. Install Asana ↗ {% endcolumn %} {% column width="50%" %}
#### [Linear](https://linear.app/docs/mcp) Create, update, and track issues in Linear's project management platform. Install Linear ↗ {% endcolumn %} {% endcolumns %} {% columns %} {% column width="50%" %}
#### [Monday](https://developer.monday.com/apps/docs/mondaycom-mcp-integration) Manage boards, items, users, teams, and workspace operations in Monday's project management platform. Install Monday ↗ {% endcolumn %} {% column width="50%" %}
#### [Notion](https://developers.notion.com/docs/mcp) View, search, create, and update Notion pages and databases. Install Notion ↗ {% endcolumn %} {% endcolumns %} {% columns %} {% column %}
#### [Sentry](https://mcp.sentry.dev/) Retrieve and analyze application errors and performance issues from Sentry projects. Install Sentry ↗ {% endcolumn %} {% column %}
#### [Stripe](https://docs.stripe.com/mcp) Create customers, manage subscriptions, and generate payment links through Stripe APIs. Install Stripe ↗ {% endcolumn %} {% endcolumns %} {% columns %} {% column %}
#### [Vercel](https://vercel.com/docs/mcp) Search documentation, manage teams, projects, and deployments. Install Vercel ↗ {% endcolumn %} {% column %}
#### [Zapier](https://help.zapier.com/hc/en-us/articles/36265392843917-Use-Zapier-MCP-with-your-client) Trigger actions across 7,000+ apps using Zapier’s integration platform. Visit [https://mcp.zapier.com](https://mcp.zapier.com/) to generate your server URL. {% endcolumn %} {% endcolumns %} # Release notes ## What's New (Week of May 18th, 2026) ### **🕵️‍♀️ Find keywords in conversation** Use `CMD + F` or `CTRL + F` to quickly locate and jump to keywords or phrases inside the conversation you have open. Check out ["Find in" conversation](/conversations/find-in-conversation) for more.
### **🔡 Adjust Your Text Size** You can now customize the text size in Glue to match your reading preferences. Increase it for better visibility or dial it back to fit more on screen — the choice is yours. Find the setting in your preferences.
Improvements * Code blocks now have a scroll/wrap toggle button, making it easier to read long lines of code without horizontal overflow headaches. * Setting a thread reminder no longer auto-archives the thread. Your reminder is set; the thread stays where it is. * Deleting a thread now requires typing DELETE to confirm — a small guardrail against accidental permanent deletions. * On mobile, the app no longer reopens to your last thread after a long period of inactivity — you'll land on the thread list instead. * Made a set of performance improvements under the hood — faster initial loads and snappier navigation across the app. * We've released an improved new user onboarding experience.
Fixes * Fixed a bug causing Glue AI to get stuck. * Fixed a bug where the "New" marker in Threads view would display incorrectly when switching between Recent and Created sort modes. * Fixed a bug where the sidebar and thread content would briefly go out of sync when navigating to a thread from the drafts section. * Fixed a bug in Windows dark mode where the code block language selector dropdown was missing its background color. * Fixed a brief flash of the message editor that appeared when loading a closed AI session. * Fixed a bug where a reminder message would appear in a thread prematurely after a new message unarchived it. * Fixed a bug where a private draft thread would incorrectly show as public when opened before it was loaded into cache. * Fixed a bug where opening the command palette while the image viewer was open would freeze the app. * Fixed a bug on iOS where push notification delivery was being impacted by the sound setting.
## What's New (Week of May 11th, 2026) ### **🤝 Glue MCP Server** We've launched our Glue MCP Server! Access your conversations with third-party AI agents in Claude, Cursor, Codex, or your client of choice. Check out [Using Glue with Claude](/integrations/using-glue-with-claude) to get set up. ### 🔓 Public/private toggle in the message editor We’ve added a thread visibility toggle to the message editor, making it easier to choose whether a thread is public or private before sending it to a group chat or another thread. Threads sent to group chats will default to public unless you switch them to private. Look for your workspace logo to indicate a public thread, or the lock icon for a private one. See [Public threads launch](/conversations/threads/public-threads-launch) for more info.
### 🔎 Search in the Threads view You can now filter by search terms in the threads view, making it easier to find the conversations you're looking for. This matches thread names only right now.
Improvements * Switching between threads is now noticeably snappier — the app stays responsive while the new thread loads, and you won't see a blank flash between views. * Apps in the Thread Details panel are now sorted by workspace first, then alphabetically, so finding the right app is faster. * The AI model dropdown in preferences is now fully responsive in the desktop app. * Pending invited users now appear in your workspace so you can see who's been invited but hasn't joined yet. * Profile pictures can now be removed — you're no longer locked in once you've set one.
Fixes * Fixed threads unexpectedly auto-opening when new messages were sent in certain views. * Fixed an infinite redirect loop in the MCP OAuth authorization flow. * Fixed a bug where the message ID parameter was lost when opening a reply thread from a linked message, breaking deep links. * Fixed a loop where tapping back from an AI session on mobile could leave the app stuck between views. * Fixed the message composer freezing and disabling send when a user typed a backtick followed by a colon. * Fixed the "Remove server" option appearing in MCP config for users who don't have permission to remove servers. * Fixed delayed or missing message delivery when returning to an active thread during websocket reconnection. * Fixed an intermittent dropdown rendering issue where a hairline border would appear instead of dropdown content. * Fixed the "Threads" button from a group not consistently landing on a filtered thread view. * Fixed a nested button accessibility issue in the AI tool call expandable view. * Fixed the GlueAI support bot so it now only responds in new threads, not existing ones.
## What's New (Week of May 4th, 2026) ### **👀** Read receipts No more wondering if your message landed or disappeared into the void: you can now see if your messages have been read with an avatar indicator by your message. You can see up to six people who have read + a count of the additional people who read.
Improvements * Navigating between threads is significantly more responsive. We've rearchitected how Glue updates the UI when you move between conversations, reducing render time and keeping the inbox and sidebar feeling snappy even when the app is busy. * You can now remove your profile photo entirely — not just replace it. * Glue AI now shows real-time progress as it works through tool calls. Each step (thinking, preparing, confirming) is visible as it happens, so you always know what's going on. * Reverted the unified "Chats" section for DMs and group chats based on your feedback. Your chats are back to their original, separate organization. * App users (bots and integrations) are no longer included in group or workspace member counts. * MCP-connected tools now receive information about who is making the request, so Glue AI can respond more accurately in contexts where your identity matters.
Fixes * Fixed a bug where threads would automatically open when new messages arrived, even when you hadn't selected them. * Fixed a bug where Glue AI tool calls would get stuck in a "Thinking" or "Preparing" state and never progress to the next step. * Glue AI's search now correctly surfaces the most recent results when you ask for the latest on a topic — a sorting and cursor issue was causing stale results to appear.
## What's New (Week of April 27th, 2026) ### **🔗 Get updates from Jira right in your threads** Share any [Jira](/integrations/jira) link (issue, epic, project, board) in a thread and Glue will automatically show a rich link preview that updates in real time. You'll also get system updates in the thread from the linked Jira object, so your team stays in the loop without switching tools. This adds to our existing support for the Atlassian MCP server that lets you take action in Jira right from Glue! ### **⚡App setup made easy — paste a link and connect!** Paste a link from one of our supported apps (Jira, GitHub, Linear, and more) into any message and Glue will prompt you to connect the app right there. No more searching to see if the app is already connected.
Improvements * When you fork a reply thread from a message, a notification now appears in the original thread so other participants can find the new sub-thread easily. If you're replying to the most recent message, the notification is skipped to keep things clean. * New users will now see Glue tips right at the top of their threads for the first two weeks. * The notification permission prompt during onboarding now appears as a final step before you enter the app, rather than popping up over everything after you've loaded in. * The App Directory now has an "Added" filter so you can quickly see which apps and MCP servers you've already connected to the workspace. * "Go to Directory" and "Go to People" shortcuts are now available in the command palette, matching the existing "Go to Groups" and "Go to Apps" options. * The compose and reply experience has been updated so that the main composer, thread reply, and message reply editors all work together more cohesively.
Fixes * Fixed a bug where switching between thread panes with a sidebar open caused display issues. * Fixed the Join button during workspace onboarding not disabling after clicking, which could send duplicate requests. * Fixed keyboard navigation issues: pressing Escape from the thread compose modal now correctly returns focus to the button that opened it. * Fixed the message actions toolbar covering message content on hover. * Fixed the OAuth consent page not redirecting properly when authenticating through certain third-party MCP clients. * Fixed GitHub app installation not being triggered during MCP OAuth setup, which previously left new users unable to access GitHub tools after connecting.
## What's New (Week of April 20th, 2026) ### 🤖 Cursor Integration **`New in beta:`** You can now kick off Cursor AI agents directly from a Glue thread. Connect your Cursor project, start a conversation, and the agent's progress updates live in the thread — no tab-switching, no copy-pasting results back to your team. Everything stays in context, where the discussion already is. Add the [Cursor](/integrations/cursor) app to your workspace to get started. ### 📌 Find all your pins in one spot Pinned messages now live in the thread sidebar. Pinning a message opens the sidebar directly, and all your pinned items — messages, threads and links — are collected in one place. Never lose context again! ![](/files/m9tEps0YHpu5HMug9mg9)
Improvements * Improved the group creation flow with clearer labels, explainer text, and suggestion chips to help you name and set up your group right from the start. * Custom OAuth apps now appear in the App Directory alongside native integrations, with a "Custom" badge so they're easy to spot.
Fixes * Fixed a bug where tapping "Chat" or "Threads" on a group result in search would do nothing. * Fixed a bug where tapping a thread notification would sometimes open a previous user profile instead of the notification target. * Fixed a bug where the "New" divider in the Threads tab would stick to the top of the view while scrolling instead of staying inline. * Fixed a bug where the emoji picker couldn't be opened via keyboard from the floating message actions bar. * Fixed a bug where double-clicking when branching from a message could create a duplicate draft thread. * Fixed a bug where the edit icon on a thread wouldn't disappear after an AI session was shared. * Fixed a bug where the GitHub app modal wouldn't reflect the installation state — users had to close and reopen it to select a repo. * Fixed a bug where loading older messages in a thread could cause duplicate fetches and infinite scroll not terminating.
## What's New (Week of April 13th, 2026)
Improvements * Hovering over the Chats section in the sidebar now reveals a **+** button, making it clear where to kick off a direct message. * Group members now receive all thread activity in their inbox by default when they join a group. * The threads feed no longer shifts layout when the scrollbar appears or disappears.
Fixes * Fixed a bug where edits would disappear if you scrolled while editing a message. * Fixed an error that required a full reload when a thread was deleted while you had it open. * Fixed a crash that could occur when deleting a message with a reply thread open in the side pane. * Fixed messages appearing to send while offline but vanishing after reconnecting. * Fixed attachments in AI sessions not being clickable. * Fixed the inbox resorting threads while you were actively reading them. * Fixed a scrolling bug on mobile where loading older messages would jump you to the bottom. * Fixed scroll position resetting in AI sessions on Safari when using an external mouse. * Fixed the Message button in the people directory doing nothing when clicked. * Fixed the emoji picker activating when pressing Enter after typing a colon with no search term. * Fixed duplicate threads appearing in the threads feed. * Fixed keyboard focus not returning to the right place after closing a dropdown or popup.
## What's New (Week of April 6th, 2026) ### 🧪 Get early access to beta features Admins can now enable beta features for your entire workspace from your workspace settings. We will be constantly adding pre-release features here for testing and feedback before they go live. We'd love to hear from you! Go to advanced > enable beta features, and you can [read more about the beta program here](/release-notes/beta-features). ### Simplified Chats: Groups and DMs, now in one chat space **`New in beta:`** The sidebar now combines Groups and DMs into a unified Chat section. This UX improvement makes messaging feel more streamlined, organized, and easier to navigate.
Improvements * Browser notifications now dismiss automatically without needing to be clicked away. * When multiple Notion properties are updated at once, all of the changes now appear in Glue instead of just the most recent one. * Reminders are now automatically cleared if you lose access to the thread they were set on. * The thread members row in the sidebar is now fully clickable, with no dead zones near the edges.
Fixes * Fixed the Message button in Android user profiles doing nothing when tapped. * Fixed a bug where app event notifications (like GitHub updates) were incorrectly grouped together when a message had been sent between them. * Fixed Glue AI failing on a second Notion lookup when two were needed in the same response. * Fixed user avatars not appearing at full size after a sequence of deleted messages. * Fixed a bug that required pressing the back button twice to exit search results. * Fixed duplicate confirmation messages appearing on mobile when pinning or subscribing to an app. * Fixed search getting stuck in an empty state, making it impossible to open threads. * Fixed a mobile bug where tapping a reaction could accidentally trigger a tap on a nearby username.
## What's New (Week of March 30th, 2026) ### 🕴Hover for message actions For a more polished experience, we've made message actions visible only on hover. Hovering over a message will highlight it with a subtle background, and give you quick access to your most important message actions, including your recent emoji reactions.
Improvements * You can now search for members, see a total member count, add people with a dedicated button, and access per-member actions right in the thread members list. * Clicking on a group now opens the group details directly instead of closing the panel. * When both a Notion database and a page within it are subscribed in the same thread, Glue now deduplicates events so you don't see the same update twice. * Modals now support drag-to-close on mobile, making them easier to dismiss. * Push notifications now arrive more quickly after you step away from the app.
Fixes * Fixed several small issues in the thread members list, including incorrect member labels for groups and unresponsive row clicks. * Fixed a bug where pressing Enter after typing something like "D:" would insert an emoji instead of creating a new line. * Fixed the Back button in the Directory on mobile routing to the wrong place depending on how you arrived. * Fixed the app crashing when opening a thread by URL directly or doing a hard refresh. * Fixed SVG files failing to attach with an invalid image format error. * Fixed a broken icon appearing in app unfurls when the associated image URL fails to load.
## What's New (Week of March 23rd, 2026) ### 📝 Public threads are here! **You can now make threads visible to your whole workspace,** without notifying everyone. Share broadly, @mention only who needs to act, and let your team browse updates on their own terms. Look for the public/private toggle when you draft a new thread or in thread details. All your existing threads remain private. Browse all threads in the new threads view!
Improvements * The emoji picker is lighter and faster, with a smoother experience and saved skin tone preference. * Threads view now makes new items easier to spot with a clearer divider and stronger unread styling. * Threads view received a visual polish pass for cleaner spacing, icons, and header styling. * Mobile messages now use a cleaner long-press menu with quick reactions and copy text built in. * Group profile actions were reorganized so common actions like starting a thread are easier to find. * Onboarding links for apps now take people to the Apps directory, which is a much better place to browse and manage them. * Disabled buttons can now show helpful tooltips when there’s useful context to explain why an action isn’t available.
Fixes * Fixed a bug where the subject suggestion button could get stuck and stop working. * Fixed new thread notifications so they open the correct thread in the Threads view. * Fixed cases where starting a new thread from Threads view didn’t actually open the new thread. * Fixed a tooltip bug that could briefly jump to the top-left corner of the app. * Fixed the Cmd key getting “stuck” after switching apps on Mac, which could trigger the wrong pane action. * Fixed mobile back-navigation issues caused by route memory getting out of sync. * Fixed keyboard navigation in the top area of the app so search and compose behave more predictably. * Fixed a double-modal issue when long-pressing message reactions on mobile. * Fixed problems pinning the same resource across different workspaces. * Fixed external group member lists so guests can see members correctly. * Fixed support for searching people within a thread’s members list. * Fixed some Plain sync errors affecting customer chat messages.
## What's New (Week of March 16th, 2026) ### **🧹 Simplified Glue inbox** We have a new threads view that lets you browse all your threads and filter by group. We've also brought together Groups, Apps, and DMs into one directory section to streamline the inbox to focus on what you quickly need access to. ### **🔎 Scoped search now works on mobile** Mobile search now supports scoped search, so it’s easier to narrow results and jump to the right conversation even on smaller screens.
Improvements * New thread system messages now include the name of the person who started the thread. * New thread notifications now take you straight to the Threads view with the right thread selected. * Reply composer now starts long quoted messages scrolled to the most relevant point, just like a real thread. * You can now select text inside the reply-to message when composing a reply. * The thread composer layout is cleaner, with the Notify control moved inline with privacy settings. * Directory got several mobile polish updates, including a cleaner header and better use of space. * Group and workspace member lists now load more smoothly with improved pagination support. * Navigation has been tidied up, with Directory moved above Activity. * Shared AI session attachments now appear more neatly nested inside the session.
Fixes * Fixed cases where app event updates could stop after a Linear issue changed teams. * Fixed group chats so silent “new thread” system messages no longer create unread badges. * Fixed mentioned users and groups being handled more intelligently when they already have access to a thread. * Fixed group notification changes so switching to “Everything” no longer dumps old threads into your inbox. * Fixed a bug where starting a new thread from the Threads view did not open the thread. * Fixed reopened drafts being sendable without recipients. * Fixed the empty-state message not appearing when no threads were found in expanded Threads view. * Fixed the People directory so scrolling pagination no longer breaks. * Fixed newly created groups so they appear in the Groups directory right away. * Fixed recipient search so people already added to a thread no longer keep showing up in results. * Fixed new workspaces showing an empty inbox instead of loading content properly. * Fixed the user profile pane so avatar loading stays in sync when switching between users. * Fixed the thread compose settings menu positioning. * Fixed fullscreen video on Mac so controls no longer hide behind window buttons. * Fixed emoji validation so status suggestions match what can actually be saved.
## What's New (Week of March 9th, 2026)
Improvements * Shared app links can now reflect refreshed titles and descriptions, so the details you see in Glue stay closer to the source. * People and Groups tabs now include onboarding cards to help new users get started faster. * User profile panes now show internal email addresses with a handy copy button. * Group member lists now let you click straight into a user’s profile. * Directory detail views were refreshed for a cleaner, more navigable experience. * Search routing is more consistent, so results take you to the place that makes the most sense. * Directory layouts on desktop now make better use of available space. * The “not in thread” view has been refreshed to better match the rest of the app. * Reply threads now handle mentions more naturally, matching the main editor experience.
Fixes * Fixed app event subscriptions so deleting the only shared app link in a thread stops future updates for that item. * Fixed custom titles being overwritten when sharing an AI thread. * Fixed Excel and Numbers paste behavior so copied cells paste more cleanly instead of showing up as a broken image. * Fixed pinned messages in split view so they open in the correct pane instead of duplicating the thread elsewhere. * Fixed newly added emojis not becoming available right away. * Fixed a groups directory reload when switching from the People tab. * Fixed Cmd+Click on a group in the Directory causing a reload/flash. * Fixed mobile back buttons in user and app profile panes. * Fixed support threads closed in Glue so they correctly sync as done in Plain. * Fixed system messages taking up more space than necessary, especially on mobile.
## What's New (Week of March 2nd, 2026) ### **💨 New search shortcut** You can now jump into scoped search by typing prefixes like `in:`—no need to remember special syntax. It’s quicker, more intuitive, and built to scale as search gets even more powerful.
Improvements * Clearer language in menus: “Resume updates” and “Stop updates” replace the more confusing subscribe/unsubscribe labels. * System messages have a refreshed design for better readability and consistency. * Filter inputs now feel instant, showing local results immediately while updating in the background. * You can now filter threads by the General group, making it easier to find key conversations. * Improved display of scoped search results with clearer context. * Directory views (Groups, People, Apps) are more consistent and easier to navigate. * Workspace switcher now supports external views when you're outside a workspace. * Buttons and UI elements feel more polished with updated spacing and rounded corners. * The thread sidebar now behaves more intelligently on smaller screens, staying out of your way when space is tight. * You can now click your own avatar in messages to view your profile.
Fixes * Fixed incorrect member counts in threads and groups. * Fixed an issue where mentioning someone in a reply thread didn’t notify them properly. * Fixed crashes when selecting certain groups from the feed. * Fixed empty modals appearing when opening some thread details (including AI sessions). * Fixed layout jump when adding recipients while composing a thread. * Fixed sluggish filtering behavior when typing in search inputs. * Fixed user status presets unexpectedly changing emojis. * Fixed cases where the thread sidebar wouldn’t behave correctly on resize.
## What's New (Week of February 23rd, 2026) ### 🔔 Manage app event subscriptions from threads You can now subscribe or unsubscribe from app events directly from thread resources, giving you more control over which connected-app updates land in your flow. Click the ellipsis next to the shared link. ![](/files/3Zb1vFxXu7hOXIn3aaya)
Improvements * Code snippets in Glue now include a handy Copy button, so it’s faster to grab and paste code without the extra selecting and scrolling. * New workspaces now open with the first onboarding thread selected in Inbox, making it easier to get started right away. * New users won’t see the feature banner during workspace setup, which keeps onboarding a little calmer and a lot less crowded. * The expanded work schedule view now uses larger text for better readability. * The Windows app experience is clearer, with cleaner presentation around the app URL.
Fixes * Fixed cases where messages could get stuck on an older view instead of loading the latest conversation. * Fixed attachment uploads that could fail, especially on weaker connections. * Fixed group member role changes that were not always saving correctly. * Fixed group chat member counts showing the wrong total. * Fixed an issue where you could not create a thread with only yourself as the recipient. * Fixed pinned thread titles in the sidebar so they update when the original thread title changes. * Fixed a case where the sidebar would not open when an AI session ID was present in the URL. * Fixed AI responses that could incorrectly include thread attachments. * Fixed preset statuses changing to unexpected emojis while editing. * Fixed the new messages chip being hidden behind the app update banner.
## What's New (Week of February 16th, 2026) ### 💡Auto-subscribe threads to updates from apps **Sharing a GitHub PR or Linear issue in a thread? Your thread will now automatically subscribe to events from that link** — so you'll see notifications like merges, status changes, and more right in the conversation where it matters. To enable this, keep the link preview attachment when sending. To opt out, remove the attachment before sending. We will be adding support for more apps soon — let us know if there's one you'd like to see this functionality with!
{% hint style="info" %} Bonus: GitHub and Linear link previews now reflect the latest status in real time. {% endhint %}
Improvements * When you ask Glue AI to search “this thread,” it now keeps results scoped to the current thread. * Added a new preset status: **🍽️ Eating**. * GitHub link previews now fail more gracefully when a repo isn’t accessible (no more broken-looking unfurls). * Reduced noise from group description changes by consolidating system updates.
Fixes * Fixed messages sometimes getting stuck on an older window and not loading the latest content without a refresh. * Fixed attachment uploads failing more often on unreliable connections. * Fixed AI sources not showing the thread identifier in results (regression). * Fixed a relevance-scoring bug where AI search previews only used the first message and missed important context later in the thread. * Fixed an OAuth token edge case that could error with “oauth client: not found.” * Fixed iPad windowed mode layout issues (now respects the window size, not the full screen size). * Fixed a mobile issue where the thread sidebar could render full-width after creating a thread. * Fixed AI thread header subjects getting cut off.
## What's New (Week of February 9th, 2026) ### ✨ Refine AI responses before sharing to your thread Now you can have a full back-and-forth conversation with Glue AI right from your message editor. Iterate on responses, ask follow-ups, and get the output just right before sharing it with your team.
### **🔌 Clarify.ai + Gleap.io MCP servers** Two new MCP servers are now available to connect: * **Clarify.ai** for insights across CRM data and support tickets * **Gleap.io** for support ticket insights {% hint style="info" %} You can suggest new MCP servers and app integrations [here](https://gluegroups.typeform.com/to/MyMonN0i). {% endhint %}
Improvements * Public API now exposes `pinResource`, making it easier for integrations to pin key items without rebuilding full thread hierarchy logic. * Mark notifications as **seen** automatically when you read the related message, keeping your feed state more accurate.
Fixes * Fixed group member counts not updating after removing someone from a group. * Fixed the “+ Add new member” button missing in the group members modal for some groups. * Fixed inbox badge counts sometimes getting out of sync with the actual inbox until the app was restarted. * Fixed thread follow status being determined incorrectly in some cases (follow state now reflects the right recipient/subscription logic). * Fixed MCP SSE requests using the wrong HTTP method for some servers (now uses POST as expected).
## What's New (Week of February 2nd, 2026) ### **🔍 Scoped search** Finding the right message just got a whole lot easier with [scoped search](/inbox/search#starting-a-scoped-search). You can now search *within* a specific thread, group chat, or DM—so results stay focused on the conversation that matters. You can start your search from an open chat, use ⌘F / Ctrl+F, or use the `@` in the search bar. ### **🛡️ Workspace admins can manage groups—even if they’re not members** Workspace admins can now approve/deny join requests, archive groups, and access group settings without having to join the group first. Handy for keeping things moving without extra hoops.
Improvements * Made it possible to add yourself to a thread individually, so you can clean up group memberships without losing access to important conversations. * Added faster navigation via the command palette, with shortcuts to key areas like AI, Feed, Groups, DMs, Activity, Apps, plus Inbox and Archive.
Fixes * Fixed a Chrome sign-in issue that could show a “layout not found” error after login. * Fixed reminders that could create repeated “phantom” reminder posts if a thread wasn’t opened for a while. * Fixed @mention search failing when punctuation appeared right before the “@”. * Fixed DM previews showing stray backslashes when messages included copied asterisks. * Fixed the editor auto-focusing on touch devices like iPad (especially annoying in landscape). * Fixed the “Start new thread” option appearing when it shouldn’t for messages that already have a reply thread. * Fixed thread counts not updating immediately after bulk archive actions. * Fixed awkward activity text when a group description was cleared. * Fixed thread access behavior after a related group was removed, so the app fails more gracefully. * Fixed cases where newly created records could get slightly different created/updated timestamps. * Fixed a rare crash when processing certain markdown-style message text.
## What's New (Week of January 26th, 2026) ### 🗒️ Start threads or DMs with yourself Need a private place for notes or drafts? You can now easily start a thread or DM with just yourself — no workarounds required.
Improvements * Added thread actions to the command palette — starting a zoom or google meet, or sending a GIF. * Implemented system messages when group descriptions change. * Improved how internal system messages appear to provide clearer context for group changes. * Made draft behavior more flexible to better support recipient role usage. * Improved general search relevance so results better match what you’re actually looking for.
Fixes * Fixed incorrect link copying that pasted internal URLs instead of shareable Glue links. * Fixed markdown being incorrectly escaped in message previews. * Fixed Google Drive links not always prompting for authorization. * Fixed crashes related to user consent and recipient cleanup edge cases. * Fixed visual sizing issues in facepile avatars. * Fixed billing-related popups appearing during short payment processing delays.
## What's New (Week of January 19th, 2026) ### **⚙️ Auto-Save for Preferences** No more lost settings! Preferences now save automatically as you make changes—no need to scroll down to click “save.” This update is especially helpful on mobile, where accidental exits were all too common.
Improvements * Sidebar toggle now remembers your last view—less clicking around. * Searching for users via command palette or top-level search now routes to the inbox instead of the DMs view.
Fixes * Fixed a bug that caused the app to hang when bulk archiving large numbers of threads. * Fixed an issue where voice notes were getting cut off on Mac after recording. * Fixed an “Invalid constraint” error that blocked voice note recording—clearing mic preferences now restores functionality. * Fixed an issue where thread starter messages disappeared when modifying recipients in reply threads. * Fixed an issue where draft threads could appear without content. * Fixed a bug where copy/pasting mentions would paste full URLs instead of @mentions. * Fixed a markdown issue that added backslashes to special characters when copying messages on Windows. * Fixed the file attach menu popping up in weird spots on Android. * Fixed a bug causing mobile DMs to show an empty state during loading instead of cached content.
## What's New (Week of January 12th, 2026) ### ⚡ Move faster with the new Command Palette The Command Palette (`Cmd+K` on Mac/ `Ctrl+K` on Windows/Linux) gives you keyboard superpowers. Instantly jump to conversations, start new threads, rename threads, archive old ones — all without lifting your hands from the keyboard. No more clicking around menus or hunting for settings. Just open the palette, type what you need, and go.
Try it out with: * `New thread` to kick off a new topic * `Close thread` to signal to others that the conversation is done * `Mark unread` to indicate you need to follow up on the item later
Improvements * The thread resources sidebar is now resizable, and a double‑click resets the size.
Fixes * Fixed the scroll position in threads so it stays at the bottom on initial load (newest messages visible first). * Fixed initial hyperlink rendering issues that were causing links to display incorrectly. * Fixed the thread view so clicking on a second quote reply no longer reloads the chat unexpectedly. * Fixed an issue where emojis would break out of the message container and overflow visually. * Fixed how code snippets and underscores display in search results so inline formatting is preserved. * Fixed messages where words in angled brackets were disappearing when sent.
## What's New (Week of January 5th, 2026) ### 💡Voice Notes improvements **Audio settings now in Preferences** Manage your microphone and speaker settings directly from the Preferences menu. Includes a handy test button. **Keyboard shortcuts for voice notes**\ Now you can press **Enter** to confirm or **Esc** to cancel—no mouse required.
Improvements * Added a 100-character limit for workspace names to prevent overly long titles. * You can now preview videos directly from the editor—no publishing needed.
Fixes * Fixed an issue where reply threads only worked on messages that already had replies. * Fixed AI drafts not clearing properly when deleted in the tabbed editor. * Fixed the editor auto-switching to the AI tab when restoring unsaved drafts. * Fixed permission issues that blocked voice note recording on some Android devices. * Fixed a layout bug where the “Create Group” modal could be cut off on shorter screens.
## What's New (Week of December 22nd, 2025)
Fixes * Fixed an issue where canceled tool calls could disappear when navigating back to a thread. * Fixed a bug where selecting a thread from search sometimes required clicking twice. * Fixed broken “Contact Support” and “See Import Status” links in the Slack import error message. * Fixed clipping issue with the voice note recording box on iPad. * Fixed layout squishing when playing a voice note in threads on iPad. * Fixed AI model selector opening in the wrong spot on iPad.
## What's New (Week of December 15th, 2025) ### 🎙️ Voice Notes are here! You can now **record and send voice messages directly in Glue.** Sometimes typing just doesn't cut it—add tone, personality, and nuance to your conversations, in your own voice. 1. Tap the new record (microphone) button in the message composer 2. Talk for up to 5 minutes 3. Hit the check mark or enter to finalize 4. You can play back your recording before hitting send *🎶 You know you want to gift your coworkers with your best caroling attempt as a holiday send off. Do ittttt.*
Improvements * Preview images and files before you send them, directly from the editor. Just click on the attachment to open a preview. * Copying and pasting tables from Glue AI now preserves formatting. * Restored the draft-saving indicator in the compose editor. * Restored sparkle indicator when a thread title is being generated. * Fixed emoji suggester being cut off in the composer. * Switched to compact avatars in AI chat messages. * Instant search results are deduplicated for clarity. * iPad dark mode background colors now consistent across sections. * Improved handling of deleted threads with smoother redirection.
Fixes * Fixed split pane staying open after deleting a draft thread. * Fixed emoji status bug where certain emojis showed a red question mark. * Fixed invalid join request buttons for DMs and group chats. * Fixed mention menu disappearing after typing `@` with inline markdown. * Fixed AI chat send button not disabling immediately, preventing duplicates. * Fixed bouncing layout when expanding/collapsing AI tool calls. * Fixed subject suggestions not reappearing after sending a thread. * Fixed expired invite links being copied due to caching. * Fixed attachment-only messages showing blank notifications. * Fixed backslash escaping in copied code blocks on Mac. * Fixed quick search results auto-scrolling on hover. * Fixed secondary pane close button getting stuck in “swap” mode. * Fixed “More/Less” buttons lingering after inbox bulk actions. * Fixed DM panel not refreshing with new messages across platforms.
## What's New (Week of December 8th, 2025) ### 📎 Resource Sidebar: your conversations, with memory Ever find yourself thinking *“wait… where’s that link?”*\ We’ve got you. Meet the **Resource Sidebar** — a new panel on the right side of every thread that keeps track of everything shared in the conversation. * **📌 Pinned** — essential resources so everyone has the same context * **🔗 Recent Links** — auto-populated with shared threads and URLs * **🖼️ Recent Media** — a visual grid of all shared images and videos Found something worth keeping around in the recents section? Click **+** to pin it and keep everyone on the same page — literally.
No setup, no extra work. The sidebar stays up to date automatically, and you only pin what actually matters. 👉 Try it now: open a thread and **click "show resources."** ### **⬆️ Edit Last Message Shortcut** You can now press `CMD+ArrowUp` key in an empty message box to quickly edit your last sent message. ### **🤠 Custom emojis, now in messages!** You can now search for and send your custom emojis in messages. Your team's inside jokes and branded icons just got a lot more expressive.
Improvements * Enabled sending unfurled links without requiring a message * Synced search input with the `q` URL parameter for shareable and refresh-safe searches * Improved visual polish for Glue AI threads and closed thread icons in the History sidebar. * Rebuilt navigation history to improve accuracy, reduce duplicates, and support more view types * Restyled thread composer with cleaner layout, updated buttons, and simplified draft UI * Collapsed GIFs by default with click-to-play behavior for a calmer message feed * Combined group creation steps into a single, simplified screen * Removed auto-open behavior for sidebars on window resize and tab switching * Displayed animated WEBP thumbnails as static previews with hover-to-play * Removed trailing empty lines after lists and block quotes for smoother backspacing * Improved display of emoji-only group names in the sidebar * Truncated long thread names and added appropriate icons in the history view
Fixes * Fixed issue where threads sometimes required opening twice to be marked as read * Fixed image pasting from gallery view inserting both the image and its URL * Fixed broken mention formatting when thread subjects included backticks * Fixed scrolling bar appearing in empty resource search results * Fixed incorrect lock icon showing on threads that aren’t private * Fixed sidebar not updating immediately after leaving a group * Fixed sidebar appearing in full width when returning to a thread view * Fixed stuck search bar in macOS app after closing a thread * Fixed quote replies not displaying link-only messages correctly * Fixed crash caused by undefined user IDs in the recent DMs list
## What's New (Week of December 1st, 2025) ### 🙏 Giphy has landed! You can now spark joy, drama, or chaotic energy by using: * The **slash command**: just type `/` and pick "Send GIF" * Or tap the **slash icon** in the message composer {% hint style="success" %} Add the Giphy app to your workspace from the Apps tab. {% endhint %} **A quick heads-up: we're still actively working on expanding the selection** so your meme potential can reach its full, majestic power. Go forth and GIF responsibly! ✨
Improvements * Reduced the visible portion of the starred section to 10 items for a cleaner view — expand to see more. * Tabs and sections now default to their proper empty state when switching views, avoiding leftover content confusion. * Status emojis now appear next to a person's name in the Direct Messages tab.
Fixes * Fixed an issue where prompts from previous Glue AI threads were appearing in new ones. * Fixed an issue where typing in the search bar while starting a new DM would unexpectedly move the cursor to another field. * Fixed layout issues caused by native keyboard resizing interfering with content safe areas on mobile. * Fixed a crash caused by `d.categories` being undefined during certain interactions. * Fixed an issue where message notifications on macOS didn’t include the sender’s name—now they match iOS behavior. * Fixed a security vulnerability related to file pattern handling (Glob).
## What's New (Week of November 24th, 2025) ### 📝 Statuses are here! You can now set a personal status from your profile menu. Let people know you’re OOO, AFK, or in a pie coma. You can choose from one of our quick presets or fully customize your emoji, text, and duration. *Now why are you reading these release notes? Go set your status to: 🦃 turkey trotting away from the keyboard.*
Improvements * Clarified the empty state in the Glue AI tab so it no longer pretends you're mid-search when you're not. * Added a character limit (150) to long search strings to prevent timeouts and improve performance. * Cleaned up the inline link pinning experience with a sleeker, static form. * Removed recipient suggestions from the thread composer to reduce clutter and streamline.
Fixes * Fixed a bug that caused numbered lists to reset after sending when the list didn't start with the number 1. * Fixed an issue where quote formatting with nested bullet points lost its structure after sending. * Fixed a confusing error message from an external library that could appear when pasting in the editor. * Fixed deleted threads still appearing in search results when composing messages.
## What's New (Week of November 17th, 2025)
Improvements * Renamed the “Flag” message action to “Report” to make it clearer what the button does, and added a confirmation modal that explains what happens next. * Updated the profile view to only show your primary and mutual workspaces with someone else—no more clutter. * Refined the “Sign in with Apple” button to use a white icon in dark mode. * Increased the clickable area for thread actions in the inbox to make them easier to find. * Synced the height of date and time pickers for a more balanced look in reminders and status updates.
Fixes * Fixed drag-and-drop issues when uploading attachments in the Windows app. * YouTube videos now play correctly in threads—no more "Error 153" interruptions. * Fixed video thumbnails not showing up in the shared media view. * Fixed broken behavior where copying text from timeline messages would turn it into a bulleted list. * Fixed visual inconsistencies with the checkbox icon appearing thinner than others.
## What's New (Week of November 10th, 2025)
Improvements * Glue now checks for required app updates before fully launching, so if you are required to update you won't be interrupted in a session. * Starred section page size reduced from 20 to 10 for faster loading. * Sidebar open/close icons now clearly reflect state. * App install banners now behave correctly after signing in on mobile. * Long URLs in hover tooltips now wrap cleanly and stay readable. * Adjusted tooltips for perfect placement, padding, and dark mode polish. * Modal forms now auto-focus the first input to speed up interactions.
Fixes * Fixed drafts not being saved when starting a new DM with someone you haven’t messaged before. * Fixed blank popups when clicking on recipients in threads you’re not part of. * Fixed infinite loading for thread attachments when you’re not a recipient. * Fixed UI collision by hiding the “back to top” button during bulk select mode. * Fixed sidebar state flickering when resizing with a secondary pane open. * Fixed AI message borders on mobile.
## What's New (Week of November 3rd, 2025) ### 🔄 Never miss a Glue release Glue now shows a banner whenever a new version is available—no detective work required. Tap it to jump straight to your app store and update. Easy, fast, and you’ll always be running the latest, greatest Glue.
Improvements * Bulk-select checkboxes in the sidebar now show a helpful “Select thread” tooltip. * Disabled read-only workspaces from being selectable in dropdowns where they don’t apply. * Updated the reply count on thread attachments to reflect actual replies, not repliers. * Clarified app descriptions for Webhook and OAuth integrations. * Improved deactivated user experience — no more blank popups. * Added onboarding guardrails: team size field now behaves as required. * Upgraded logo handling due to Clearbit’s logo API sunset.
Fixes * Fixed draft deletion logic to ensure only the correct editor pane closes. * Fixed unread marker inconsistencies in threads — they now reliably show where they should. * Fixed AI responses displaying incorrect source counts or misrendered characters like `/`. * Fixed hover image previews shrinking too much and getting blocked by download buttons. * Fixed bug where sidebar’s “Browse Groups” option didn’t work in Feed or Activity views. * Fixed unexpected billing modal flash on app startup. * Fixed Enter key behavior in the Glue AI tab not matching user settings. * Fixed slash character rendering as `[Object object]` in AI source lists. * Fixed incorrect glue AI message grouping when replying to older messages. * Fixed app layout showing when an update is required to have a full screen prompt. * Fixed edge case where submitting empty thread sessions was still allowed.
## What's New (Week of October 27th, 2025)
Improvements * Easier bulk-select in the sidebar. Hovering over any part of a thread now reveals the bulk-select checkbox. * Updated webhook and OAuth app descriptions in Workspace settings for clearer guidance. * Added a remove button directly in the MCP server modal — no need to dig through settings anymore.
## What's New (Week of October 20th, 2025)
Improvements * Newly added workspaces now show up instantly in the Workspaces menu. * Unified and streamlined workspace selector components. * Virtualized the Groups Directory for smoother scrolling. * Improved emoji picker behavior: unsupported emojis now show a clear message. * Reduced unnecessary data fetching when the app loads or refreshes. * App pane now shows a proper “App not found” screen when needed. * New users now land on the Glue AI view after onboarding.
Fixes * Fixed black backgrounds behind custom emojis in Safari. * Fixed issue where threads with only a pasted link couldn’t be sent. * Fixed loading bug when viewing thread attachments you’re not part of. * Fixed resize handle glitch in Safari and the Mac app. * Fixed cropped thread names in long message drafts. * Fixed duplicate meeting messages triggered by repeated sign-ins. * Fixed starred threads being incorrectly marked as archived after setting reminders. * Fixed third draft being inaccessible on mobile. * Fixed network banner showing for retryable errors. * Fixed threaducation banner appearing across user sessions or restricted views. * Fixed workspace list not refreshing after adding a new one.
## What's New (Week of October 13th, 2025) ### 🔌 Glue's Public API is now in beta Thanks to our new API, you can now create complex custom workflows and integrations that work exactly how your team does. Build on top of Glue’s platform to automate tasks, connect to rich historical data, and utilize Glue’s powerful thread-based structure. [**Explore the docs →**](https://docs.glue.ai/developers)
Improvements * The Apps Directory now defaults to the “All” tab when reopened. * Workspace names are now shown for all external groups. * Reduced unnecessary data fetching for custom emoji.
Fixes * Fixed a crash caused by pasting content in the message editor. * Fixed an issue where the Send button was inaccessible for long DMs on iOS. * Fixed a visual flash during onboarding after accepting an invite. * Fixed intermittent lint job failures in CI.
## What's New (Week of October 6th, 2025) ### 🧩 Discover and connect apps faster The new Apps section in your inbox makes it easy to find and install integrations and [MCP servers](/integrations/mcp-servers/mcp-server-best-practices) from an ever growing directory. Browse available apps and get set up in just a few clicks, so you can start taking actions without skipping a beat.
### **🧪 MCP Servers & Glue AI Rules are out of Labs** These features have officially graduated and now live in the main preferences menu.
Improvements * Suggest an app directly from the Apps Directory * Cleaned up the “New +” menu by removing the header and adjusting spacing for a sleeker dropdown. * Descriptions in link preview cards are now capped at two lines to keep things tidy. * On mobile, link previews now stretch to the full width of your screen with a visual polish to icons and layout. * Long MCP tools lists now include an expand/collapse option—see the first 20–25 tools, then click to reveal the rest.
Fixes * Fixed a bug that prevented thread links from automatically converting into mentions when pasted into messages. * Fixed avatar display in recipient chips so they now fill the space correctly without awkward gaps. * Fixed a macOS bug where window control buttons (close, minimize, maximize) would disappear under certain theme settings. * Fixed message reactions not updating in the feed until a page refresh. * Fixed a glitch where the AI chat view showed old content after deleting or sharing a conversation—it now refreshes to a clean slate. * Fixed link previews on mobile that weren’t taking up the full width of the screen. * Fixed tool suggestions that weren’t displaying workspace-level rules correctly. * Fixed tool suggestion icons to properly fade out when they’re temporarily disabled. * Fixed unclear error messaging during integration setup by providing better guidance on what’s wrong and how to fix it.
## What's New (Week of September 29th, 2025) ### ✅ **🧵 Close threads to stay focused** Keep your workspace clean and your priorities sharp. You can now close threads when the work’s done—no more sifting through old conversations. Just head to the thread action menu to close (or reopen) any thread. This is just the beginning—more powerful thread management tools are on the way. [Read more on our blog →](https://glue.ai/blog/closed-threads)
### 🧹 Clean up your feed in one click Your Feed just got easier to declutter when you need a fresh start. Use the new **"mark all seen"** button to clear out unread updates. It’s a quick way to tidy up and refocus on what’s next.
Improvements * The editor now auto‑switches to the Glue AI tab if pasted content mentions “Glue AI” * Improved mobile layout: the join requests view now has a top margin so you can navigate back * Updated Capacitor to version 7.4.2 * Preference screens now refetch available LLM models on open, ensuring new models appear
Fixes * Fixed bugs in Glue AI draft flow: empty draft headers no longer appear; drafts now persist when navigating away and back * Fixed code blocks losing formatting when pasting content * Fixed pasting of text links using double-brackets (`[TEXT][TEXT]`) — the hyperlink will now remain intact * Fixed GIFs displaying with black backgrounds in Safari (Imgix conversion issue) * Fixed layout shift in message list when removing text (Safari / webkit)
## What's New (Week of September 22nd, 2025) ### **🔮 Refreshed inbox experience** We’ve redesigned the Glue inbox to make it cleaner, modern, and easier to use. * **Stay in the zone:** Navigate all sections of Glue directly from your inbox, so you always stay in context. * **Focus on what matters:** Unread badges now appear only when you (or your group) are @mentioned directly. Other unread messages are bolded. Less clutter, more clarity! * Workspace settings menu shifted to the upper left side. 👉 Update your app to explore the refreshed inbox today. Have feedback on this change? We’d love to [hear from you](https://app.gluegroups.com/?action=contact_support)!
### 🎉 New pricing plan for startups! Our new **Startup plan** gives small teams the essentials to get started, plus ***5 seats free (forever)*** to kick things off. The former "standard" pricing plan is now known as the Business plan. Current customers retain their early adopter discounts! You can switch between plans from your [billing settings](https://app.gluegroups.com/?action=upgrade_workspace), or contact our team about upgrading to enterprise.
Improvements * Tweaked the **"Back to top"** and **unreads/unread mentions** buttons to better match design specs and improve visibility. * Adjusted the draft composer layout on **iOS** to ensure controls are always visible—even when the keyboard is closed.
Fixes * Fixed a bug where **DM autocomplete suggestions were getting cut off** unexpectedly. * Fixed an issue where **focus wasn't fully returned to the editor** after closing the image gallery modal. * Fixed a bug allowing users to **accidentally create duplicate threads** by navigating back to a sent draft.
## What's New (Week of September 15th, 2025)
Improvements * Breadcrumbs and back-navigation are now smarter across different screen sizes in two-pane layouts. * When Cmd+Clicking a thread from the inbox, your primary view stays put—no more losing your back button. * Updated hover and selected state color variables across the app for better theming support. * When creating a group from the inbox, you now stay in your current tab rather than being redirected. * Search and mention dropdowns now include consistent borders for clearer visual hierarchy. * New themes and color modes are now supported across both desktop and mobile. * Max-width has been standardized across all “attachment-like” components—links, files, threads, and tool calls—for better visual alignment. * OAuth apps can now be configured in the app builder, with support for adding redirect URIs, secrets, and client info.
Fixes * Fixed a bug where the “Approve Request” button didn’t visibly change after being clicked—users now get clear confirmation. * Resolved a Safari-only z-index issue where the AI model selector dropdown appeared behind the Super Sidebar. * Recipients are now hidden in the threads list view on narrow screens to reduce clutter. * Fixed an issue where the billing deep link (`action=upgrade_workspace`) was opening the user profile instead of the billing tab. * Addressed a display issue with join approvals during simultaneous mutations—approvals now render correctly even when done quickly. * Fixed a `Photoswipe` TypeError that could occur when opening media previews.
## What's New (Week of September 8th, 2025) ### **🆕 SCIM deprovisioning settings for admins** Workspace admins can now access a **“Configure Deprovisioning”** button from the Single Sign‑On settings. Use this to view and update SCIM deprovisioning status, set it up via the wizard, and ensure deprovisioned users are logged out automatically. You must have SSO via the enterprise plan to have access to this setting.
Improvements * Improved truncation logic so message previews don’t cut off in the middle of markdown links or formatting—“see more” expansions now respect complete markdown syntax. * Updated themes and UI color modes behind a feature flag—onboarding, sign‑in, and header now react to the new theme setting. * Enhanced Recent Media sidebar: GIFs now show a “Gif” label, display thumbnails, and animate on hover for easier discovery. * Removed redundant “New thread” buttons from DM & Group headers and mobile overflow menus—cleaner header UI now that the tabbed editor covers thread creation. * The Threads section in inbox sidebar is now collapsible, so you can hide/show that section as needed.
Fixes * Fixed a bug where group chat messages wouldn’t load fully when accessed via a thread that was created from a group chat message. Older messages now correctly load in those cases. * Fixed behavior where preview links in the native app were opening **twice**—now only one tab opens per link click. * Fixed group directory behavior: leaving a group no longer causes it to disappear from the directory list; membership status updates correctly without deleting the group entry. * Fixed unread badge logic: for non‑DMs, only mentions generate numerical badges. Threads with new messages without mentions no longer show number badges (just the “unread” indicator).
## What's New (Week of September 1st, 2025)
Improvements * Updated our chat components to use **stream‑chat‑react v13** (and stream‑chat v9). This brings better typing and performance improvements. * After sending a thread or finishing a Glue AI session, the editor now automatically resets to the **Reply** tab for a smoother conversational flow. * When you mention someone while creating a thread from a group chat (via the tabbed Reply editor), that mentioned user/group will now be added automatically to the thread recipients—no manual step needed. * App link previews have a new maximum width, preventing them from stretching too wide on large screens. * The interface now omits the `glue:` prefix when extracting mentions, for cleaner mention formatting.
Fixes * Fixed an issue where the “pinned message” close (X) icon showed even when you hadn’t hovered over it, creating confusion. * Fixed layout overflow in settings modal when a user has a very long email address. * Fixed notifications badge stuck on iPhones when notification permissions are disabled or lost; now badge is cleared in those cases. * Fixed ToolCall block buttons sometimes remaining disabled after confirming, especially when authentication is involved. * Addressed vulnerability in `linkifyjs < 4.3.2` (CVE‑2025‑8101). We’ve bumped to a safe version.
## What's New (Week of August 25th, 2025) ### **🔗 Fresh App Link Previews for Github and Linear** App link previews from [Github](/integrations/github#github-link-previews) and [Linear](/integrations/linear#setting-up-the-linear-integration) now support expand/collapse behavior, status indicators, and cleaner visuals to give you more context at a glance. Make sure to [add the apps to your workspace](/integrations/integrations-overview#add-app-to-workspace) and authorize your user account to see these enhanced previews!
### **🧭 Smarter onboarding for admins** New workspace admins can now tell us whether they’re a generalist or technical during onboarding. This helps us tailor educational content and guidance that fits your role—no extra fluff, just what you need.
Improvements * Updated team onboarding step: * Removed subhead text for a cleaner, simpler layout. * Team size selector now clearly marked as required. * Added a new role selector so admins can choose between *Generalist* and *Technical* tracks. * Created a reusable modal component for a more consistent experience to upgrade pricing plans across the app.
Fixes * Fixed a crash caused by `useState` being used outside its provider in the thread view. * Fixed a visual bug where the recipient input field in the thread info modal was displaying at the wrong width. * Fixed a `TypeError` related to dynamically importing modules that could interrupt the pre-login experience.
## What's New (Week of August 18th, 2025) ### 👉 One-click MCP Server Setup We now have an [MCP server directory](/integrations/mcp-servers/mcp-server-directory) that you can use to install the most popular MCP servers in Glue just by clicking the install button! Try it now by clicking the Install Linear link below.
### [Linear](https://linear.app/docs/mcp) Create, update, and track issues in Linear's project management platform. Install Linear ↗
Improvements * Tooltips for Notion MCP tools now support markdown and longer content for better readability. * Reduced frequency of thread name suggestions in the tabbed editor to avoid over-prompting. * Added a lint rule to block insecure `window.open()` usage—security is now baked in. * Emoji dropdown in thread modals now displays correctly on top of tabs. * MCP settings updated with cleaner CTAs and a new "Browse directory" link to our docs. * Updated external object rendering for cleaner link and audio displays. * Fixed layout issues in the “More unreads” UI overlapping with bulk edit actions.
Fixes * Fixed thread recipient pagination to support threads with more than 20 participants. * Fixed syntax error that occasionally broke rendering of message previews. * Fixed image thumbnails resizing oddly when clicked in certain dual-pane views. * Fixed thread attachment footers showing unnecessarily when no replies were present. * Fixed a stream chat error caused by Glue AI trying to load deleted thread channels.
## What's New (Week of August 11th, 2025)
Improvements * Editor tutorial flow now skips the “Reply” step and transitions directly to “Ask Glue AI anything.” * Cmd+Enter keyboard shortcut hint now appears contextually in the editor tutorial after you start typing. * Trust and security language added to the MCP OAuth connection modal for better transparency. * Mentions dropdown now appears correctly on mobile, no longer overflowing off screen. * Added link preview support in Storybook to showcase different variations. * Updated the Android app to meet the new minimum target version required by Google. * Glue now sends regular device heartbeats to keep presence status accurate. * Disabled source maps in production builds to improve code security.
Fixes * Fixed an issue where threads created from a DM didn’t include the other participant. * Fixed a text styling bug where send error messages appeared in bold instead of regular weight. * Fixed an issue where the number of sources listed in a magic thread didn’t match the number returned. * Fixed a bug that caused an error when trying to show browser notifications without a proper service worker. * Fixed tutorial banner lingering when switching editor modes; it now dismisses properly. * Fixed duplicate authentication calls during SSO sign-in via Identity Provider flow.
## What's New (August 7th, 2025) ### :e-mail: **Improved message composer** Seamlessly switch between drafting a message, kicking off a new thread, or launching a private GlueAI session—without ever leaving the composer. Enjoy a smoother, more intuitive editing experience that keeps your workflow focused and your conversations flowing.
### :key2: **SAML-based SSO** Enable enterprise-grade security and centralized user management with our new SAML-based single sign-on and JIT provisioning integration. Admins can connect any compatible identity provider—like Okta or Azure AD—to streamline authentication, automate user provisioning, and maintain full control over access. Enterprise customers, contact us to enable this feature for your workspace!
Improvements * Thread attachment layout shifts eliminated for a smoother viewing experience. * Enhanced onboarding tutorial for new workspaces and users
Fixes * Fixed AI tab model switching issue. * Fixed search hover state inconsistencies. * Fixed disabled state applying to non-selected items. * Fixed alignment of confirmation alert buttons.
## What's New (July 24th, 2025) ### :recycle: **Agentic AI with multi-step tool use** Supercharge your workflows with new agentic behavior in Glue AI to automate complex tasks seamlessly. Glue AI can now use multiple tools across several conversational turns: from fetching data and looking up users to updating records in external systems. No extra prompts or manual steps required, just make your request and Glue AI handles the rest.
### :closed\_lock\_with\_key: MCP client security fix We've added mitigations to some vulnerabilities in our MCP client implementation to further protect your data and interactions with Glue AI. In particular, we resolved an XSS vulnerability and strengthened input validation and output sanitization to prevent malicious script execution. We also investigated and confirmed that there was no exploitation of these vulnerabilities prior to our mitigations. No other action needed on your part.
Improvements * New tool call hover states and status labels make workflow actions clearer. * Narrow view UI improvements for both desktop and mobile. * Better handling of masonry blocks and fallback displays in messages.
Fixes * Fixed media items in shared group tabs opening in separate windows. * Fixed custom emoji size when it’s the only element in a message. * Fixed incorrect value being sent to feature flag checks.
## What's New (June 30th, 2025) ### **🔗 Share your MCP setups with the whole team** You can now share personal MCP servers—complete with custom AI rules—with your entire workspace. Once your server is dialed in, just hit [“Share with workspace”](/integrations/mcp-servers#id-5-share-the-mcp-server-configuration-server--rules-with-your-workspace-optional-but-recommended) to make it available to everyone. Your teammates can start using shared tools via Glue AI right away (they’ll just need to sign in to the service). It’s a game-changer for managing tasks together in tools like Linear and Asana.

Share your MCP Servers with the whole workspace!

### **✅ Glue is now an official Asana MCP client** You can now set up your [Asana MCP server](https://developers.asana.com/docs/using-asanas-mcp-server) in Glue! That means smoother, smarter workflows when using Glue AI to manage Asana tasks. Ask Glue AI to assign, update, and create tasks—all without leaving the thread. It’s the fastest way to keep projects moving without context-switching.
Improvements * Built a new tool call block component for cleaner display of AI actions in threads. * Added client-side validation to prevent users from connecting to unsupported localhost MCP servers—complete with a helpful error message and link to proxy setup instructions.
Fixes * Fixed an intermittent issue where pinning or unpinning a message didn’t update the UI correctly. * Fixed inconsistent button icon colors across the app.
## What's New (June 25th, 2025) ### **⁄ Slash commands for quick actions** Want to start a Zoom call right where you're messaging in Glue? Instead of digging through a menu, you can now use the `/` key or press the `/` icon at the bottom of the message editor to instantly bring up thread actions, and you can type what action you want to take to narrow down the list. This replaced the lightning bolt icon for thread actions. We will introduce more slash commands soon!
Improvements * Replaced the old lightning bolt icon in the message editor with a more intuitive slash command icon to match the new workflow. * Updated the thread action menu layout to match the new design for faster scanning and usability.
Fixes * Fixed an issue where source links in Glue AI responses weren’t displaying legibly in the super tab. * Fixed a bug that prevented scrolling back to the beginning of long threads in some cases. * Fixed an error that occurred when attempting to create a chat without listing a recipient. * Fixed an issue with recipient select dropdown colors for better visibility.
## What's New (June 18th, 2025)
Improvements * Sync editor option preferences for what the enter key does (i.e. start new line or send) across devices * Added support for passing the trigger event across all modal openings, improving focus management and accessibility. * Made `triggerEvent` a required parameter for modal openings, with fallback for auto-opened cases. * Form submissions (like workspace billing or message sending) now pass through `triggerEvent` for better consistency. * Improved the UX when leaving a group from the inbox — you’ll now stay on your current tab. * Unified the AI and regular editors behind the scenes to pave the way for upcoming tabbed editing features. * Updated the emoji picker for better accessibility and future flexibility. * Significantly reduced unnecessary re-renders in the app layout by isolating hooks and optimizing component structure. * Enabled code quality rules to avoid barrel file re-exports for clearer and safer imports.
Fixes * Fixed the "More unread" banner not appearing when unread threads are in a collapsed sidebar section. * Fixed certain "action" links not properly opening the Settings modal.
## What's New (June 12th, 2025) ### **🧠 Personalize Glue AI with AI Rules** You can now tailor Glue AI's behavior to match your unique communication style using AI Rules, available in the Labs section of your profile and preferences. These user-specific settings allow you to guide how Glue AI responds and suggests content within the platform.
* **Messaging Rules**: Define how Glue AI interacts with you directly, setting preferences for tone, formatting, language, and more. * **Suggestion Rules**: Customize how Glue AI proposes thread names, recipient suggestions, and group emojis, aligning with your team's conventions. * **MCP Server Rules**: Control Glue AI's interactions with each MCP Server individually, specifying default values, templates, and naming conventions for tasks and documents. To set up your AI Rules, navigate to your Preferences, open the Labs section, and select AI Rules. MCP Server Rules are managed from the Server itself. For more detailed guidance, visit our [AI Rules documentation](/profile-and-preferences/ai-rules). ### 🕵 AI Sessions — workshop with Glue AI in private, wow in public Now when you mention @Glue AI in the message editor, you will enter a private session that gives you a preview of Glue AI's response before you send it in the thread or chat with others. This gives you the flexibility to review and iterate on the results until you are ready to share broadly. Just type `@Glue AI` or hit the ✨ icon in any thread, group chat, or DM to start a session. You'll see a new editor, a response preview, and options to refine your prompt before publishing.

When you @ mention Glue AI in a message, the editor will enter a special private session mode

[Check out Evan's post about AI Rules and Sessions](https://www.linkedin.com/posts/evanaowen_were-releasing-two-new-ai-focused-features-activity-7340521909958098945-4Fbx/) to see how this combines with MCP to supercharge your work in Glue.
Improvements * We are officially implementing a paywall at the end of a trial or cancelation. “Upgrade now” and “Workspace limited” modals appear once per day. * Pasting code blocks automatically detects and tags the correct language—no extra steps needed. * OAuth server sign-ins now open in a new tab with clear “Sign in” CTAs and helper text after login. * Cleaner thread composer: Glue AI is no longer suggested by default. Suggestions now appear only after you've written enough context. * Sidebar rendering is more efficient—fewer unnecessary redraws when marking threads read/unread. * Updated keyboard handling in modals for consistent Escape key behavior. * Focus is now returned to the correct trigger element when modals are closed—across all modal types. * Focus states have been reviewed in modal views to ensure all elements are accessible and tabbable. * Video, audio, image galleries, and file attachments now have consistent hover and focus states for improved accessibility. * Improved file preview reliability by polling for Box IDs—if a file isn’t ready, you’ll now see a clear message.
Fixes * Fixed beeping sound from playing when using keyboard shortcuts. * Fixed a form nesting conflict that prevented replies in mobile search view. * Fixed a bug where quoting a message and tagging Glue AI could crash the composer or freeze the thread. * Fixed an error related to thread channels not being properly initialized. * Fixed a crash caused by missing workspace data during app load. * Fixed a confusing “Go to original message” behavior that opened a duplicate panel. * Fixed broken link previews for `.ai` domains like glue.ai. * Fixed a bug where non-AI threads could appear in the Glue AI tab. * Fixed missing focus return when closing some modals. * Fixed a vulnerability by resolving the `tar-fs` package issue. * Added extra error tracking for expired stream tokens to improve debugging and resilience.
## What's New (June 4th, 2025) ### 🧑‍🔬 **Experiment in Glue Labs — try cutting-edge features early** You’ll now see a new section in your user profile and preferences: [Glue Labs](https://glue.ai/labs). It’s your space to explore experimental AI and platform features while they're still in the works. We'll be iterating quickly here—so expect frequent updates and surprises. First up, MCP! ### 🤖 MCP is here for everyone — connect Glue AI to your tools [MCP](https://www.anthropic.com/news/model-context-protocol) (Model Context Protocol) is now live for all customers in the Labs section of Glue. You can connect MCP Servers for [supported third party apps](https://github.com/modelcontextprotocol/servers) to allow Glue AI to take your requests (like "turn the contents of this thread into an issue in Linear") and translate them into API-level commands. MCP is an emerging technology, but it is developing rapidly, and new companies are continuously adding support for MCP servers. Curious how it works? [Check out Evan's post about MCP](https://www.linkedin.com/posts/evanaowen_today-were-releasing-support-for-mcp-tools-activity-7336112787015835648-pKy_?utm_source=share\&utm_medium=member_desktop\&rcm=ACoAAAj_BPgBqkZ6O-FGxl4Gj3X6he2yixYlFNg) to dive deeper into why we’re so excited about it.
Improvements * Deep links for MacOS and iOS - Tapping a Glue link now opens directly in the app. * MCP Servers now support OAuth in addition to SSE. * Added support for keyboard accessibility across more menus and popovers (Create, Pinned Messages, and Thread Actions). * Focus management in modals has been tightened—modals now auto-focus on open for smoother keyboard use. * Added scroll behavior for overflowing Glue AI messages so the latest responses are always visible. * Refined AI feedback: positive reactions now auto-post a 👍 in the thread; negative feedback opens a feedback form. * Introduced character limits to rule text areas for better UX. * Enhanced accessibility in the Settings modal views: Profile, Labs, and Workspaces. * Groundwork for upcoming AI Sessions and MCP functionality that will be releasing later * Improved onboarding for mobile users by displaying tool details via tooltip. * Escape now resets editable headers inside modals instead of closing them—especially useful in the thread info modal. * Wide tables now scroll horizontally on mobile, so content no longer gets cut off. * Improved keyboard navigation and focus handling in the Group profile modal for smoother accessibility. * Cleaner attachment handling across editor and thread sessions for a more consistent file experience. * The HorizontalScrollingList component now supports spacing in flex containers, giving devs better layout control.
Fixes * Fixed a white flash during app launch that occurred before the theme loaded. * Fixed an issue where modals didn’t receive focus on open, requiring a manual click before ESC would work. * Fixed a bug where the suggested group recipient box sometimes lingered in the composer UI. * Fixed a visual bug where link attachments overflowed the message editor when focused. * Fixed a font flash (FOUC) when loading the mono font in certain views. * Fixed an issue where switching super tabs with an empty route memory would unexpectedly close the secondary pane. * Fixed a JavaScript alert popup that appeared in the Mac app due to a security issue in certain threads. * Fixed a bug that prevented single-backtick code blocks from rendering properly if the contents included a link. * Fixed an issue where code blocks wouldn't form properly when using Shift+Enter under “Enter to Send” settings. * Fixed an issue where the native app skipped anchor links during tab-based navigation. * Fixed an error caused by null `FilePreview` objects when updating the client.
## What's New (May 15th, 2025) ### 🧪 MCP available in Alpha — power up Glue AI with external tools Glue AI now supports [MCP (Model Context Protocol)](https://www.anthropic.com/news/model-context-protocol) as a client, available in alpha to select customers. MCP acts as a universal translator between AI and your external tools—so as the ecosystem grows, Glue AI gets smarter automatically.\ Want to try it? [Learn how to set up MCP servers with Glue](/integrations/mcp-servers) in our docs. ## What's New (May 9th, 2025) ### **🔐** Manage Workspace Access by Email Domain Admins can now manage access by **approved email domains**, with new options to let users auto-join or request access, right from your workspace settings.
Improvements * You can now request to join closed workspaces from the onboarding flow—complete with confirmation and approval emails. * Deep search results now display attachments. * Native apps now show a video thumbnail before playback begins.
Fixes * Fixed issue so inbox sidebar education shows for new users as intended. * Fixed mention dropdown on mobile so it auto-scrolls to the bottom. * Fixed an app crash on iPhone when typing "@" in the editor. * The app now terminates if a Web View crashes, improving stability.
## What's New (April 24th, 2025) ### ✨ Meet the new Glue AI composer We've revamped the Glue AI tab with a sleek new interface. See clear examples of what you can achieve with Glue AI and **get starter prompts to inspire your next query!**
### ⚡️ Be the first to try new LLM models We've added support for OpenAI’s GPT-4.1 and o4-mini models within the same week they were announced, as well as Google's Gemini 2.5 Pro Preview model. **GPT-4.1 isn’t available to consumers yet, so be one of the first to try it in Glue!** ### 📂 Analyze Google Drive links with our new integration Glue AI can now access Google Drive links sent in messages as if they were file attachments, so you can seamlessly analyze and summarize your GDrive content. No permission changes required! **Learn how to connect GDrive to your Glue account** [**here**](https://docs.glue.ai/integrations/google-drive)**.** *Stay tuned for more enhancements in this integration!*
### 🪟 Download the Windows desktop app You asked, we delivered. The Glue desktop app is **now available for Windows** — ready to download straight from the Microsoft Store. [**Download the Windows app now!**](https://apps.microsoft.com/detail/9p0bfrbfpcd9) ### 🔄 Reimport Slack channels with ease **Accidentally imported a Slack channel as a thread and want to make it a group?** No worries! You can now reimport Slack channels by simply re-uploading your file and selecting the channels you'd like to redo. This will overwrite the previous upload for those specific channels. Got more questions about Slack import? [Check out our documentation](https://docs.glue.ai/for-admins/slack-import#detailed-instructions-for-slack-import). ### 🛠️ Get Glue support answers faster **Glue AI now actively participates in support conversations with the Glue Team**, offering you a first response only if it thinks it has a relevant answer. Our team still checks every support thread, but this will help get you the answers you need even faster!
Improvements * \[ALPHA] Added configuration options to **MCP Settings**, giving admins more control. * Streamlined the **"Join Workspace"** step for new users during onboarding. * Profile tips now include **working hours**, helping teammates sync better. * Improved performance in **DMs directory** with virtualized user lists. * **Settings & Preferences** now support **grouped views** for better organization. * In multi-workspace threads, **apps now show their workspace**, reducing confusion. * Refreshed the **app header dropdowns** for a cleaner look and easier navigation. * Deleting the sole admin account now **automatically cancels the workspace subscription**. * Slack import UI now clearly **states the file size limit**, reducing upload frustration. * **Notification titles** now include group names for better context at a glance. * **Summarize thread** action is now hidden in group chats and DMs where it's not applicable. * You can now **add a workspace** directly from your settings and profile.
Fixes * Fixed an issue where pressing Enter in Quicksearch cleared the query when navigating to results. * Fixed lingering user tooltip when opening a secondary pane. * Fixed the AI composer button not disabling immediately when clicked. * Fixed the “See more” button not appearing when a code block starts at the truncation point. * Fixed a bug where deleting a workspace logged out the user and displayed a stuck modal. * Fixed workspace settings on mobile not navigating to the root view as expected. * Fixed that "Ask Glue AI" from the Help menu was still routing to old UI modal. * Fixed a bug where search could get stuck in a loading state. * Fixed the Groups tab media section only showing six items on initial load. * Fixed the mention selector being cut off in mobile view. * Fixed error notifications not being allowed for the application. * Fixed link previews missing titles when only a URL is shared. * Fixed external video attachments displaying a double footer.
*** ## What's New (March 20th, 2025) ### **🚀 Start Zoom or Google Meet Calls Directly from Glue** You can now start a Zoom or Google Meet video call from any Thread, Group, or DM in Glue. A meeting link will be sent automatically—no extra steps needed! If it's your first time, follow these setup instructions for [Zoom](/integrations/zoom) and [Google Meet](/integrations/google-meet).

If Zoom and Google Meet are added to your workspace, you can start a call from the lightning bolt icon

### **⚙️ Redesigned Menu for your Personal and Workspace Settings** We've revamped all your settings (for your user account and your workspace) to be in menu that's simpler to navigate. This new design also makes it easier for us to add more customization options in the future — more to come!

New menu allows you to access account profile and preferences and workspace settings in same view

Workspace settings menu

### **🔔 More Push Notification Controls** **Sounds:** You now have the option to [choose which notifications play a sound](/profile-and-preferences/push-notifications#notification-sounds). By default, sounds are on for DMs and @mentions, but you can now enable sounds for all notifications—or turn them off entirely. **Test Notifications:** You can now send yourself a test push notification to preview how it looks and sounds, and test to make sure you have them enabled.

In your preferences menu you can now control notification sounds and send a test notification!

If you do not see an option to send a test notification, that means you do not have them enabled on your device! [See how to set up notifications here](/profile-and-preferences/push-notifications#after-account-setup).
Improvements * **Credit card no longer required to start a trial!** We heard your feedback and removed the paywall before starting a trial. Users will still need to pay to continue using Glue at the end of the trial. * **Notifications:** Improvements to push notification reliability for the Mac desktop app. * **Restricted Groups:** Improved UI for composing or creating a reply thread to a restricted group, making it clear when you do not have messaging access.
Fixes * Fixed bug that allowed non-workspace users to create groups in the inbox. Groups are a workspace only feature. * Fixed bug so that clicking on a push notification correctly navigates to the target thread. * Fixed bug to ensure the "Welcome to Glue" thread is auto-selected on first sign-in.
*** ## What's New (February 27, 2025) ### Set Your Time Zone and Work Schedule for Smarter Collaboration Each person can now add their [time zone and weekly work schedule](/profile-and-preferences/sign-in-to-glue#time-zone-and-work-schedule) to their profiles. For colleagues working across time zones, it will make it much easier to see if someone is within their working hours before messaging.

Profile view of time zone and work schedule

### Clean Up Your Groups with Archiving Group and workspace admins can now [archive groups](#clean-up-your-groups-with-archiving) from the group's settings, keeping your workspace organized while preserving past discussions for easy search and reference.

Archived groups can still be accessed in the Group Directory

### Help Shape Glue AI with Better Feedback We've released an improved [Glue AI feedback form](/glue-ai/using-glue-ai#feedback-on-responses-from-glue-ai) that makes it easier to capture and submit relevant details, helping us make meaningful improvements faster.

Glue AI feedback form will open if you select the thumbs down icon on a response

*** ## Version 0.6.2 (February 21, 2025) ### **Cut the Noise: Turn Off Replies in Threads & Groups** Big news for large teams—you can now turn off replies for threads and groups to make them announcement-only. This isn’t a default setting as most threads and groups should be open for discussion, but it gives admins and thread starters flexibility to limit specific conversations sent to a large audience to help reduce noise. #### **Limit replies in a Thread** Thread starters and admins can now turn off replies in a thread. When enabled, only the thread starter, group admins, and workspace admins who are on the thread can respond. Keep key updates distraction-free and reduce the number of notifications for threads sent to a large audience. [Learn how to set this up →](https://docs.glue.ai/conversations/threads/thread-permissions#how-to-modify-thread-permissions)

User view of a thread with replies turned off

#### Limit replies in a Group Chat Group admins and workspace admins can now turn off replies in any group chat—including the [General group](https://docs.glue.ai/groups/group-settings/admin-settings-for-groups#turn-off-replies-in-the-general-group). Ideal for groups that need to be used for organization-wide updates without the notification overload. [Set it up in admin settings →](https://docs.glue.ai/groups/group-settings/admin-settings-for-groups#group-replies)

Admin view of a group with replies turned off

### Search your workspace and group members There's now a search bar in the Members section of your Workspace and Groups. This lets anyone easily search for who is in the workspace or group, and for admins, allows you to take actions to change a member's permission level or remove their access.
Fixes and Improvements * Fixed Reactions modal on mobile to scroll through who reacted * Fixed issue where guest users added to a thread were unable to create an account without creating a workspace * Fixed issue with signing up for a new account on mobile * Fixed bug with Starred section not showing the open group chat if you collapse the section * Hid Photoswipe full screen button on native apps since it already displays full screen * Refactored component for CSS modules * Upgraded firebase
*** ## Version 0.6.1 ( January 17, 2025) ### **What’s New** ### Manage push notifications directly from the Preferences menu Easily check if push notifications are enabled on your device by navigating to the Preferences menu in your app. If notifications aren't enabled, you can turn them on right from this view. This makes setting up push notifications straightforward, even if you initially opted out during sign-in. See more information about this feature [here](/profile-and-preferences/push-notifications#push-notifications-this-device).

Enable push notifications right from the preferences menu

### ✨ Glue AI glow ups ✨ - source icons and response information Glue AI sources now include icons to distinguish external links, threads, and uploaded content. There's also a handy new info button when you hover over a Glue AI response. This shows you the model used and a list of sources. Plus, you can provide feedback on response accuracy directly from this info card.

The response information includes the model, sources, and feedback buttons

Improvements * Sync unread count across devices when marking read * Improved device registration for push notifications to enable the new experience in the UI * Refresh UI for Thread info modal * Improved button icon sizing in the header * Improved layouts for all tabs across the app to be consistent * Renamed Glue AI conversations from "chat" to "thread"
Fixes * Fixed issue with DM Directory search not returning expected users * Fixed image resolution issue when zooming * Fixed duplicate subjects in thread notifications when a Group is added to a Thread * Fixed thread notifications for Groups added to a new Thread created from a message * Fixed text wrapping issue in thread notifications * Fixed broken “See more” button in Feed * Fixed validation error with adding a user to a draft Thread * Fixed issue with code blocks rendering in Thread attachment previews * Fixed issue with bulleted list formatting breaking when using Quote reply feature * Removed info and feedback buttons from Thread Reminder message from Glue AI * Fixed issue with Follow button text being cut off when Thread name is too long * Fixed education card reloading issue so they only show to brand new users * Fixed issue with updating the app if the app window size was too small
*** ## Version 0.6.0 (December 3, 2024) ### **What’s New** ### Glue AI gets its own tab! ✨ Glue AI is now even easier to find and use with its own dedicated space in Glue. We designed this to be a familiar, intuitive experience, similar to other LLMs like ChatGPT.
This new section is your personal scratch pad with Glue AI. It's completely private to you and makes it easy to see all your past Glue AI queries in one place. This change also moves private threads with Glue AI out of your thread inbox to keep your inbox focused on conversations that need your attention. **What you can do in the Glue AI tab** * See all your private threads with Glue AI in one place * Add people or groups to the Glue AI thread to collaborate and move it into your thread inbox * Change your LLM model * Search for Glue AI threads ### Thread Reminders ⏰ You can now set a reminder on a thread (clock icon ⏰) so it reappears in your inbox at a time that works for you. When you set a reminder, the thread is temporarily archived from your inbox until the date and time of your choosing. This gives you more control over how you manage your thread to-do's while keeping your inbox clean.

Setting a thread reminder from the inbox

### Create button in the sidebar ⊕ We've added a new "create" button (plus sign icon ⊕) that initiates your most important actions in Glue — starting a thread, asking Glue AI a question, creating a group, or sending a DM. It's prominently featured in the side bar so it's always where you are in Glue!

Create button can be found on the bottom left of the sidebar

Improvements * Workspace Settings menu easier to access from new company logo icon in app header * Improvements to new user experience: * Improved empty state messaging on Activity and DM sections of the app to indicate what will happen in these spaces once there are messages to view * Added welcome cards in the primary sections of the app without empty states (Inbox, Glue AI, Feed, Groups). The cards display to new users on the desktop and web app, and give context on how to use the app * Mention-style links for Glue AI sources * Improved group creation flow
Fixes * Fixed bulk action bar in inbox to stay pinned to the top when scrolling through thread list * Fixed missing emojis in reactions list on mobile * Fixed incorrect aspect ratio of uploaded HEIC images * Fixed missing attachments during initial DM creation * Fixed mobile support for onboarding flow * Fixed invalid group share link URL * Fixed a bug causing a frozen search input on older Mac OS versions * Fixed a bug causing improperly truncated thread subjects * Fixed a bug where Glue AI showed up twice in the inbox during onboarding
*** ## **Version 0.5.6 (October 15, 2024)** ### **What’s New** ### Pinned messages in Threads Anyone in a thread can now [pin a message](/conversations/threads#pinning-messages) to save it to the pinned section for everyone in the thread. The pin icon 📌 will appear at the top of the thread when there’s one or more pinned messages. Pinned messages will also be highlighted in the chat view.

Click the pin icon to see all pinned messges in a thread

Pinned messages are highlighted and show who pinned them

### Shared content tab on groups Groups now have a “Shared” tab that shows all content that’s been shared in the group - Docs, Media, and Links. View by recently shared or filter by type of content.
### Support for markdown tables We've added support for markdown tables in messages, so Glue AI can render tables of data in its responses.
Improvements * Fixed [Glue AI Feedback form](/glue-ai/using-glue-ai#feedback-on-responses-from-glue-ai) — the submission form is broken in 0.5.5 and has been restored * Display of photos from Hipstamatic on iOS * UI improvements in modals and threads detailed view
## Version 0.5.5 (August 27, 2024) * GlueAI is now better at understanding follow-up questions and can consider the context of the thread conversation when answering queries. * Redesigned search and auto-complete UI to be clearer and added a new search results view that allows users to filter by type of search result: conversations, groups, and people. * Improved semantic search results, with noticeable improvements to both the search bar and GlueAI responses. * Group chats will now be badged in the Inbox for new threads. This will make it easier to know what's happening in your various groups and give you the option to **Follow** any threads that you'd like to be notified about going forward. We've also updated the visual design of these threads in the group chat timeline to make them easier to read. * In-app Slack import tool allows admins to upload their exported Slack workspace directly into Glue and choose to import their old slack channels as either groups or threads. ## Version 0.5.4 (July 19, 2024) * Add top-level menu with help and support options * Fix minimum width of sidebar to allow resizing below 25% of full width * Fix broken privacy policy and terms of service links during sign up * Fix sluggish UI and idle CPU usage for some users
## Version 0.5.3 (July 8, 2024) * Show full group profile under Groups in the Inbox * Add info dialog to Glue AI response messages * Allow workspace admins to edit and delete threads * Allow admins to remind pending group invites * Automatically add mentioned groups to new threads * Better and safer workspace deletion flow * Fix bugs delaying inbox updates of new threads * Fix bug causing selection of wrong search result * Many other bug fixes # Beta features Get early access to pre-release functionality before it reaches general availability. Workspace admins can enable or disable beta access at any time. ### Overview The beta program gives your workspace early access to features that are actively being developed and refined. When beta features are enabled, your workspace receives access to all current beta-tier functionality as a single package — there are no per-feature toggles. Participation is optional and entirely reversible. Enabling or disabling beta features will not break your existing workspace configuration or affect your data. {% hint style="warning" %} **Beta features may change without notice.** Behavior, availability, and interfaces are subject to change at any time during the beta period. Features are not guaranteed to reach general availability in their current form. {% endhint %} *** ### Features Currently in Beta The following features are available to workspaces with beta features enabled. This list is updated alongside the release notes as features are added or promoted to GA. {% hint style="success" %} **NEW IN BETA** **Simplified Chats: Groups and DMs, now in one chat space** The sidebar now combines Groups and DMs into a unified Chat section.
**Why it matters:** This UX improvement makes messaging feel more streamlined, organized, and easier to navigate. {% endhint %} {% hint style="info" %} On rare occasions, major features may have their own individual flag rather than being included in the package — this will be noted clearly in the release notes. {% endhint %} ### Enabling Beta Features Only workspace admins can enable or disable the beta program. The setting is found in your workspace's general settings. 1. Navigate to **Workspace Settings → Advanced** 2. Toggle **Turn on beta features** to the on position 3. Confirm the prompt acknowledging that beta features may change without notice
Once enabled, beta features are available to all members of the workspace. Individual users cannot opt in or out independently — access is controlled at the workspace level. {% hint style="info" %} Changes to the beta toggle may take some time to propagate across your entire workspace. Members may not see the update simultaneously — ask your team to refresh if access appears inconsistent. {% endhint %} ### What to Expect #### Stability Beta features have cleared internal review but may still contain rough edges. They do not carry the same reliability guarantees as GA features. #### Changes without notice Because beta is a pre-release environment, we may update, replace, or remove features at any point. We won't always be able to give advance warning. If a feature is removed, your workspace will simply revert to GA behavior — no data or configuration will be lost. #### Documentation Beta features are documented in-product and noted in release notes with a `new in beta` tag. They do not receive full standalone documentation until they reach general availability. #### Support Beta features are supported on a best-effort basis. If you encounter a bug or unexpected behavior, please report it through the standard feedback channel — your reports directly influence whether a feature makes it to GA. {% hint style="success" %} Found a problem with a beta feature? Submit feedback directly in-product using the **Share feedback** option in the feature itself, or contact support with `[BETA]` in your subject line. {% endhint %} ### Release Notes When new beta features are available, they'll be noted in the release notes. There are no separate announcements — keep an eye on the release notes to stay current. Features in beta are tagged inline so they're easy to identify. Examples of how beta features appear in release notes: `New in Beta` AI-assisted table generation in documents — available to workspaces with beta features enabled `New in Beta` Inline comment threads on shared views — available to workspaces with beta features enabled `Now in GA` AI-assisted table generation — previously in beta; now available to all workspaces with full docs When a feature graduates from beta to GA, it becomes available to all workspaces automatically with full documentation and standard support. ### Opting Out You can turn off beta features at any time using the same toggle in workspace settings. When you opt out: * Beta features are immediately hidden from all workspace members * No data created or modified with beta features will be deleted * Workspace settings and permissions are unaffected * You can re-enable beta features at any time without consequence {% hint style="warning" %} If your team has been actively using a beta feature, disabling access may disrupt in-progress workflows. Communicate the change to your team before opting out. {% endhint %} ### FAQ **Can individual members opt into beta without admin action?** No. Beta access is controlled exclusively at the workspace level by workspace admins. Individual members cannot enable or disable beta independently. *** **Can I choose which beta features to enable?** Not currently. The toggle enables all current beta features as a package. Occasionally, large or high-impact features may have their own individual flag — this will be noted clearly in the release notes for that feature. *** **Will I lose data if a beta feature is removed?** No. Removing a feature from beta affects access to the UI or functionality, not the underlying data. Any content created via a beta feature is retained. *** **Is there a cost to participate in the beta program?** Beta features are included in your existing plan at no additional cost. *** **How will I know when a beta feature is promoted to GA?** Promotions are announced in the release notes with a **Now in GA** tag. Once promoted, the feature is available to all workspaces without any action needed, and full documentation is published. # Miscellaneous Various questions asked by our users
How do I change the send message shortcut? The default keyboard shortcut to send a message in Glue is Cmd+Enter, and Enter is the keyboard shortcut to add a new line in your message. However, for those who prefer to use Enter to send a message in Glue, you can change this under the **Preferences** menu.
Are there bots in Glue? Bots can be created by leveraging our Public API. See documentation for more information: [Glue Developers](https://docs.glue.ai/developers/)
How do I turn off email notifications? When you download our desktop or mobile app and enable push notifications, we will turn off email notifications for your account to avoid duplicate notifications. If you do not want to enable push notifications but also want to stop receiving email notifications about new messages, go to **Preferences** and change your push notification settings to **Nothing.**
{% hint style="info" %} Note that you will still receive notifications for any new requests or invitations. {% endhint %}
Why didn't I set a password? Glue does not use passwords. You can either log in using Google single sign on or with your email address and a one time log in code that we will send to your email. As long as your session stays active, you will not need to re-log in to Glue every time you use it.
Can I export my data from Glue? We currently do not have a self service way to export your message history from Glue. If you need to export your data, please [contact our support team](/get-started/help-and-support) in Glue or via email. Please specify: * Date range for the export * Data format (JSON or EML) * All workspace data or specific user We can provide message data in JSON or EML (email file) format. The EML export puts each message in a separate file grouped into folders by thread. The export will include *all* message data including DMs and private threads. If you want to scope by user we can export just threads visible to certain users. If you are canceling, we can provide the export until 30 days after you cancel.
Does Glue has an availability indicator to show when users are active or away? No, Glue does not currently have an online indicator, and this is intentional. We do have the ability to set your [time zone and work schedule](/profile-and-preferences/profile#time-zone-and-work-schedule) to let your team know your availability by day, and set a status to say if you're out of office or in a meeting. Please share feedback with us at if this is a blocker to using Glue and let us know more about your use case.
How can I make sure spell check is enabled on my desktop app? Right click on the message editor in Glue (wherever you are typing a message) and check under "spelling and grammar" to make sure the different spell check settings are enabled. They are not always on by default despite system settings.
Is Glue HIPAA or FINRA compliant? No, Glue is not currently certified for HIPAA or FINRA compliance. Please refer to our [security](/for-admins/security) and [privacy policy](https://glue.ai/privacy) information for the latest information on our security posture. If you are interested in using Glue but require a specific compliance certification to do so, please email [support@glue.ai](#how-do-i-change-the-send-message-shortcut) to let us know. We are always tracking these requests to determine which certifications to prioritize.
How can I add an emoji to a thread name? Adding emojis to thread names makes chatting in Glue more fun. Easily add emojis with the emoji shortcut — type a semi colon and then at least two letters and then an emoji picker will appear. You can also use your device's system shortcut for emojis or check if your keyboard has an emoji button.
**Some ideas for using emojis:** Add a checkmark to the beginning of a thread name when a project is done

Include a checkmark to show a thread is done

Is there a limit on the number of admins that can exist in a workspace? For our startup plan, yes there is a limit of one admin. If you want to add an additional admin, you will need to upgrade plans. For our business and enterprise plans, you can have unlimited admins. See our [pricing page](https://glue.ai/pricing) for the latest details.
How can I get links from the Windows app to open in Chrome instead of Edge? Install **MSEdgeRedirect** from Github to have links open in Chrome instead of Edge. 1️⃣ Set Chrome as your **default browser** (most important) This handles **most apps** automatically. 1. Open **Settings** → **Apps** → **Default apps** 2. Find **Google Chrome** 3. Click **Set default** 💡 If you want to be extra thorough: * Scroll down and make sure **.htm, .html, HTTP, HTTPS** are all set to Chrome. 2️⃣ If links *still* open in Edge (very common with Windows apps) Some Windows apps (like **Teams, Outlook, Slack, and system apps**) ignore your default browser and force Edge. Fix: Install **MSEdgeRedirect** (best workaround) This tool quietly intercepts Edge-only links and opens them in Chrome instead. 🔹 **What it does:** * Redirects `microsoft-edge://` links → Chrome * Works system-wide * Lightweight + safe (open source) 🔹 **How to use it:** 1. Download **MSEdgeRedirect** from GitHub 2. Run installer 3. Choose **Active Mode** 4. Select **Chrome** as your preferred browser
Can I see the full list of who has read my message? You can see a list of up to 5 people who have read your message, with a count of additional users who viewed it. If more than 5 people viewed your message, you cannot see the full list of names, just the count. This also is only tracked on recently sent messages, and you cannot get the history of who has seen past messages. Please give us feedback if you would like to see this working differently!
# Troubleshooting
Why isn't my desktop or mobile app working? Here are some quick ways to troubleshoot any app issues: * Please check to confirm that you are on the most recent OS on desktop and mobile. * Check for updates in the App Store or Play Store depending on your device. * Try force quitting the Glue app and restarting it.
My Inbox shows I have an unread message, but I can't find it It's possible you have an unread message in the "More" section of your thread inbox. If you sort your inbox by "Unread First," any unread messages will sort to the top and be visible to you. You can then read or mark the messages as read to clear the unread badge.

Try sorting your inbox by unread instead of recent

I didn't receive an email with my login code for Glue Please try the following steps if you've not received the login code: * **Check Spam/Junk Folder** * **Verify Email Address:** Make sure the email address used was spelled correctly and matches your Glue account and/or email that was invited to Glue * **Email Filtering:** Check if there are any filters or email rules that may be moving Glue emails to a folder other than the inbox. * **Resend Code:** Try logging in again after a few minutes in case there was a temporary issue. * **IT Restrictions:** If you are using a corporate email, there might be restrictions or firewall settings blocking emails from new senders. If your company does this, contact your IT department to whitelist Glue's email domain. * **Sign in with Google (if available):** If you have a Google account, you can bypass using the login code and use your Google account to authenticate. * **Contact our support team:** If you've tried all the troubleshooting steps, please reach out to our [support team](/get-started/help-and-support) and include the impacted email address and details about your login experience.
I am having an issue using the login code Please make sure you are using the code within a few minutes of receiving it, as the code expires. Otherwise you will need to try logging in again to get a new code. If you continue to have issues, please contact our [support team](/get-started/help-and-support#reach-us-via-email). If you reach out about a login issue, please specify where in the login process the issue is happening and what you see when you try to login.
I am having general issues logging in on the browser If you are noticing anything off while trying to log in to Glue on a browser (frozen pages, showing a paywall, etc), try clearing your browser's cache or deleting the site data for app.gluegroups.com from your browser. It's possible if you've visited the site in the past that it's storing old data from a prior visit. Clearing your cache should refresh your log in experience.
My notifications aren't working Please see the [notification troubleshooting documentation](/profile-and-preferences/push-notifications/notification-troubleshooting). If you try our troubleshooting and still have issues, you can [reach out for support](/get-started/help-and-support). Please specify what exactly isn't working in your message — is it not seeing notifications, not hearing the sound, or something else? The more detail the better! If you're able to send screenshots or screen recordings too that helps.
Are there character limits in Glue? There are some character limits specifically for individual messages and URLs. If you go past the character limit, you will receive an error and be unable to send the message. **Messages:** 12,000 characters **URLs:** 1,240 characters If you need to send a message that is more than 12,000 characters, you can break it into several smaller messages, or paste the copy it into a document and send it as a link or attachment. Glue AI will still be able to answer questions based on attached documents.
# API quickstart {% hint style="success" %} **The Glue API is in beta.** As the product evolves, we need to evolve the API as well. While we take breaking changes and deprecations seriously, the API is still in beta and we will need to make some of these changes. While we're in beta, the notice period may be as short as a few weeks. Glue's GraphQL API doesn't have versioning like many REST APIs. Instead the schema will evolve with certain things being marked with the `@deprecated` directive. This is usually accompanied by an addition to the schema intended to replace the deprecated functionality. Anything marked with `@deprecated` will be removed after some time. {% endhint %} Glue's public API is built using GraphQL and follows the [Relay](https://relay.dev/docs/) specification. It's the same API we use internally for developing our applications. If you are new to GraphQL, Apollo has [resources for beginners](https://blog.apollographql.com/the-basics-of-graphql-in-5-links-9e1dc4cac055). The official [GraphQL documentation](https://graphql.org/) is another good starting point. ## Endpoint Glue's GraphQL endpoint is: ```http https://api.gluegroups.com/public/graphql ``` It supports introspection so you can query the whole schema. ## Authentication The Glue API supports OAuth2 authentication. ### OAuth [OAuth2 authentication](/developers/authentication/oauth-2-0-authentication) is required. Once you complete the authentication flow and acquire an access token, pass it with the header `Authorization: Bearer ` ```sh curl \ -X POST \ -H "Content-Type: application/json" \ -H "Authorization: Bearer " \ --data '{ "query": "{ groups { nodes { id name } } }" }' \ https://api.gluegroups.com/public/graphql ``` ## Glue IDs Glue uses prefixed IDs to identify different types of resources. The prefix indicates the resource type, followed by a unique identifier. Common prefixes include: * `usr_` - Users * `thr_` - Threads * `grp_` - Groups * `wks_` - Workspaces * `msg_` - Messages For example: `usr_2a1b3c4d5e6f7g8h9i0j`, `thr_1b2c3d4e5f6g7h8i9j0k`, `grp_3c4d5e6f7g8h9i0j1k2l` These IDs can be used in GraphQL queries and mutations, and they work with the Relay `node` query to fetch any type of resource. ## Glue SDK The [Glue SDK](https://docs.glue.ai/developers/sdk) exposes the Glue GraphQL schema, and makes it easy to access models, or perform mutations. We recommend using it to interact with the GraphQL API. It is written in TypeScript, allowing all operations to be strongly typed. ## Getting Started Our GraphQL API is explorable and queryable via [Apollo Studio](https://studio.apollographql.com/public/glue-api/variant/current/home), no download or log in required. Click the Schema tab to browse the schema, and click the Explorer tab to run queries. {% embed url="" %} Once you have your client installed, you can start making queries (read) and mutations (write) to the API. {% hint style="info" %} We highly recommend using a GraphQL client to introspect and explore the schema if you are not using the Glue Client (SDK). {% endhint %} ### Queries & Mutations To get information about the authenticated user, you can use the `me` query: ```graphql query Me { me { id name } } ``` You can use the `groups` query to get a list of groups. ```graphql query Groups { groups { nodes { id name } totalCount } } ``` If you have a specific group ID, you can use a `node` query to query for the group. ```graphql query Group { node(id: "grp_2a1b3c4d5e6f7g8h9i0j") { ... on Group { id name } } } ``` The node query is part of the [Relay](https://relay.dev/docs/) specification. It can be used to query any object by its ID, and the response is polymorphic. The response type is tied directly to the type of ID passed in and you need to use fragments to specify which type you're querying. Here's a similar example where we query for a thread: ```graphql query Thread { node(id: "thr_1b2c3d4e5f6g7h8i9j0k") { ... on Thread { id subject } } } ``` And here's an example of querying a thread edge. The thread edge contains user specific information for the given thread ID. ```graphql query ThreadEdge { node(id: "thr_1b2c3d4e5f6g7h8i9j0k-usr_2a1b3c4d5e6f7g8h9i0j") { ... on ThreadEdge { id cursor recipientRole subscription node { id subject createdAt } } } } ``` This query returns the user's recipientRole and subscription with respect to the thread, as well as the thread subject and creation date. To learn more, take a look at these other pages: [Sending messages](/developers/graphql-api/messages_and_threading) [Understanding Glue thread types](/developers/graphql-api/understanding-glue-thread-types) [Pagination](/developers/graphql-api/pagination) To see everything that is available, check out our [GraphQL Explorer](https://studio.apollographql.com/public/glue-api/variant/current/home). This serves as a complete API reference and also provides an interface to help you construct and run queries. ## Support If you run into problems or have questions or suggestions, you can reach us in Glue using the "Contact Support" option under the Help menu in the top right corner or send us a note (). # Understanding Glue thread types In Glue, everything begins with a **Thread** — the core container for messages, participants, and activity.\ All conversations, whether a direct message, group chat, or topic-based discussion, are built on this same primitive. Every message belongs to a Thread, and its **ThreadType** defines the context. These types aren’t just technical details: they also shape how the conversation appears in the app. Different types have their own interfaces, optimized for their purpose, and may even appear in separate sections so users can tell them apart at a glance. This shared structure keeps things consistent for developers while giving the platform room to support different behaviors and evolve over time. ## Thread Types The `ThreadType` enum defines the different kinds of conversations supported in Glue. Each type controls how recipients are treated, how the thread behaves over time, and how it is displayed in the Glue interface. ```graphql enum ThreadType { thread # or named? chat } ``` {% hint style="info" %} `ThreadType` is **mutable by the system**. For example, a `thread` may evolve into a `chat` if the thread is converted into a group later. {% endhint %} *** ### `thread` A subject-based discussion designed to have a clear lifecycle. * For topic-oriented conversations that benefit from focus and closure. * Can be opened with a subject line and later closed when the discussion is complete. * Behaves like the “classic” threaded model
Sample Response Payload of a Standard Thread ```graphql { "data": { "thread": { "id": "thr_2hTJ4DGsxUAeEhKOyJ2PMePFL0c", "subject": "Project: Omega Initiative" "threadType": "thread", "recipients": { "edges": [ { "node": { "id": "usr_2rdDJjsN0n5HONuOusUoNcdu26X", "name": "Charlie Davis" } }, { "node": { "id": "grp_2tuREOmMXCuwA9GDHhJf9CaHaaa", "name": "Product Team", } }, { "node": { "id": "usr_2rdAe3Iuh2i92zy9Rq2xsWBQ59u", "name": "Diana Wilson" } } ] } } } } ```
*** ### `chat` A persistent chat for a single group or between two users ("DM"). * Always associated with either a single user (a DM) or a single group (a group chat) * Not tied to a specific subject * Recipients can't be added or removed, and the thread cannot be closed * Used for ongoing conversations between a set of recipients {% hint style="info" %} The recipient ID of a `chat` cannot change, it is either the single user or the group. While the recipient ID is locked, group membership remains dynamic. For example, if a user joins or leaves the group, the chat automatically reflects the updated membership. {% endhint %}
Sample Response Payload of a DM ```graphql { "data": { "thread": { "id": "thr_2PtTG7GFSgcgwfpeDOBGEQtyB24", "threadType": "chat", "recipients": { "edges": [ { "node": { "id": "usr_1h3c43PfmSQpPb0CXwRJUYs0ker", "name": "Alice Johnson" } }, { "node": { "id": "usr_2mHVPy5LlHYPs2zHcwm56M85J3h", "name": "Bob Smith" } } ] } } } } ```
Sample Response Payload of a Group Chat ```graphql { "data": { "thread": { "id": "thr_2rdAeYdtPPUOMQx5MgeeUkw9Yar", "threadType": "chat", "recipients": { "edges": [ { "node": { "id": "grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "name": "Engineering Team", "description": "Core engineering team discussions" } } ] } } } } ```
# Threads, Group Chats, and DMs In Glue, conversations occur inside threads, group chats or DMs. The functionality and appearance of these are very similar, and in the API, they are all represented by a `Thread`. To distinguish the 3 in the API, look at the `isPeristentChat` and `recipients` fields. ## DMs DMs will have `isPeristentChat: true` and the `recipients` field will contain exactly 2 users. ### GraphQL Response Sample ```graphql { "data": { "thread": { "id": "thr_2PtTG7GFSgcgwfpeDOBGEQtyB24", "isPeristentChat": true, "recipients": { "edges": [ { "node": { "id": "usr_1h3c43PfmSQpPb0CXwRJUYs0ker", "name": "Alice Johnson" } }, { "node": { "id": "usr_2mHVPy5LlHYPs2zHcwm56M85J3h", "name": "Bob Smith" } } ] } } } } ``` ### Looking Up a DM's Thread ID To find the thread ID for a DM with a specific user, you can query for a `UserEdge` and access its `persistentChatEdge`. The `UserEdge` represents the relationship between the current user and another user, and contains a `persistentChatEdge` field that points to the DM thread. **Note**: The `UserEdge` ID follows the pattern `{otherUserID}-{currentUserID}`. In this example, `usr_2mHVPy5LlHYPs2zHcwm56M85J3h-usr_1h3c43PfmSQpPb0CXwRJUYs0ker` represents the edge from Alice (current user) to Bob (other user). One of the 2 user IDs must be the user associated with the access token. You cannot access DMs involving other users. #### GraphQL Query Example ```graphql query GetDMThreadID($userID: ID!) { node(id: $id) { ... on UserEdge { id persistentChatEdge { node { id isPeristentChat recipients { edges { node { id name } } } } } } } } ``` #### Variables ```json { "id": "usr_2mHVPy5LlHYPs2zHcwm56M85J3h-usr_1h3c43PfmSQpPb0CXwRJUYs0ker" } ``` #### Response Sample ```json { "data": { "node": { "id": "usr_2mHVPy5LlHYPs2zHcwm56M85J3h-usr_1h3c43PfmSQpPb0CXwRJUYs0ker", "persistentChatEdge": { "node": { "id": "thr_2PtTG7GFSgcgwfpeDOBGEQtyB24", "isPeristentChat": true, "recipients": { "edges": [ { "node": { "id": "usr_1h3c43PfmSQpPb0CXwRJUYs0ker", "name": "Alice Johnson" } }, { "node": { "id": "usr_2mHVPy5LlHYPs2zHcwm56M85J3h", "name": "Bob Smith" } } ] } } } } } } ``` ## Group Chats Group Chats will have `isPeristentChat: true` and the `recipients` field will contain exactly 1 group. ### GraphQL Response Sample ```graphql { "data": { "thread": { "id": "thr_2rdAeYdtPPUOMQx5MgeeUkw9Yar", "isPeristentChat": true, "recipients": { "edges": [ { "node": { "id": "grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "name": "Engineering Team", "description": "Core engineering team discussions" } } ] } } } } ``` ## Threads Threads will have `isPeristentChat: false`. The `recipients` field could contain any combination of users and groups. ### GraphQL Response Sample ```graphql { "data": { "thread": { "id": "thr_2hTJ4DGsxUAeEhKOyJ2PMePFL0c", "isPeristentChat": false, "recipients": { "edges": [ { "node": { "id": "usr_2rdDJjsN0n5HONuOusUoNcdu26X", "name": "Charlie Davis" } }, { "node": { "id": "grp_2tuREOmMXCuwA9GDHhJf9CaHaaa", "name": "Product Team", } }, { "node": { "id": "usr_2rdAe3Iuh2i92zy9Rq2xsWBQ59u", "name": "Diana Wilson" } } ] } } } } ``` # Sending messages Sending a message is the core building block of any Glue integration. Whether you’re writing a bot that reports issues, an app that posts status updates, or just testing the API, the `sendMessage` mutation is the place to start. ## The `sendMessage` mutation The `sendMessage` mutation allows you to: * Send a message to an **existing thread** (using a `threadID`) * Create a **new thread** (by providing a thread object with configuration) Here is a basic example that sends a message to an existing thread with ID `thr_2hSyORgf8VqMLg0ADIvTi9oY6Nk`. ```graphql mutation SendMessage($input: SendMessageInput!) { sendMessage(input: $input) { thread { id subject } message { id text } } } ``` With variables, a payload looks like this: ```json { "input": { "threadID": "thr_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "message": { "text": "New bug reported!" } } } ``` ### First, find a Thread ID To send a message into an existing thread, you’ll need its ID. * Open the thread in the Glue app. * Select **Copy share link** from the menu. * Look in the URL: * Thread IDs begin with `thr_...` * Group IDs begin with `grp_...` Example URL: ``` https://app.gluegroups.com/thr_2hSyORgf8VqMLg0ADIvTi9oY6Nk?t=Chat ``` Here the thread ID is: ``` thr_2hSyORgf8VqMLg0ADIvTi9oY6Nk ``` Use this value as the `threadID` in your mutation input. ### SendMessage mutation input Here are the fields that you can send to the `sendMessage` mutation. These fields should be sent as GraphQL variables. | Field | Description | | ---------- | -------------------------------------------------------------------------------------------------------------------------------------- | | `threadID` | Optional. The ID of an existing thread to send to. If provided, the message will be sent to this thread. | | `thread` | Optional. Thread configuration for creating a new thread or updating an existing one. Must be provided if `threadID` is not specified. | | `message` | Required. The message to send. | #### ThreadInput fields | Field | Description | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `recipients` | Required. Array of recipient IDs (users, groups, or workspace). For a group, a message will be sent to the chat unless a `subject` is specified - in this case a thread will be created in the group instead. | | `subject` | If specified, a thread will be created instead of just sending a message. The `recipients` must be a group if a subject is specified. | | `threadBy` | Specify a value here to be able to update this thread after it is created. If you call the mutation again with the same value, it will update the existing thread instead of generating a new one. | | `replyToMessageID` | Optional. The ID of a message to reply to. | #### MessageInput fields | Field | Description | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `text` | Required. The text of the message to send. By default, this is treated as markdown. | | `attachments` | Optional. Array of file IDs to attach to the message. | | `uniqueBy` | Specify a value here to be able to update this message after it is created. If you call the mutation again with the same value, it will update the existing message instead of generating a new one. | | `quotedMessageID` | Optional. The ID of a message to quote in this message. | *** ## Example: Sending a message to an existing thread To send a message to an existing thread, provide a `threadID` and a `message` input with the message text. ```graphql mutation SendMessage($input: SendMessageInput!) { sendMessage(input: $input) { thread { id subject } message { id text } } } ``` ### Quick Test with curl Try a quick test, and `curl` right from your terminal: ```bash curl https://api.gluegroups.com/graphql \ -H "Authorization: Bearer $GLUE_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "query": "mutation SendMessage($input: SendMessageInput!) { sendMessage(input: $input) { thread { id subject } message { id text } } }", "variables": { "input": { "threadID": "thr_[YOUR ID HERE]", "message": { "text": "Hello World 👋" } } } }' ``` If you need help generating an access token, check out the [OAuth 2.0 Authentication guide](/developers/authentication/oauth-2-0-authentication). ## Example: Editing an Existing Message with `uniqueBy` Often, integrations need to *revise* a message — for example, updating the status of a bug report. To do this, include a `uniqueBy` tag. * Using the same `uniqueBy` updates the message. * Using a new `uniqueBy` creates a new message. To update the previously sent message, call the mutation again with the same `uniqueBy` value. ```json { "input": { "threadID": "thr_2hTJ4DGsxUAeEhKOyJ2PMePFL0c", "message": { "text": "New bug reported: [BUG154](https://example.com/BUG154) \n\nResolved by Jason", "uniqueBy": "BUG154" } } } ``` To generate a new message, simply provide a new `uniqueBy` value, or omit the `uniqueBy` value if you will not need to update the message. {% hint style="info" %} The `uniqueBy` can be any unique string, but it's a great way to map IDs of another service, such as bug, issue, project, or incident IDs. {% endhint %} ## Example: Creating threads To create a thread instead of just sending a message, provide a `thread` object with `recipients`, `subject`, and optionally a `threadBy` value. This will result in a thread created among the specified recipients and the app with the subject and starter message from `message.text`. ```graphql mutation SendMessage($input: SendMessageInput!) { sendMessage(input: $input) { thread { id subject } message { id text } } } ``` With variables: ```json { "input": { "thread": { "recipients": ["grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk"], "subject": "New crash in main.js", "threadBy": "BUG268" }, "message": { "text": "ReferenceError: reference to undefined property x", "uniqueBy": "BUG268-starter-message" } } } ``` When you specify an `threadBy` value in the thread, you can send follow up messages to the thread by calling the mutation again with the same `threadBy` value. This is perfect for linking threads to your issue tracking system or project management tool. In this case we're using the value `BUG268`. ```json { "input": { "thread": { "recipients": ["grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk"], "subject": "New crash in main.js", "threadBy": "BUG268" }, "message": { "text": "Jason, can you look into this?" } } } ``` Because we specified a `uniqueBy` value for the starter message, we can call the mutation again to update that starter message. Here we're using `"uniqueBy": "BUG268-starter-message"` which is the value we passed in the first mutation to start the thread. ```json { "input": { "thread": { "recipients": ["grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk"], "subject": "New crash in main.js", "threadBy": "BUG268" }, "message": { "text": "ReferenceError: reference to undefined property x \n\nAssigned to: Jason", "uniqueBy": "BUG268-starter-message" } } } ``` To create a different thread, send a new `threadBy` value or, if the `threadBy` value is omitted, a new thread will always be created. ```json { "input": { "thread": { "recipients": ["grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk"], "subject": "New crash in index.js", "threadBy": "BUG269" }, "message": { "text": "ReferenceError: reference to undefined property y", "uniqueBy": "BUG269-starter-message" } } } ``` ## Example: Attachments To send a message with attachments, you'll need to upload files first using the attachments API. See the [Attachments](/developers/graphql-api/attachments) documentation for detailed information on how to upload files. Once you have file IDs for the attachments, you can include them in your message: ```graphql mutation SendMessage($input: SendMessageInput!) { sendMessage(input: $input) { thread { id subject } message { id text attachments { ... on File { id name } } } } } ``` With variables: ```json { "input": { "threadID": "thr_2kbzWHxtQvfVEgwEdQduuxRTYG3", "message": { "text": "New report available!", "attachments": ["fil_2ymM4HRuRY4A7ed8OvVaUYxQ812"] } } } ``` You can attach up to 10 files per message. *** ## Summary You now know how to: * Find a thread ID * Send a basic message * Update a message with `uniqueBy` * Create new threads * Add attachments These are the core concepts you’ll use in any Glue integration. From here, you can start building bots, automation, and workflows that connect your systems directly into Glue conversations. # Message formatting Glue uses markdown to format messages. The following features are supported: * Text styling * Bold * Italics * Strikethrough * Links * User mentions * Inline code * Code blocks * Blockquotes * Paragraphs * Lists * Ordered * Unordered These features are described in detail below. ## **Text Styling** **Bold** To make text bold, wrap it with two asterisks (`**`) or two underscores (`__`). For example: ``` **This is bold text** __This is also bold text__ ``` Displays as:
**Italics** To italicize text, wrap it with one asterisk (`*`) or one underscore (`_`). For example: ``` *This is italic text* _This is also italic text_ ``` Displays as:
**Strikethrough** To strikethrough text, wrap it with two tildes (`~~`). For example: ``` ~~This text is strikethrough~~ ``` Displays as:
**Bold and Italics Combined** You can combine bold and italics for even more emphasis. For example: ``` ***This is bold and italic text*** ___This is also bold and italic text___ ``` Displays as:
## **Links** To create a hyperlink, use square brackets `[ ]` to set the text and parentheses `( )` to set the URL. For example: ``` [Glue](https://glue.ai) ``` Displays as:
**User Mentions** To mention a user in our chat app, use the following format: ``` [Jason Yonker](glue:usr_2PtTG7GFSgcgwfpeDOBGEQtyB24) ``` Displays as:
## **Inline Code** To include inline code, wrap your text with backticks (\`). For example: ``` Here is some inline code: `print("Hello, World!")` ``` Displays as:
## **Code Blocks** For longer code snippets, use triple backticks (\`\`\`) before and after your code block. You can also specify the language for syntax highlighting. For example: ```` ```python for i in range(10): print(i) ``` ```` Displays as:
## **Blockquotes** To create a blockquote, use the greater than (`>`) symbol followed by a space. For example: ``` > This is a blockquote. ``` Displays as:
## **Paragraphs** To create paragraphs, simply separate your text with one or more blank lines. For example: ``` This is the first paragraph. This is the second paragraph. ``` Displays as:
## **Lists** **Unordered Lists** To create an unordered list, use `-`, `*`, or `+` followed by a space. For example: ``` - Item 1 - Item 2 - Subitem 1 - Subitem 2 * Item 3 + Item 4 ``` Displays as:
**Ordered Lists** To create an ordered list, use numbers followed by a period and a space. For example: ``` 1. First item 2. Second item 1. Subitem 1 2. Subitem 2 3. Third item ``` Displays as:
# Attachments This document describes how to upload attachments using the Glue API. The process involves three main steps: 1. **Get an upload ticket** - Request a signed URL for uploading 2. **Upload the file** - Upload the file content to the signed URL 3. **Create a file object** - Register the uploaded file in the system 4. **Use the file** - Attach the file to messages or other objects ## Overview Files in Glue are uploaded directly to cloud storage using presigned URLs. The process ensures that only authorized users can upload files and that file integrity is maintained. ## API Endpoints ### 1. Get Upload Ticket **Mutation:** `uploadTicket` Request a signed URL for uploading a file. This endpoint validates file metadata and returns either an existing file (if the same content was already uploaded) or a new upload ticket. ```graphql mutation UploadTicket($input: UploadTicketInput!) { uploadTicket(input: $input) { ... on File { id name } ... on UploadTicket { id url headers { name value } formData { name value } } } } ``` **Input Parameters:** | Field | Type | Required | Description | | --------------- | -------------- | -------- | --------------------------------------------- | | `name` | String | Yes | The filename | | `contentLength` | String | Yes | File size in bytes | | `contentMD5` | String | Yes | Base64-encoded MD5 hash of the file content | | `contentType` | String | Yes | MIME type of the file | | `metadata` | UploadMetadata | No | Additional metadata (width/height for images) | **UploadMetadata:** ```graphql input UploadMetadata { width: Int height: Int } ``` **Response Types:** The `uploadTicket` mutation returns a union type `UploadTicketResponse` that can be either: #### Existing File Response If a file with the same MD5 hash already exists in the system, the API returns a complete `File` object. In this case there is no need to re-upload the file and the file ID can be used immediately as an attachment ID for sending a message. ```graphql { "uploadTicket": { "__typename": "File", "id": "fil_1h3c43PfmSQpPb0CXwRJUYs0ker", "name": "document.pdf", } } ``` #### New Upload Ticket Response If the file content is new, the API returns an `UploadTicket` object with upload instructions: ```graphql { "uploadTicket": { "__typename": "UploadTicket", "id": "upl_2k4m56QgnTRqQc1DXxSKVZt1ler", "url": "https://storage.glue.com/upload/presigned-url", "headers": [ { "name": "Content-Type", "value": "application/pdf" }, { "name": "x-amz-acl", "value": "private" } ], "formData": null } } ``` ### 2. Upload File Content Once you have an `UploadTicket`, upload the file content to the provided URL. If FormData is absent then you will nee to perform a PUT request to the specified URL. If FormData is present, then you will need to make a `multipart/form-data` POST request to the specified URL. In both cases you will need to supply the headers returned in the `UploadTicket`. **For PUT requests (no FormData):** ```javascript // Upload using PUT await fetch(uploadTicket.url, { method: "PUT", headers: uploadTicket.headers.reduce((acc, header) => { acc[header.name] = header.value; return acc; }, {}), body: fileBuffer, }); ``` **For POST requests (when formData is provided):** The `FormData` array may contain multiple entries that should be used to supply the form data for the POST. One entry will contain a value of `@file` which needs to be substituted for for the actual file content. The Content-Type will be `multipart/form-data` in order to accommodate the file data. Read more about multipart form data [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods/POST#multipart_form_submission). ```javascript // Upload using POST with form data const formData = new FormData(); uploadTicket.formData.forEach(({ name, value }) => { if (value === "@file") { formData.append(name, fileBuffer, { contentType: contentType, filename: filename, }); } else { formData.append(name, value); } }); await fetch(uploadTicket.url, { method: "POST", headers: uploadTicket.headers.reduce((acc, header) => { acc[header.name] = header.value; return acc; }, {}), body: formData, }); ``` ### 3. Create File Object After successful upload, create a file object in the system. **Mutation:** `createFile` ```graphql mutation CreateFile($input: CreateFileInput!) { createFile(input: $input) { id name } } ``` **Input Parameters:** | Field | Type | Required | Description | | ---------------- | ------ | -------- | ----------------------------- | | `uploadTicketID` | String | Yes | The ID from the upload ticket | ### File Metadata For images and videos, provide the following metadata which will be used to the client to show an appropriately size preview of the file before it is loaded. ```graphql type FileMetadata { width: Int # Image/video width in pixels height: Int # Image/video height in pixels blurHash: String # Blur hash for image previews } ``` **Key Points:** * **Always check `__typename`** - The response can be either `File` or `UploadTicket` * **Existing files are immediate** - No upload step needed, file is ready to use * **New files require upload** - Must upload content then call `createFile` ## Using Files in Messages Once you have a file object, you can attach it to messages: ```graphql mutation SendMessage($input: MessageInput!) { sendMessage(input: $input) { id text attachments { ... on File { id name url fileType contentType } } } } ``` **Message Input:** ```graphql input MessageInput { text: String! attachments: [ID!]! # Array of file IDs quotedMessageID: ID } ``` ## File Object Properties ```graphql type File implements Node { id: ID! # Unique file identifier fileType: FileType! # Type classification name: String! # Original filename contentLength: String! # File size in bytes contentMD5: String! # MD5 hash for integrity contentType: String! # MIME type metadata: FileMetadata # Additional metadata previewable: Boolean # Whether file can be previewed url: String! # Download URL } ``` # Pagination All list responses from queries return paginated results. We implement Relay style cursor-based pagination model with `first`/`after` and `last`/`before` pagination arguments. For example, this is how to query the last 10 threads available to you: ```graphql query Threads { threads(last: 10) { edges { node { id subject } cursor } pageInfo { hasNextPage endCursor } } } ``` To query the next 10, simply pass the value of `pageInfo.endCursor` as `after` parameter for the next request. You can do this as long as `pageInfo.hasNextPage` return true and you'll paginate through all the values in the collection. The first 50 results are returned by default without query arguments. In general, results are ordered by `createdAt` field. In some cases you can return results in a different order by specifying `order`: ```graphql query Threads { threads(order: lastMessage) { edges { node { id subject } cursor } } } ``` # Outbound webhooks Glue provides webhooks that let you receive HTTP push notifications whenever threads or messages are created or sent in your workspace. This allows you to build integrations that respond to changes in real time—for example, syncing data to external systems, triggering workflows, or sending notifications based on activity in Glue. You can use the Glue GraphQL schema explorer to look up the object types that are included in webhook payloads. Webhooks are configured at the **Workspace** level. You can choose to receive updates from all groups and threads within a workspace, or scope webhooks to a specific group, depending on your integration needs. To set up webhooks, go to your application’s settings in Glue, and create an [OAuth Application](/developers/authentication/oauth-2-0-authentication) to get started. Once configured, whenever a new workspace authorizes your application, Glue automatically creates a webhook for that workspace that posts to the URL you provide. ## Handling Webhook Requests ### Authentication and Security All webhook requests must be sent through HTTPS. Each request is also signed, so you know the request came from Glue. ### Retry Policy If the response to the webhook request is anything other than a 200, we will retry the request with the delays listed below. | Retry # | Delay | | ------- | ----- | | 1 | 10s | | 2 | 1m | | 3 | 10m | ## Webhook Payload The webhook HTTP payload will include information both in its HTTP headers and its request body. The format of the payload body reflects that of the corresponding GraphQL entity. You can explore the payload structure in our [GraphQL schema explorer](https://studio.apollographql.com/public/Linear-Webhooks/variant/current/schema/reference/objects). For a closer look at specific fields, you can also query them directly using the Linear API. The payload will be sent with the following HTTP headers: ```http Content-Type: application/json X-Glue-Event-Signature: {HMAC Signature} ``` **Example JavaScript to verify the signature** ```jsx const crypto = require("crypto"); function verifySignature(request, secret = "") { const hmac = crypto.createHmac("sha256", secret); hmac.update(request.body); const digest = hmac.digest("hex"); return digest === request.headers["X-Glue-Event-Signature"]; } ``` ### Event Body | Field | Type | Description | | ------------- | ------ | -------------------------------------- | | `type` | string | The Event Type being sent | | `workspaceID` | string | The Workspace ID the event belongs to. | | `event` | Event | The Event payload | ### Event Type | Name | Description | | --------------- | ---------------------------------------------------------------------------------------------------------------------- | | message.created | Occurs when a new message is sent in an existing thread. Contains the Message, and the Thread the Message was sent in. | | thread.created | Occurs when a new thread is created. Contains the Thread Created, and the first Message sent. | ## New Message or Thread Event For each message created in Glue, the corresponding event will have `message` content and `thread` content. The contents of each one are outlined below. For example: ```json { "event": { "message": { "id": "msg_2u0hEEQUZuDraFWJdoqLV2nF1gm", "quotedMessageID": "msg_2u0hEEQUZuDraFWJdoqLV2nF1gm", "text": "I don't know what happened, it worked on my local", "createdAt": "2025-03-07T23:48:06.079072Z", "updatedAt": "2025-03-07T23:54:33.050815Z", "url": "https://app.gluegroups.com/thr_2rKIaEdbiSuc869jTAGfMpSfaaa/usr_2vTvWPDt27hffx7BUNgIHQVLbbb-bd784d43-f620-46e7-bded-393522c68ccc", "user": { "avatarURL": null, "bio": "Software Developer", "id": "usr_2rdDJjsN0n5HONuOusUoNcdu26X", "name": "Donald Johnson", "workspaceIDs": ["wks_2rdAeYdtPPUOMQx5MgeeUkw9Yar"] } }, "thread": { "id": "thr_2rdAeT8weQGRzVVjJ0HDzYhI57q", "subject": "Prod is down", "createdAt": "2025-01-14T18:17:53.703017Z", "updatedAt": "2025-03-07T23:48:06.077649Z", "url": "https://app.gluegroups.com/thr_2rKIaEdbiSuc869jTAGfMpSfaaa", "isPersistentChat": false, "recipients": [ { "id": "grp_2tuREOmMXCuwA9GDHhJf9CaHaaa", "name": "🥸 Dev Team" }, { "address": "imadev@gluegroups.com", "id": "usr_2tuREOmMXCuwA9GDHhJf9CaHaaa", "name": "Ima Goodev" } ], "user": { "avatarURL": null, "bio": "Project Manager", "id": "usr_2rdAe3Iuh2i92zy9Rq2xsWBQ59u", "name": "Jane Smith", "workspaceIDs": ["wks_2rdAeYdtPPUOMQx5MgeeUkw9Yar"] } } }, "type": "message.created", "workspaceID": "wks_2rdAeYdtPPUOMQx5MgeeUkw9Yar" } ``` ### `message` content | Field | Type | Description | | --------------- | ------ | ---------------------------------------------------------- | | id | string | Unique Message UUID (ie `msg_2u0XJ6Urwwhd50uzfT1EVgJTwl1`) | | user | User | The User that sent the Message | | text | string | The Markdown text representing the Message sent. | | quotedMessageID | string | The Message UUID quoted by this Message | | url | string | Link to the message in the Glue App | | createdAt | string | The time the Message was created | | updatedAt | string | The time the Message was last updated | ### `thread` content | Field | Type | Description | | ---------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | id | string | Unique Thread UUID (ie `thr_2rdAeT8weQGRzVVjJ0HDzYhI57q`) | | user | User | The User that created the Thread | | subject | string | The subject of the Thread | | url | string | Link to the Thread in the Glue App | | recipients | \[]Recipient | Array of recipients of the Thread | | isPersistentChat | boolean | Indicates that this is the underlying thread for a group chat. In this case `recipients` will contain just one entry which is the group containing this group chat. | | createdAt | string | The time the Thread was created | | updatedAt | string | The time the Thread was last updated | ### `user` content | Field | Type | Description | | ------------ | --------- | ------------------------------------------------------- | | id | string | Unique User UUID (ie `usr_2mHVPy5LlHYPs2zHcwm56M85J3h`) | | name | string | The full name of the user | | avatarURL | string | A link to the User’s avatar image (optional) | | bio | string | User’s bio (optional) | | workspaceIDs | \[]string | Workspace IDs the User belongs to | ### `recipient` content | Field | Type | Description | | ------- | ------ | ------------------------------------------------------------------------------------------------------------------------ | | id | string | Unique User or Group UUID (ie `usr_2mHVPy5LlHYPs2zHcwm56M85J3h` for User or `grp_2rdAeYdtPPUOMQx5MgeeUkw9Yar` for Group) | | name | string | The full name of the User or the Group | | address | string | The User’s email address. (This will not be set for Groups) | All time fields are formatted as ISO8601 in UTC `1989-10-28T17:30:00.000Z` # OAuth 2.0 authentication Glue supports OAuth2 authentication, which is required in order to utilize the API. An OAuth2 authorization grant flow can be used to install an app to a workspace and to obtain an access token for a dedicated user associated with an app in the given workspace. For private apps, it's also possible for apps to be installed to a workspace from within the product. Regardless of installation method, once an app is installed to a workspace, an OAuth2 token request with client credentials can also be used to obtain an access token for a given app user by providing a workspace ID. This can eliminate the burden of maintaining a single set of access and refresh tokens for each workspace that an app is installed to. The app user tokens you obtain allow you to perform operations using a specific user associated with your app. In the future we plan to allow apps to obtain tokens for standard Glue users using an OAuth2 authorization grant flow. {% hint style="info" %} You must create a workspace for the purpose of managing the OAuth2 Application. {% endhint %} ## Create an OAuth2 application Create a new OAuth2 Application in Glue and configure the redirect callback URLs to your application. {% hint style="success" %} If you're having trouble finding Custom Apps, contact to ensure Custom OAuth Apps are enabled on your workspace! {% endhint %} ## Obtaining an access token via Client Credentials request Custom OAuth apps are automatically added to the workspace they're created in. You can obtain an access token for the app user for that workspace by making a client credentials request to `/oauth/token` with a `subject` field containing the ID of the workspace. ```http POST https:/api.gluegroups.com/oauth/token HTTP/1.1 ``` {% hint style="info" %} Pass parameters in body as [URL-encoded form submission](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST#url-encoded_form_submission), where the `Content-Type` header must be `application/x-www-form-urlencoded`. {% endhint %} | Parameter | Description | | ------------------------------- | ------------------------------------------------------------------------------------ | | `subject` | (required) The workspace to obtain token for (ie: `wks_32kbzWHxtQvfVEgwEdQduuxRTYG`) | | `redirect_uri` | (required) The registered redirect URL | | `client_id` | (required) Application's client ID | | `client_secret` | (required) Application's client secret | | `grant_type=client_credentials` | (required) | ### Response The token you obtain will contain the workspace app user's ID. There is no refresh token in this case as you can simply obtain another token by repeating the request so long as the application is still installed. ```json { "user_id": "usr_uxRTYG32kbzWHxtQvfVEgwEdQdu", "access_token": "00a21d8b0c4e2375114e49c067dfb81eb0d2076f48354714cd5df984d87b67cc", "token_type": "Bearer", "expires_in": 315705599 } ``` ## Make an API request Once you have obtained a valid access token, you can make a request to Glue's GraphQL API. You can initialize the [Glue Client](https://docs.glue.ai/developers/sdk) with the access token: ```typescript const client = new GlueClient({ accessToken: response.access_token }); const me = await client.me; ``` Or pass the token as an authorization header: `Authorization: Bearer ` ```sh curl https://api.gluegroups.com/public/graphql \ -X POST \ -H "Content-Type: application/json" \ -H 'Authorization: Bearer ' \ --data '{ "query": "{ me { id name } }" }' \ ``` # OAuth scopes This document describes the OAuth scopes available in the Glue API. Scopes define what permissions an application has when accessing the API on behalf of a user. ## Scope Naming Convention Scopes follow the pattern: `[admin.]:[.subset]` * `admin` - Optional prefix for admin-level permissions * `resource-path` - Path to the resource (e.g., `threads`, `workspaces`) * `action` - The action being performed (e.g., `read`, `write`) * `subset` - Optional subset of the resource (e.g., `messages`) ## Available Scopes ### Read Scopes #### `workspaces:read` **Permission Level:** Standard\ **Description:** View workspace information\ **Capabilities:** * Access workspace information like name, email domain, and avatarURL #### `threads:read` **Permission Level:** Standard\ **Description:** View thread information\ **Capabilities:** * View basic information about publicly accessible threads in a workspace * View basic information about threads the app is added to #### `groups:read` **Permission Level:** Standard\ **Description:** View group information\ **Capabilities:** * View basic information about public groups in your workspace * View basic information about groups that the app is added to ### Write Scopes #### `threads.messages:write` **Permission Level:** Standard\ **Description:** Send messages in threads, group chats and DMs\ **Capabilities:** * Send messages as the app user to threads the app has access to # Tutorial: Creating a hello world bot In this guide, we’ll walk through how to set up a simple "Hello World" bot: 1. Configure a Custom OAuth App and generate API credentials. 2. Finding a thread ID to target. 3. Sending your first message. 4. Updating or creating threads. 5. Adding attachments. *** ### 1. Configure a Custom OAuth App In Glue, navigate to the **Apps** section of the workspace settings. Locate **OAuth App** under the **Custom configuration** section, and click **Add**.
Enter a Name and a Description for your Custom App, and click **Create app**.
Once created, you'll be able to see your app's Client ID and Client Secret, which are your credentials to authenticate with the Glue API. Reference [OAuth 2.0 authentication](/developers/authentication/oauth-2-0-authentication) to use your Client ID and secret to generate your Access Tokens. *** ### Step 2. Using the SendMessage Mutation The core building block for integrations is the `sendMessage` mutation. This is how you post into an existing thread or create a new one. Here’s the GraphQL definition we'll use: ```graphql mutation SendMessage($input: SendMessageInput!) { sendMessage(input: $input) { thread { id subject } message { id text } } } ``` *** ### Step 3. Finding a Thread ID Every message needs a target thread, so let's find one. To see what Threads your App can see, we'll start by running this query: ```graphql query Query { threads { edges { node { id subject } } } } ``` Sample response: ```graphql { "data": { "threads": { "edges": [ { "node": { "id": "thr_1234lrtjf6gLyiQrscylCtqpxeG", "subject": "🍮 Fans of Flan Chat" } }, ] } } } ``` Let's store this thread ID for the next step. #### Not seeing any Threads? Let's check Group Membership The App you just created only has access to Groups it has been added to. By default, your newly created App is not part of any Group, and a Groups query will return no results. This is intentional! Your App shouldn't have access to DMs and private messages in closed groups, after all. You can verify this by specifying `GroupPreview` in your query to see the list of Groups you are not added to. **Adding Apps to Groups** In Glue, navigate to a group you want to grant access to your App. In the three dot menu in the top right corner, select **Apps** to open the Apps modal. The modal should looks something like this:
To check to see the Groups the App has been added to, specify Group in your query: ```graphql query Query { workspace { groups { edges { node { ... on Group { id name } } } } } } ``` You might see a response like this: ```graphql { "data": { "workspace": { "groups": { "edges": [ { "node": { "id": "grp_1234EYwyzBEbFbNeTAJCtFw460", "name": "🔍 Bots Welcome!" } }, { "node": { "id": "grp_1234lrnK07Tc6GNv5Npqto7qTqK", "name": "🍮 Fans of Flan" } } ] } } } } ``` To find a thread ID: * In the Glue app, navigate to the thread. * Open the menu and select **Copy share link**. * Paste the link — thread IDs start with `thr_...` and group IDs with `grp_...`. For example in the following URL: ``` https://app.gluegroups.com/thr_2hSyORgf8VqMLg0ADIvTi9oY6Nk?t=Chat ``` the thread ID is `thr_2hSyORgf8VqMLg0ADIvTi9oY6Nk`. *** ### Step 4. Send Your First Message Let’s post “Hello World!” into our thread. Replace the `threadID` with the one you copied above. ```json { "input": { "threadID": "thr_2hSyORgf8VqMLg0ADIvTi9oY6Nk", "message": { "text": "Hello World! 👋" } } } ``` Run this mutation, and your bot has spoken. 🎉 *** ### Step 5. Creating a New Thread If you know your recipients, you can also start a new thread and send the first message in one go. Just pass a `thread` object instead of a `threadID`. ```json { "input": { "thread": { "recipients": ["grp_2hSyORgf8VqMLg0ADIvTi9oY6Nk"], "subject": "Hello World Bot waves into the workspace!", "externalID": "HELLOBOT-INTRO-THREAD" }, "message": { "text": "Hello World, I'm the Hello Bot!", "externalID": "hellobot-starter-message" } } } ``` This creates a new thread in the target group and posts the message as the starter message. *** ### Wrap Up That’s it :tada: — you now know how to: * Post a simple “Hello World!” into a thread. * Create new threads on the fly. With these basics, you can build bots that announce deploys, report incidents, or connect Glue to your internal systems.