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
Setting Up a Team
1
Create a Team
- Click the Teams panel in the bottom-left of Flipspace
- Select Create new team
- Name your team (e.g., “Research Team,” “Client Analytics”)
2
Invite members
- Open your Team settings 2. Click Invite members 3. Enter email addresses for team members
- Set permissions (view-only or full access)
3
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
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 to ensure consistent output:Permissions
| Role | Capabilities |
|---|---|
| Admin | Create/delete Teams, invite/remove members, full chat access |
| Member | Access all Team chats, create new chats, fork conversations |
| View-only | Read Team chats, fork to personal workspace |
Best Practices
Name chats clearly
Name chats clearly
Use descriptive names so teammates can quickly find relevant analyses:
- “Arbitrum DEX volumes Q1 2024 - Client X”
- “Aave liquidation analysis - Risk report”
Fork before experimenting
Fork before experimenting
If you want to explore a tangent without cluttering the main chat:
- Fork the conversation
- Experiment in your forked version
- Share back to the Team if the tangent proves valuable
Document methodology
Document methodology
At the end of major analyses, add a summary message:
- Key findings
- Data sources used
- Limitations or caveats
- Suggested follow-ups
Use Teams for institutional knowledge
Use Teams for institutional knowledge
Create a “Reference” Team for:
- Standard analyses your team runs repeatedly
- Definitions of custom metrics or thresholds
- Template prompts for common questions
Common Workflows
Research Collaboration
- Lead researcher creates initial analysis in Team workspace
- Team members review, ask follow-up questions, validate findings
- Lead synthesizes feedback into final report
- Team publishes final version (if appropriate)
Client Reporting
- Account manager creates Team for Client X
- Analysts collaborate on recurring reports within the Team
- Quality check: senior team member reviews before client delivery
- Export polished artifacts for client presentation
Protocol Monitoring
- Create a “Protocol Health” Team for ongoing monitoring
- Set up recurring analyses (weekly TVL, user growth, etc.)
- Team members rotate responsibility for updating reports
- Alerts: flag anomalies or concerns in Team chat for visibility