> For the complete documentation index, see [llms.txt](https://docs.fyxer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyxer.com/using-fyxer/share-context-with-spaces.md).

# Share context with Spaces

Give every client, deal, or project one shared home.

{% hint style="success" %}

* [What's in a Space](#whats-in-a-space)
* [Create a Space](#create-a-space)
* [Who gets added](#who-gets-added)
* [Ask your Space](#ask-your-space)
* [Control what's shared](#control-whats-shared)
* [Workflows to try](#workflows-to-try)
  {% endhint %}

The story of a client is usually spread across several inboxes and calendars. A Space brings it together. Emails and meetings with that company are added as they happen, so anyone on the account can see what was said, what was agreed, and who owes the next step.

{% hint style="info" %}
You might not see Spaces yet. We're rolling this feature out gradually as we test and refine it, so availability will vary. We'll keep this page updated as things evolve.
{% endhint %}

### What’s in a Space

A Space is built around a client, a company, or a project. It shows:

* A summary of the relationship
* A timeline of emails and meetings, linking back to the originals
* Action items, with owners and deadlines
* Notes
* Who’s involved, on your side and theirs

Learn more: [**Get started with Fyxer Spaces.**](https://support.fyxer.com/article/get-started-with-fyxer-spaces)

***

### Create a Space

1. Go to [Dashboard](https://app.fyxer.com) → Spaces and select **Create new**
2. Name your Space and choose what should be added
3. Select **Create Space**

Emails and meetings start flowing in straight away.

You might also find you’ve already been added to some Spaces as a Viewer or invited as a Contributor.

***

### Who gets added

When you create a Space, you choose how people join. Either they’re added only when you invite them, or automatically when they email or meet with that company.

There are two roles:

* **Viewers** can see everything in the Space. They’re added without needing to accept an invite
* **Contributors** can see the Space and add to it. Their own emails and meetings with that company are only shared once they accept the invite

Automatic invites keep a Space complete. If a client contacts someone new on your team, that person is added, and the history is there for them.

To change how people join, open the Space and select **Invite**.

***

### Ask your Space

Ask your Space a question, and Fyxer answers from everything in it. Try:

* “What have we promised this client, and who owns each item?”
* “What’s changed with this account this week?”
* “Is there anything they’ve asked for that nobody has replied to?”

You can also reassign action items, set deadlines, mark them done, and add new ones.

***

### Control what’s shared

* **Only members can see a Space.** The Space owner can invite people, remove them, and approve requests to join
* **You choose what’s included.** To keep an email or meeting out of a Space, open it in the timeline and select **Hide from others**
* **Your inbox stays yours.** Only emails and meetings relating to the Space get shared, and only with its members

***

### Workflows to try

* [**Know where every account stands.**](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/know-where-every-account-stands) Keep everyone in the loop on every account
* [**Hand over an account.**](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/hand-over-an-account) Pass on a client, with the history

***

### Next up

Learn which tools integrate with Fyxer.

* Next: [**Integrations**](/using-fyxer/integrations.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fyxer.com/using-fyxer/share-context-with-spaces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.