Spaces overview
A Space is where your team and Hops work together. Learn what a Space is and how to create one.
A Space is a shared workspace for a team and Hops. Everything relevant to a project or workflow lives here: conversations, docs, the Space Context document, and artifacts.
When your team works in a Space, Hops builds up shared context from it. The next question in that Space already has the background.

How Spaces work
One Space, one shared context. Everything in a Space — decisions, drafts, threads, docs — contributes to the shared context Hops draws from.
People and Hops work side by side. Tag @Hops in a thread. If your workspace has installed skills, Hops uses the right skill automatically when the request matches, and shows attribution like Hops · Pipeline watch on the response.
Spaces are scoped. Hops working in one Space doesn't automatically carry that context into another. You control what each Space contains and who can see it.
Set up the Space Context document early. It's the single fastest way to make Hops sharper in the Space — one brief Hops reads before responding.
Space visibility
Every Space is either public or private inside your workspace. You pick when you create it and can change it later.
| Visibility | Who can see it | Good for |
|---|---|---|
| Public | Everyone in your workspace can find and join | Team channels, company-wide projects |
| Private | Only invited members and Hops | Client work, confidential launches, exec-only rooms |
Private Spaces are hidden from search for people who aren't invited. Hops scoped to a private Space only draws context from it.

Search puts exact matches first, then favours things you opened, created or are named in, and newer items.
Cmd/Ctrl-click or middle-click a sidebar section, Hops thread or automation to open it in a new tab.
Space shortcuts
Space managers can add one-click shortcuts to a Space: open a document or app, start a table entry, create a document, ask Hops with a prompt ready, or open a web link. Anyone can pin their favourite shortcuts to Home.
Work with Hops in a thread
Every Space has Hops by default. Tag @Hops in a thread and it responds from the Space's shared context. If a matching skill is installed, Hops uses it automatically and attributes the response like Hops · Pipeline watch.
@Hops pull the latest competitor pricing for Q3
@Hops turn those findings into three subject-line options
@Hops draft a follow-up to yesterday's demo using the new positioningReplies land in the same thread so the whole team sees the context.
Create a Space

Click the + button
At the bottom of the left sidebar, click + and select Space.
Name your Space
In Icon & Name, pick an icon and give the Space a clear, specific name. Optionally add a Topic.
Good examples:
Product launch Q3,Acme Corp account,Marketing team.Choose visibility and continue
Select Public (anyone in the account) or Private (by invitation only), then click Continue.
Your Space is ready. Start a thread, set up the Space Context document, or tag @Hops to get to work.
Extend Hops with skills
Every Space has @Hops by default. To give Hops role-specific behavior — a Legal reviewer, a Researcher, an SDR — install a skill. There is only one agent: Hops.
Open Skills
From the left sidebar, open Home, then choose Skills in the sidebar.
Install what the Space needs
Pick a skill for yourself, or (as an admin) install it for the whole workspace so every Space's Hops can use it.
Tag Hops in chat
Tag
@Hopsin the Space. When the request matches an installed skill, Hops uses it and shows attribution on the response.
Keep a small, focused set of skills installed. Fewer, sharper skills give better results than a long overlapping list.
See Hops overview, Skills, and Build a skill for more.
When to create a new Space
Create a Space for a distinct project, team, or ongoing workflow:
| Type | Good for |
|---|---|
| Project | A specific initiative with a start and end |
| Team channel | An ongoing team with recurring workflows |
| Client account | All context for one external relationship |
| Process | A repeating workflow (hiring, onboarding, reporting) |
Keep one Space per topic. Mixing unrelated projects dilutes the context and makes Hops less accurate.
What's inside a Space
Docs, files, and tables created in a Space also show up in the global Artifacts sections in the left sidebar (Docs & Tables and Files).
Common Space setups
Not sure how to structure your first few Spaces? Start from a proven pattern.
See Teams & Use cases for every team's playbook.