Flow: members, roles, teams and billing
Only members of a workspace can work in it. Roles define what each member can see and change. Teams power "own team" permissions. This article covers invitations, roles, permissions, teams, and Flow billing.
Members
The member list is in "Settings → Members". The table shows the member, email, role, status ("Active" or "Disconnected"), and member ID. The owner and admins can change a member's role right in the table.
A person joins a workspace only after accepting an invitation themselves. Nobody can be added to a workspace without their consent.
Flow takes a member's name and photo from their Sensever account. They are the same in every workspace and on every screen: in tables, on the board, in the card, in filters, reports, and mentions. There is no separate member name inside a workspace. If someone changes their name or photo in their account, Flow usually shows the new one within a minute, and within 24 hours at the latest. If there is no photo, the initials of the name are shown instead.
Invitations
The owner and admins can invite people.
Open "Settings → Members".
In the "Invite member" field, enter an @tag, name, email, or phone number. Tags are matched by prefix; names, emails, and phone numbers only in full. The search covers everyone on Sensever, not just people who have already used Flow.
Choose the "Invitee's role": "Member", "Viewer", or "Admin".
Click "Invite" next to the person you found.
The invitation arrives in the person's Sensever notifications. They become a member once they accept it. They can also decline it there.
If nobody on Sensever has that email, an "Invite by email" button appears. Sensever sends an invitation email (no more than three emails per address in 24 hours). The invitation waits until the person signs up with that address, confirms it, and accepts the invitation. If the email could not be sent, Flow tells you — let the person know yourself.
Open invitations are listed in the "Invitations" block with the role and who sent them. The "Cancel" button revokes an invitation. To change the role of an invitation that has not been accepted yet, cancel it and invite the person again.
You cannot pick a custom (non-system) role in an invitation. Assign it after the person accepts.
A phone number is found only if it is verified and the person has not hidden it. The search never shows the email or phone number of the person it finds.
System roles
Every workspace has five system roles. They cannot be renamed or deleted.
Role | Who it is |
|---|---|
Owner | Can do everything, including deleting the workspace. Owner permissions cannot be changed. A workspace can have several owners; the last one cannot be removed |
Admin | Manages the workspace: types and fields, members and access, automations, processes, webhooks |
Member | A regular employee who works with objects |
Viewer | Can only view |
Integration | A service role for API keys, automations, and integrations. Its permissions cannot be changed, and it is never assigned to people |
Default role permissions:
What | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
View objects | all | all | all | all |
Create objects | yes | yes | yes | no |
Edit objects | all | all | own team's | no |
Change status and click action buttons | all | all | own team's | no |
Archive objects | all | all | own | no |
Start processes | yes | yes | yes | no |
Custom views | all | all | own | no |
Types, fields, and statuses | yes | yes | no | no |
Automations and processes: setup | yes | yes | no | no |
Webhooks and integrations | yes | yes | no | no |
Members, roles, and access | yes | yes | no | no |
Delete workspace | yes | no | no | no |
Newer features have no permissions of their own — they follow the permissions on the object:
logging time, starting a timer, and editing or deleting your own time entry require permission to edit the object; the owner and admins can change other people's time entries;
seeing time entries and totals requires permission to view the object;
setting up or stopping a task's recurrence requires permission to edit the object;
@ suggests only members who can see the object, and only someone who can see the object gets the mention notification.
So a viewer cannot log time or set up recurrence, and time tracking never makes anyone a paid staff member beyond their regular permissions.
The owner and admins can change the permissions of the "Admin", "Member", and "Viewer" roles in the "Access" section. For example, they can let members edit any object or stop them from archiving.
The "Access" section: roles and permissions
"Settings → Access" → the "Roles" tab. The list of roles is on the left, and the permissions of the selected role are on the right. Roles are assigned to members in the "Members" section. If a person has several roles, the permissions add up: the broadest one wins.
Custom role
The "+ New role" button creates a role. Enter a name (for example, "Sales manager") and pick "Based on role" — permissions are copied from the selected role. The "Empty — no permissions" option creates a role with no permissions. A custom role can be renamed and deleted. A role cannot be deleted if it is someone's only role: assign that person another role first.
Objects
A "type × action" table. Actions: "View", "Create", "Edit", "Change status", "Archive". Values:
Value | Meaning |
|---|---|
"All" | All objects of the type |
"Own team's" | Your own objects and objects whose assignee shares a team with you |
"Own" | Objects where you are the assignee or author |
"No" | Nothing |
The first row is "All types". For an individual type, you can keep "Same as all" or set a value of its own.
Permissions only grant; they never deny. A per-type permission is added on top of the "All types" row: you cannot take away from a type what is granted to all types. If the "All types" row has "View: All", the role sees objects of every type, whatever the values of individual types. So to let a role see only some types, set "No" in every column of the "All types" row and grant permissions to the types you need. Roles add up the same way: a person with two roles gets everything each of them allows.
"Create" can only be "All" or "No".
Fields
For each field of a type, you can choose a mode:
"Same as object" — the field is available exactly like the object itself;
"Read-only" — the field is visible, but the role cannot change it;
"Hidden" — the role does not see the field in the card or in lists.
Workspace settings
"Can / cannot" toggles: "Types, fields and statuses", "Automations", "Processes", "Webhooks and integrations", "Accept external events (API)", "Members, roles and access". Separately, "Views (saved table, board and calendar views)": "All", "Own only", or "No".
Click "Save permissions" to save your changes. The owner and admins can change permissions. Only the owner can delete the workspace: an admin cannot grant that permission to themselves or anyone else.
Separate workspace or per-type roles
When several departments use Flow, there are two ways to keep their data apart.
What | Separate workspace | One workspace, per-type roles |
|---|---|---|
How it works | The department has its own workspace with its own types, members, roles, automations, and settings | Everyone works in one workspace, and the department's role sees and changes only its own types |
Who sees the data | Only members of that workspace | The department sees only its own types. Workspace owners and admins see all types |
Relations between objects | Only within the workspace | Objects of different departments can be related, for example a purchase to a deal, and shared rules and reports can be built on them |
When to choose | Not even admins of other departments should see the department's data; the department has its own process and its own admins; work with an external contractor | Departments work on shared objects and the manager needs the full picture, but department staff do not need to see other types |
You can combine both approaches. A person still sees all their workspaces at once in "All workspaces" mode.
Example: the purchasing department sees only purchases
A workspace has the types "Deal", "Task", and "Purchase". Purchasing staff should work only with purchases.
Open "Settings → Access", the "Roles" tab, and click "+ New role". Name it "Purchasing" and set "Based on role" to "Member". The "Member" role is used as the base so that the new role keeps the basic workspace permissions (seeing types, views, processes). The "Empty — no permissions" role does not work for this.
In the "Objects" table, set "No" in every column of the "All types" row: "View", "Create", "Edit", "Change status", "Archive".
In the "Purchase" type row, set the permissions you need, for example "View: All", "Create: All", "Edit: All", "Change status: All", "Archive: Own".
Click "Save permissions".
In "Settings → Members", select the "Purchasing" role for the department's staff. Choosing a role in the table replaces the previous one: staff must not keep the "Member" or "Viewer" role, or they will still see all types.
An invitation lets you choose only a system role. So invite new staff as usual and assign the "Purchasing" role after they accept the invitation. Until the role is changed, the person sees every object their system role allows.
If some purchase fields contain data not everyone should see (for example, the supplier price), hide them in the same role in the "Fields" block.
The "Purchasing" role allows changing data, so department staff count as paid staff (see "Billing" below).
Teams
"Settings → Access" → the "Teams" tab. A team groups people. A role with the "Own team's" permission lets a person see and change objects whose assignee is on the same team.
Create a team (for example, "Sales"), then use the "Members" button to choose its members. A team can be renamed and deleted. Once a team is deleted, "own team" permissions no longer apply through it.
A team grants no permissions on its own. It only widens the meaning of "Own team's" in its members' roles.
Disabling a member
A disabled member ("Disconnected" in the list) cannot sign in to the workspace. At the same time, Flow immediately:
revokes all of that member's API keys in the workspace;
turns off all of their webhooks.
If the person is invited again later and accepts, the keys and webhooks do not come back: they have to be issued again.
If the person's whole Sensever account is disabled, everything that runs on their behalf in Flow stops: sessions, keys, webhooks, automations. When the account is enabled again, everything starts working again. Changing the password and signing out on all devices do not stop keys and webhooks — only sessions are revoked.
Members are disabled through the API: see Flow API: workspace, access and notifications.
Billing
Flow is free for a single person in any number of workspaces. The workspace owner pays for the people who change data in their workspaces.
Rule | How it is counted |
|---|---|
Price | $5 per staff member per month |
Staff member | A person who has at least one permission to change data in the workspace: create, edit, change status, archive, configure, and so on |
Free | Viewers who only view. Permissions on their own views (filters, boards) do not make someone a staff member |
Free | Bots, integrations, API keys, and other service members |
Free | The payer themselves |
Several workspaces | A person who works in several workspaces of the same owner is counted once |
Main | Counted as a regular workspace |
Counted | Only active workspaces and active members; invitees are counted after they accept the invitation |
The payer is the workspace owner; if there are several owners, the one who joined the workspace first (usually its creator) pays. If that owner is disabled, the next active owner pays.
What counts is the set of permissions, not the role name. A custom role with at least one edit permission makes a person a staff member. A custom role with view permissions only does not. Teams do not affect the bill.
The number of staff members is recalculated several times an hour, and charges are prorated by time: a staff member who worked half a month costs half. Charges appear in the Sensever finance section as the "Flow · staff" line.
Example: you have two workspaces. The first has you and two members; the second has you, one of the same members, and two viewers. Besides you, there are two staff members: $10 per month.
What's next
Flow: workspaces and templates — workspaces, Main, and templates.
Flow: notifications and reminders — who Flow notifies and when.
Flow API: workspace, access and notifications — members, roles, teams, and invitations through the API.
评论