Members & roles
Add people to a project, set their roles, and assign AI personas that shape how the assistant works for them.
Open Members in a project to manage who's on it, what they can do, and how the AI treats them.
Add a member
To remove someone, use Remove next to their name. (The project owner can't be removed.)
Roles
A member's role controls what they can change in the project:
| Role | Typical permissions |
|---|---|
| Owner | Full control, including members and integrations. The owner can't be removed. |
| Admin | Manage the project, members, repositories, and Linear. |
| Member | Create and edit content, run AI generation, and manage tasks, docs, and skills. |
| Viewer | Read-only. Can browse but not change anything. |
Some actions are reserved for higher roles. For example, linking GitHub repositories and managing Linear require Owner or Admin, and deleting tasks or skills requires Owner or Admin.
Personas
Each member can be assigned one or more personas. Personas describe how a person works and directly affect the AI:
| Persona | What it signals |
|---|---|
| Business owner | Emphasis on scope, outcomes, and value. |
| Project manager | Emphasis on planning and task breakdown. |
| Developer | Implementation focus. Required to use the Developer Advisor in Ragnarock. |
| QA engineer | Test coverage and quality focus. |
| Stakeholder | Read-only visibility — stakeholders can't send AI messages. |
To set personas, use the persona picker next to a member and select any that apply. You can choose several.
Personas are the fastest lever on AI quality. If answers feel off-target — too high-level, or too technical — adjust your persona here before rewording prompts. See Getting the best outcomes.
If a member's only persona is Stakeholder, they have read-only access and can't send messages to the AI. Give them an additional working persona (such as Developer or Project manager) to let them interact.