Members & Roles

Members are the users who have access to a project. Each member is assigned a role that determines exactly what they can see and do within that project. Roles are scoped to the project — the same user can be an Owner in one project and a Reader in another. Runner's global Admin role, which governs executors, settings, and user management, does not automatically grant access to any project; admins still need to be added as members like anyone else.

Project roles

Runner has four project roles, ordered from most to least permissive.

Permission	Owner	Maintainer	Operator	Reader
View all project resources	✓	✓	✓	✓
Trigger runs (Run Now)	✓	✓	✓
Abort and delete own runs	✓	✓	✓
Abort and delete any run	✓	✓
Create, edit, and delete environments	✓	✓
Create, edit, and delete files	✓	✓
Create, edit, and delete schedules	✓	✓
Manage members	✓
Edit project settings and delete project	✓

Owner — full control over the project. Owners are the only role that can manage who has access and change project-level settings. Every project must have at least one Owner.

Maintainer — can build and maintain everything inside a project: environments, files, and schedules. Can also trigger, abort, and delete any run. Cannot manage members or change project settings.

Operator — intended for users who run workflows but should not change how they are configured. Operators can trigger runs and manage the runs they started, but cannot edit environments, files, or schedules.

Reader — view-only access. Readers can inspect all project resources — environments, files, schedules, runs, and logs — but cannot make any changes or trigger runs.

Your members

The member list shows all users who have access to the current project. Each row shows the member's email address and Gravatar, their role, and when they were added and by whom.

You can filter by role and sort by email address, role, or date added. Use the search box to find a member by email.

Adding a member

Adding a member requires the Owner role. Click Add Member, enter the user's email address, select a role, and click Save. The email field autocompletes from existing Runner user accounts — only users who already have a Runner account can be added as members.

If SMTP is configured in Settings, the new member receives an email notification when they are added.

Changing a role

To change a member's role, click their row in the list and select a new role from the dropdown. Changing a member's role requires the Owner role.

Two constraints apply:

• You cannot change your own role. Ask another Owner to change it for you.
• The role of the sole Owner cannot be changed. Promote another member to Owner first, then change the original Owner's role.

Removing a member

Removing a member revokes their access to the project immediately. Click the delete button on the member's row or open their detail page and click the delete button there. Removing a member requires the Owner role.

The sole Owner of a project cannot be removed. Promote another member to Owner first.

If SMTP is configured in Settings, the removed member receives an email notification.

Leaving a project

Any member can leave a project themselves by opening their own entry in the member list and clicking Leave Project. Leaving a project removes your own access immediately.

The sole Owner of a project cannot leave. Promote another member to Owner first, then leave.