Everything you can see and do in BriefFlow is driven by your role. There are three default roles.

Administrator#

Full access: managing users and invitations, creating and assigning tasks, reviewing understanding, managing projects and releases, workspace settings, reporting, and exports.

Developer#

Works assigned tasks: submits understanding, updates task status and comments, and tracks their own work on My Board. Developers see the tasks they own or are assigned to, not the whole workspace.

Tester#

Everything a Developer has, plus the ability to perform QA — starting QA cycles, recording results, and requesting changes.

How visibility works#

Access in BriefFlow is permission-driven, not just role-labeled: what a page shows and what actions are available both check the same underlying permission a role carries. A Developer and a Tester see different things not because BriefFlow special-cases their role names, but because they hold different permissions.

Task-level access#

Beyond role, individual task visibility follows a simple rule: you can see a task if you're its owner, one of its assignees, or you hold a permission that grants visibility into all tasks (like an Administrator's).