Projects Get Collaborator Access
Project owners can now invite existing Tracsio users to collaborate by email. Shared projects appear in the project list and editors can work across project data without owning the project.
This is the first real collaboration layer for projects. Until now, project work mostly assumed a single owner; now the product can show shared projects and let a teammate contribute without transferring ownership.
The implementation touches more than the sidebar dialog. Access checks have to follow the same rule everywhere project data is read or changed, otherwise collaboration feels random.
We keep management deliberately narrow for now: only owners can invite or remove collaborators, and collaborators need to already exist in the app. That gives us a controlled version of team access before adding broader invite flows.
- Collaborator dialog: project owners can open project actions from the sidebar, invite collaborators by email, and remove existing collaborators.
- Shared project access: invited users now see shared projects in their project list with an editor role.
- Project member records: collaborator access is tracked through project-member records, with email and account-token matching for reliable access checks.
- Access checks expanded: project chat, experiments, feedback, ICP, public onepagers, and project queries now respect owner or editor access instead of owner-only assumptions.
- Sidebar project actions: owners get a project action menu for managing collaborators while editors keep a simpler project list.
- Project list roles: project list results now include whether the viewer is an owner or editor, so the UI can show the right controls.
- Legacy editor compatibility: existing editor emails are still honored while the new project-member access model takes over.