Choose the right organization, team, or folder scope; add an existing flowmo account with Editor, Commenter, or Viewer access; and distinguish container-wide membership from one-project sharing.
Where: Dashboard → workspace sidebar → organization, team, or folder settings → Share with people
Key ideas
- Workspace hierarchy: Organizations contain teams; teams provide the membership context in which folders and projects are organized.
- Editor, Commenter, and Viewer: Editors can change authored work. Commenters can read and participate in review threads without editing. Viewers can read but cannot create comments. Owner-gated access and deletion controls remain unavailable to collaborators.
- Container membership is live: Organization, team, or folder membership grants every project currently in that scope and projects moved or created there later. Project invitations and links remain a separate, narrower grant.
- Personal containers need care: The personal organization cannot be shared. Personal team/folder sharing remains available for compatibility but warns that it includes all current and future default projects until access is removed.
Steps
- In the dashboard sidebar, select the organization and team you intend to manage.
- Open the organization, team, or folder settings and review existing people with access before inviting anyone.
- Add the person by the email address of their existing flowmo account and choose Editor, Commenter, or Viewer.
- For one-project access, use that project’s Share dialog instead of broadening workspace membership.
- Review access after role changes, transfers, or project moves, and remove invitations or members that are no longer needed.
Choose the narrowest useful scope
- Project Share: one project.
- Folder sharing: every project in that folder.
- Team membership: every project stamped with that team.
- Organization membership: every project stamped with that non-personal organization.
- Commenter: review participation without authored-document writes.
- Viewer: read-only access.
Tips
- Use Commenter when stakeholders need to leave review feedback but must not edit.
- Use Viewer for stakeholders who only need to inspect.
- Name organizations, teams, and folders by client or outcome so invite scope is obvious.
Limitations and important notes
- Available teams, seats, and organization features depend on the plan and account role.
- A public project link is not a substitute for managed workspace membership.
- Only the owner can change roles or remove people from a shared-in container.