> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flipsidecrypto.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams

> Collaborate with colleagues using shared workspaces in FlipsideAI

Teams let you collaborate on blockchain analyses with colleagues, sharing chats, insights, and
workflows in private workspaces.

## What are Teams?

Teams are shared workspaces where you can:

* **Share chats privately** with team members
* **Collaborate on analyses** without making them public
* **Maintain context** across multiple team members working on the same project
* **Organize work** by project, client, or research area

Unlike public sharing, Team chats stay private to your organization.

## Setting up a Team

<Steps>
  <Step title="Create a Team">
    1. Click the **Teams** panel in the bottom-left of FlipsideAI
    2. Select **Create new team**
    3. Name your team (e.g., "Research Team," "Client Analytics," "DeFi Research")
  </Step>

  <Step title="Invite members">
    1. Open your Team settings 2. Click **Invite members** 3. Enter email addresses for team members
    2. Set permissions (view-only or full access)
  </Step>

  <Step title="Start collaborating">
    * Any chat created while a Team is selected will be accessible to all team members
    * Team members can view, fork, or continue conversations
  </Step>
</Steps>

## Using Teams effectively

### Organize by project

Create separate Teams for different workstreams:

* **Client work**: Keep client analyses separate and confidential
* **Research initiatives**: Organize long-term research projects
* **Internal ops**: Track protocol monitoring or risk assessments

### Share context, not just results

Teams preserve the full conversation history, so teammates can:

* See how you arrived at conclusions
* Understand your methodology
* Build on your work without starting from scratch

### Use Teams with Rules

Establish team-wide [Rules](/flipsideai/rules) to ensure consistent output:

```text theme={null}
Example: Create a shared Rule for your team's reporting style:
- Charts use company brand colors
- All analyses include TVL, user count, and transaction volume
- Summaries follow the "Problem → Data → Insight → Action" framework
```

While Rules are personal, you can share Rule templates with teammates.

## Permissions

### Admin

* Create and delete Teams
* Invite and remove members
* Manage Team settings
* Full access to all Team chats

### Member

* Access all Team chats
* Create new chats within the Team
* Fork and continue existing conversations
* Cannot invite others or delete the Team

### View-only

* Read Team chats
* Fork conversations to personal workspace
* Cannot create new chats or modify existing ones

## Teams vs public sharing

<Tabs>
  <Tab title="Teams (private)">
    **Use when:**

    * Working on confidential client projects
    * Collaborating with colleagues
    * Iterating internally before publishing
    * Need ongoing access and collaboration

    **Visibility:** Only team members
  </Tab>

  <Tab title="Public sharing">
    **Use when:**

    * Publishing research or insights
    * Sharing examples or tutorials
    * Contributing to community knowledge
    * No ongoing collaboration needed

    **Visibility:** Anyone with the link

    Learn more in [Sharing & exporting](/flipsideai/sharing)
  </Tab>
</Tabs>

## Best practices

<AccordionGroup>
  <Accordion title="Name chats clearly" icon="tag">
    Use descriptive names so teammates can quickly find relevant analyses:

    * ✅ "Arbitrum DEX volumes Q1 2024 - Client X"
    * ✅ "Aave liquidation analysis - Risk report"
    * ❌ "New chat" or "Untitled"
  </Accordion>

  <Accordion title="Fork before experimenting" icon="code-fork">
    If you want to explore a tangent without cluttering the main chat:

    1. Fork the conversation
    2. Experiment in your forked version
    3. Share back to the Team if the tangent proves valuable
  </Accordion>

  <Accordion title="Document methodology" icon="book">
    At the end of major analyses, add a summary message:

    * Key findings
    * Data sources used
    * Limitations or caveats
    * Suggested follow-ups

    This helps teammates understand context when they revisit later.
  </Accordion>

  <Accordion title="Use Teams for institutional knowledge" icon="building">
    Create a "Reference" Team for:

    * Standard analyses your team runs repeatedly
    * Definitions of custom metrics or thresholds
    * Template prompts for common questions

    New team members can onboard by reviewing this Team's chats.
  </Accordion>
</AccordionGroup>

## Common workflows

### Research collaboration

1. **Lead researcher** creates initial analysis in Team workspace
2. **Team members** review, ask follow-up questions, validate findings
3. **Lead synthesizes** feedback into final report
4. **Team publishes** final version publicly (if appropriate)

### Client reporting

1. **Account manager** creates Team for Client X
2. **Analysts** collaborate on recurring reports within the Team
3. **Quality check**: senior team member reviews before client delivery
4. **Export** polished artifacts for client presentation

### Protocol monitoring

1. **Create a "Protocol Health" Team** for ongoing monitoring
2. **Set up recurring analyses** (weekly TVL, user growth, etc.)
3. **Team members** rotate responsibility for updating reports
4. **Alerts**: flag anomalies or concerns in Team chat for visibility

## Leaving or deleting Teams

### Leave a Team

Members can leave a Team at any time. You'll lose access to Team chats but won't delete anything.

### Delete a Team

Only admins can delete Teams. **Warning:** This permanently deletes all Team chats and cannot be
undone.

Before deleting:

* Export important chats or artifacts
* Fork analyses you want to keep to your personal workspace

## Next steps

<CardGroup cols={2}>
  <Card title="Sharing & exporting" icon="share-nodes" href="/flipsideai/sharing">
    Learn how to publish Team analyses publicly
  </Card>

  <Card title="Rules" icon="sliders" href="/flipsideai/rules">
    Create consistent output styles for your Team
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/flipsideai/workflows">
    Use specialized Workflows for Team analyses
  </Card>

  <Card title="Data & results" icon="database" href="/flipsideai/data-and-results">
    Export data from Team chats
  </Card>
</CardGroup>