COMMUNAL WORKSPACES
How communal workspaces work
In a communal workspace, saving is submitting: contributions are reviewed before others can find them.
A company workspace trusts its members. A communal one — a school, a community, a partner network — cannot. There, anything added is a contribution that starts as unreviewed and only becomes shared memory when a moderator accepts it. This applies however it arrives: flow save, flow contribute, email or an assistant.
flow workspace create "Year 9 science" --communalThe type is chosen at creation and never converted. The creator becomes administrator.
Roles
| Role | Can |
|---|---|
| Contributor | Search accepted memory, contribute, see their own contributions, challenge, forget their own posts. |
| Verifier | The same as a contributor for now — reserved for peer review. |
| Moderator | Review contributions and disputes, correct shared memory, see who is here, make join links. |
| Administrator | Also change roles and set the review rules. |
flow contribute <text>- Submit to a communal workspace. It may need a moderator's review before anyone else can find it.
flow my contributions- Your own submissions to this workspace, and where each one stands.
flow rules- This workspace's review rules — who joins without an invite, and how much history earns faster publishing.
flow rules set domains <…> · threshold <…>- Change this workspace's rules. Administrators only.
Review rules
Administrators can let contributors with a good track record publish without review (a reputation threshold), and allow people from certain email domains to join. With no threshold set, everything is reviewed.
Contributors never see the member list: in a school, members often don’t know each other and many are students. Decisions and meeting minutes are not available in communal workspaces.