> 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/teams-and-admins/use-fyxer-as-a-team.md).

# Use Fyxer as a team

Give everyone the full story, and hand off work without the back-and-forth.

{% hint style="success" %}

* [How Fyxer helps your team](#what-changes-for-your-team)
* [Spaces: shared context everyone can see](#spaces-shared-context-everyone-can-ask)
* [Ask Fyxer where your team already talks](#ask-fyxer-where-your-team-already-talks)
* [Flows that keep the whole team posted](#flows-that-keep-the-whole-team-posted)
* [See it in action](#see-it-in-action)
* [Hand over an account](#hand-over-an-account)
* [What stays private](#what-stays-private)
* [Get your team started](#get-your-team-started)
* [More ways Fyxer helps teams](#more-ways-fyxer-helps-teams)
  {% endhint %}

On most teams, knowledge is spread across inboxes and meetings, so no one has the full picture.

When your team uses Fyxer together, Fyxer helps close those gaps, so less depends on who was in which meeting or on which thread.

### How Fyxer helps your team <a href="#what-changes-for-your-team" id="what-changes-for-your-team"></a>

* **Shared context:** anyone can get up to speed on an account without asking around
* **Smooth handovers:** the history moves with the account, so clients don’t repeat themselves
* **Updates that arrive on their own:** regular team updates turn up without anyone putting them together
* **One way of working:** shared tone, team scheduling, and org-wide settings keep everyone consistent

***

### Spaces: shared context everyone can see <a href="#spaces-shared-context-everyone-can-ask" id="spaces-shared-context-everyone-can-ask"></a>

A Space brings together everything about one client, deal, or project. Emails and meetings with that company are added as they happen, so the Space is always up-to-date.

* **One Space per account.** Create a Space for each client, deal, or project your team shares
* **The right people, automatically.** Turn on automatic invites and anyone who emails or meets with that company is added, as a Viewer or a Contributor
* **Ask it anything.** Anyone in the Space can ask, "What have we promised \[company name], and who owns each item?"
* **Shared action items.** Action items are pulled in from meetings and emails. Reassign them, set deadlines, and mark them done

Learn more: [**Share context with Spaces.**](https://docs.fyxer.com/using-fyxer/share-context-with-spaces.md)

***

### Ask Fyxer where your team already talks <a href="#ask-fyxer-where-your-team-already-talks" id="ask-fyxer-where-your-team-already-talks"></a>

Mention @Fyxer in a Slack or Microsoft Teams thread to pull in the information everyone needs, without anyone having to go off and search for it.

> In #acme-account: @Fyxer check the Acme Space: when did we last send Acme the revised pricing, and did they reply?

Fyxer pulls the answer from the Space, so it doesn’t matter who sent the pricing or who was on the call.

***

### Flows that keep the whole team posted <a href="#flows-that-keep-the-whole-team-posted" id="flows-that-keep-the-whole-team-posted"></a>

Flows are pre-built automations that handle yours and your teams repeat tasks.

A Flow can post to Slack or Microsoft Teams, so everyone gets the same update at the same time. For example:

* An action-item roundup after each client call, posted to the account channel
* A Friday wrap-up of what moved this week, posted to the team channel

Learn more: [**Run tasks with Flows.**](https://docs.fyxer.com/using-fyxer/run-tasks-with-flows.md)

***

### See it in action <a href="#see-it-in-action" id="see-it-in-action"></a>

Mike's team of four looks after 30 clients between them. On Friday Mike is out, and Acme emails asking whether the new start date still works.

Sophia picks it up. She's never been on an Acme call, so she asks the Acme Space:

> What's the latest with Acme, and what have we promised them about the start date?

She gets the answer from Mike's call notes and the email thread, both already in the Space. She follows up by asking for a draft reply she can review and send.

***

### Hand over an account

When an account moves to someone new, cc them on the handover email. If automatic invites are on, they're added to the Space and will see the full history straight away. They can then ask the Space for a handover brief.

Step by step: [**Hand over an account workflow**.](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-use-case/hand-over-an-account)

***

### What stays private <a href="#what-stays-private" id="what-stays-private"></a>

* Only members of a Space can see what's in it. Colleagues outside it can see its name, company domain, logo, owner, and members on the Discover tab, unless the Space is Private
* You can hide any of your own emails or meetings from a Space with **Hide from others**
* Contributor emails and meetings are only shared into a Space once they accept the invite

***

### Get your team started <a href="#get-your-team-started" id="get-your-team-started"></a>

1. Pick one account the whole team works on, create a Space for it, and turn on automatic invites
2. Tell your team to connect Fyxer to Slack or Microsoft Teams in [Dashboard](https://app.fyxer.com/) → Settings → Integrations
3. Set up one Flow that posts to a team channel. Go to [Dashboard](https://app.fyxer.com/) → Flows → **Create Flow**
4. Share some example questions that people can ask Fyxer in a Space, Slack or Teams:

   \
   **In a Space:**

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

   **With @Fyxer in Slack or Teams:**

   * “@Fyxer check the \[client] Space: what’s still outstanding?”
   * “@Fyxer what do I need to know before my call with \[client]?”

For help bringing everyone on board, see [**Roll out Fyxer: a manager's guide**.](https://docs.fyxer.com/teams-and-admins/roll-out-fyxer-a-managers-guide)

***

### More ways Fyxer helps teams

#### One voice across your team

Share tone of voice guidelines, templates, and key messaging with your whole organization, so every draft sounds on-brand. Go to [Dashboard](https://app.fyxer.com) → Settings → Drafts → Files.

Learn more: [**Work with drafts.**](https://docs.fyxer.com/using-fyxer/work-with-drafts.md)

#### Book meetings as a team

Share one booking link that shows your team’s availability, or spread inbound bookings across the team.

Learn more: [**Team scheduling and resources.**](https://docs.fyxer.com/teams-and-admins/team-scheduling-and-resources.md)

#### Organization-wide settings

Admins can set how Fyxer works across your whole organization, in one place.

Learn more: [**Admin controls and settings.**](https://docs.fyxer.com/teams-and-admins/admin-controls-and-settings.md)

***

### Next up <a href="#next-up" id="next-up"></a>

Get your team up and running in minutes.

* Next: [**Onboard your team**](https://docs.fyxer.com/teams-and-admins/onboard-your-team.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/teams-and-admins/use-fyxer-as-a-team.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.
