Summary
Multi-user collaboration through teams and organisations. This feature underpins artefact sharing with specific users and organisation-level admin. Flagged as important to plan early so the application is built with these concepts in mind from the start.
Why Plan Early
Even if teams/orgs are not in the first release, the data model and access patterns should account for them:
- User identity should support belonging to an organisation
- Artefacts should have an ownership model that can extend to teams
- Permissions should be designed to accommodate sharing from day one
- API design should consider multi-tenancy
Core Concepts
Organisation
- A top-level entity (company, team, group)
- Has members (users) with roles
- May have billing/subscription at this level
- Manages team structure
Team
- A group within an organisation
- Users can belong to multiple teams
- Artefacts can be shared with a team (all members get access)
- Teams may have their own workspaces or shared data
Roles (Preliminary)
| Role | Scope | Capabilities |
|---|---|---|
| Owner | Organisation | Full admin, billing, delete org |
| Admin | Organisation | Manage teams, users, settings |
| Member | Organisation | Use the platform, create artefacts |
| Team Lead | Team | Manage team membership |
| Team Member | Team | Access team-shared content |
Sharing Model
With teams in place, artefact sharing extends to:
- Share with individual users (by email or username)
- Share with a team (all current and future members)
- Share with entire organisation
- Each with permission levels (view, comment, duplicate — TBD)
Open Questions
- Is there a free tier for individuals vs. paid for teams?
- How does team membership affect what data/explorations are visible?
- Can teams have shared workspaces (collaborative snippet collection)?
- Should there be team-level explorations (multiple users exploring together)?
- How do invitations work? Email invite? Link? SSO?
- What's the org creation flow? Self-service or sales-assisted?
- How does this interact with the platform-level data? (Spaces, sources, feeds — are these per-user or per-org?)
- Should there be a "personal" vs. "organisation" context switch?