Project Roles & Sharing
Who can see and do what
Every FlowQi project decides, on its own, who takes part and what each person is allowed to do. That happens in two places:
You might ask about sharing a project, access, permissions, or inviting people to a project — in FlowQi that is project roles & members.
- Roles — what a person can do in the project (view, comment, create tasks, manage the project).
- Privacy — how wide the project is open, from “only people with access” to everyone.
On top of that, you can share content out of the project with a secure link at a permission level of your choosing. This article walks through all of it.
Where to manage roles and access
You manage roles, members, teams, and privacy from a project’s Settings — the gear icon at the top-right of any project view.
The Settings dialog has these tabs:
| Tab | What it controls |
|---|---|
| General | The project’s name, organization, time, tags, and description |
| Circle | The Circle the project belongs to |
| Team Members | The people (and teams) in the project, and their roles |
| Permissions | The available roles and what each one can do |
| Privacy | How wide the project is visible — Private or Public |
The four project roles
People take part in a project through a role. You’ll see the roles, and exactly what each one allows, on the Permissions tab:
| Role | Capabilities |
|---|---|
| Owner | Full access to all project features and settings |
| Member | Can create tasks, manage members, and share content |
| Viewer | Can view project content and tasks |
| Commenter | Can view and comment on tasks |
A few things worth knowing:
- The person who creates the project becomes its Owner.
- A project always keeps at least one Owner — you can’t remove the last one. To hand the project over, give someone else the Owner role first.
- Only Owners and Members can manage members and share content; Viewers and Commenters are read-only (Commenters can also leave comments on tasks).
Project roles (Owner / Member / Viewer / Commenter) are not the same as Circle roles (Owner / Member / Viewer / Guest). They look similar, but they govern different things: a project role decides what you can do inside one project, while a Circle role decides your place in the wider Circle. Someone can be a Member of a project and a Viewer of its Circle, or the other way round.
Adding people to a project
- Open the project and click the Settings gear (top-right).
- Go to the Team Members tab.
- Click Add users to project and pick the people you want.
- For each person, set a role with the role dropdown — Owner, Member, Viewer, or Commenter.
- Save your changes.
Each added person shows up in the list with their role dropdown and a remove (×) button, so you can change a role or remove someone at any time.
Adding whole teams
Instead of adding people one by one, you can assign an entire team to a project and give the team a role. Everyone on that team picks up the project at that role — handy when a fixed group always works together. Manage team assignments from the same Team Members tab.
Members must be in the project’s Circle
Adding someone to a project isn’t enough on its own: a person also has to be part of the project’s Circle to actually act in it. FlowQi takes the intersection of the two — if an assigned person isn’t a member of the Circle, they can’t do anything in the project, no matter which role you gave them.
So if a teammate has a role but still can’t reach a project, check that they’re a member of its Circle. To learn how Circles group people and content, see Circles .
When access looks “wrong,” it’s almost always the Circle. Confirm the person is both in the project (Team Members) and in its Circle before changing roles.
Removing a member
Remove someone from the Team Members tab with the × button next to their name. When you remove a member, FlowQi unassigns them from that project’s tasks — any tasks they were the assignee on are freed up so you can hand them to someone else.
Remember you can’t remove the last Owner. Set a new Owner first if you need to take the current one out.
Privacy: how wide the project is open
The Privacy tab controls who can view the project, on top of roles:
| Setting | Meaning |
|---|---|
| Private | Only people with access can see the project |
| Public | Widens visibility so more people can view the project |
Use Private when a project should stay limited to the people you’ve explicitly added. Switch to Public when you want a broader audience to be able to view it. Privacy fine-tunes visibility; roles still decide what each person can do.
Sharing content with a link
Members and Owners can share content out of a project. Sharing creates a secure link that carries a permission level, so the person you send it to gets exactly the access you intend — no more.
A shared link can grant:
| Permission | What the recipient can do |
|---|---|
| View | See the shared content, read-only |
| Comment | See the content and add comments |
| Edit | See and change the content |
You can also set an expiry on a shared link, so the access ends automatically after a date you choose. That makes sharing safe for one-off reviews or temporary collaborators — share at the chosen permission level, set an expiry, and the link closes itself when the time is up.
Share at the lowest permission that still gets the job done — View for a read-through, Comment for feedback, Edit only when someone genuinely needs to change things. Add an expiry for anything temporary.
Quick reference
| You want to… | Where to go |
|---|---|
| Change what someone can do | Settings → Team Members → role dropdown |
| Add a person or a team | Settings → Team Members → Add users to project |
| See what each role allows | Settings → Permissions |
| Widen or limit who can view | Settings → Privacy |
| Give outside access to content | Share a link at view, comment, or edit |