Work with the assistant inside a Space

Intermediate · ~10 min · Prerequisites: editor access to a Space

What you'll do

Bind the assistant to a specific Organizational Space so it searches that Space first, creates documents inside it, and respects the Space's permission model.

Bind to a space

Open the assistant from inside a Space — click Ask assistant in the Space sidebar panel — and the assistant binds automatically. The breadcrumb in the panel header confirms which Space it's scoped to.

You can also bind from a standalone thread: type @ in the composer, pick the Space from the list, and send your message. The thread stays bound to that Space for the rest of the conversation.

To unbind, start a new thread without mentioning a Space.

Space-first search

Once bound, the assistant searches the Space's documents before anything else. If it finds enough there, it answers from those results directly.

When the assistant pulls in content from outside the Space — for example, from your personal Your content — it discloses the source so you know where the answer came from. See Knowledge for how search scoping works.

Create & edit space docs

Ask the assistant to create a document and it lands inside the Space, in the current folder if you're browsing one:

"Draft a one-page project brief for the mobile redesign."

The document appears in the Space's explorer. Editor-level access (or higher) is required — ask the assistant to create or edit and it will tell you if your permissions don't allow it.

To edit an existing Space doc, open it, click Ask assistant, and work in the bound coop panel. Changes land for all Space members in real time.

Permissions

The assistant enforces the Space's access model:

• Editor and above — can create, edit, and move documents.
• Viewer — can read and search Space content, but the assistant will decline write requests.

You cannot grant the assistant permissions you don't have yourself. If a Space is restricted, the assistant sees only what you see.

Try this next