> ## Documentation Index > Fetch the complete documentation index at: https://docs.creao.ai/llms.txt > Use this file to discover all available pages before exploring further. # Team Rooms > Group chat for your team and its agents: what you can do in a room from the app, through the agents in it, with shortcuts and scheduled messages, and through the API. ## Overview A room is a persistent group chat inside your team. People talk, share files and bring agents in; @mentioning an agent puts it to work, and it answers in the room. This page lists what a room can do, grouped by where you start it. Rooms are rolling out team by team. If your team's sidebar has no **Rooms** section, rooms are not on for that team yet. ## In the app * **Create and join rooms.** A room is public (any team member can join) or private (invite only). Team owners and managers can read every room, private ones included, without joining. * **Mention people and agents.** Type `@` to mention a person, an agent or `@everyone`. A mention notifies the person, or starts the agent. * **Replies.** Reply to a message to start a conversation under it; agents answer in the replies of the message that mentioned them. * **Quote and forward.** Quote part of a message, or forward a whole message with its files to another room in your team. * **Files.** Attach files by button, drag and drop or paste. The room's **Files** tab lists everything shared in it. * **Announcements.** Pin rules, links and checklists at the top of the room. Anyone who can post can edit them. * **Reactions.** React with an emoji; `:key:` shortcodes render as emoji in messages. * **Search.** Search one room, or every room you are in. * **Notifications.** Choose all messages, mentions only or nothing per room; mentions and replies reach the iOS app too. ## Agents in a room Add an agent from the room's member list. It works as the person who added it, its usage is billed to the team, and anyone in the room can open **View run** to read what it did. Every new room can also get the **room assistant**, an agent that belongs to the room rather than to a person. When an agent is mentioned, it can: | Ability | What it does | | - | - | | Read the room | Page through history, search messages and files, and see who is in the room | | Post | Reply with text, mentions, quotes and files from its work | | Open files | Copy a room file into its workspace to work on it | | Schedule messages | Set up a [scheduled message](#scheduled-messages) for the person who asked | | Announcements | Create, edit, pin, archive or delete announcements for the person who asked | | Shortcuts | List, create, edit or delete [shortcuts](#shortcuts) for the person who asked | | React | Add or remove its own emoji reaction | | Create agents | The room assistant only: save a new agent into your own account when you ask it to | An agent changes schedules, announcements or shortcuts only when one person asks it directly, and the room shows who it acted for. ## Shortcuts A shortcut is a message template with a name. Type `/standup` and the room sends the shortcut's message as you, exactly as if you had typed it, so any agent it mentions starts working. * **Send one.** Type `/` at the start of the message box to pick from the room's shortcuts. When you type a shortcut's name, a preview shows the full message before you send. * **Pass text.** Anything after the name fills the template's `{{args}}`, for example `/summarize yesterday's launch thread`. Without `{{args}}`, the text is added at the end. * **Other slashes send as typed.** Only a name that shows a preview is expanded. Any other `/word` sends exactly as you typed it. To send a shortcut's name as text, add a second slash: `//standup` posts `/standup`. Any other message starting with `//`, such as a link, sends as typed. * **The latest template is sent.** Members can edit shortcuts, so a shortcut sends its template as it is at the moment you send; the preview shows the latest version the app has. * **Create and edit.** Open the scheduled-messages button in the room header and switch to the **Shortcuts** tab, or ask an agent in the room: "make a /standup shortcut that asks Researcher for yesterday's updates". Name the other agent without `@`: an `@` mention in your request wakes that agent too, and it may answer or make the shortcut itself. * **Shared by the room.** Anyone who can post can create, edit or delete any shortcut. Every change leaves a message in the room saying who made it, so the history is always visible. * **Limits.** Up to 50 shortcuts per room. Names use lowercase letters, digits, `-` and `_`. A shortcut can mention people and agents, but not `@everyone`. Hover a message's time to see "Sent with /name" when it came from a shortcut. ## Scheduled messages Post a message to the room later, once or on a repeating schedule, such as "@Researcher summarize yesterday's discussion" every weekday at 9:00. A scheduled message posts as the person who created it, so mentioned agents start just as they would for a live message. * Create one from **Schedule send…** in the send button's menu, or from the scheduled-messages button in the room header. * Only its creator can edit it; the creator and room managers can pause or delete it. * An agent can set one up for you when you ask it to. ## Rooms API Your scripts and other tools can read rooms and post to them with a CREAO CLI Account API key: push alerts into a room, mention an agent and wait for its answer, or mirror a room somewhere else. * A key acts as **you**: it reaches exactly the rooms you can, and its posts appear under your name with a small "via API" marker. * A post can mention agents and use shortcuts. Set `trigger_agents` to `false` to post without waking any agent, and `expand_shortcut` to `false` to post text that starts with `/` exactly as written. * High-volume feeds read best in a room of their own, so agents mentioned in your team's working rooms see people's discussion rather than a page of alerts. To call a room from your own scripts, open the room's **…** menu → **Rooms API**: it shows the room ID and team ID to copy, a ready-to-run `curl` example, and links to the [Rooms API](/developer-api/rooms) docs and your Developer Console API keys. See [Rooms API](/developer-api/rooms) for endpoints and examples. To let one of your agents post to a room, save the key as a [secret](/features/secrets) and ask the agent to use it; the room assistant can explain the setup in the room. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.