Members
The Members page is where you manage who can do what in your organization. It lives under Settings → Members (avatar dropdown in the top-right of the Console). Each organization has its own members list — switching organizations changes who you see here.
Roles
Depfloy has five built-in roles. Pick the role that matches what someone needs to do; do not give a more powerful role "just in case". You can change a member's role any time.
Owner
Full access to all organization settings, servers, and team members. The Owner is the only role that can transfer ownership and delete the organization. Each organization has exactly one Owner.
Admin
Full access to the organization, except managing or assigning Owner roles. Admins can do everything Owners can except transfer ownership or delete the organization itself.
Manager
Manages servers and team, but not billing or organization settings. Managers can create new servers, transfer them, invite teammates, and manage projects — but they cannot view or change billing or organization-wide settings.
Developer
Full access to servers and sites, but can't create new servers. Developers can deploy, manage existing servers, run commands, edit project settings, manage SSL and domains. They cannot create new servers, manage members, or touch billing.
Viewer
View all servers, sites, and sensitive data without making changes. Viewers can see deployment history, view logs, and inspect configuration. They cannot trigger deployments or change anything.
Capability summary
Use the Compare roles button on the Members page for a side-by-side capability table. Highlights:
| Capability | Owner | Admin | Manager | Developer | Viewer |
|---|---|---|---|---|---|
| View servers, projects, deployments, logs | ✓ | ✓ | ✓ | ✓ | ✓ |
| Trigger deployments | ✓ | ✓ | ✓ | ✓ | — |
| Update server settings | ✓ | ✓ | ✓ | ✓ | — |
| Manage projects (SSL, env, domains, jobs) | ✓ | ✓ | ✓ | ✓ | — |
| Create new servers | ✓ | ✓ | ✓ | — | — |
| Transfer servers between organizations | ✓ | ✓ | ✓ | — | — |
| Invite, edit, and remove members | ✓ | ✓ | ✓ | — | — |
| Manage API tokens | ✓ | ✓ | ✓ | — | — |
| View / update organization settings | ✓ | ✓ | — | — | — |
| Transfer ownership | ✓ | — | — | — | — |
| Delete the organization | ✓ | — | — | — | — |
Limiting access to specific servers or projects
Beyond a role, every member except the Owner can be scoped — limited to a subset of the organization's servers or projects.
- Server scope — the member can only see and act on the servers you select.
- Project scope — the member can only see and act on the projects you select.
- Project access is built on top of server access: a member needs access to a project's server before project access can be granted. If you remove a server from someone's scope, their project scope on that server is removed automatically.
The Owner is unscoped because ownership is the permanent organization-wide role; transferring ownership is a separate action.
Invite a new member
Two invite flows depending on whether the person already belongs to another organization in your Depfloy account:
- Invite member — for someone outside your Depfloy account. Enter their email; they receive an invitation, create an account, and are added to the organization with the role and scope you chose.
- Add existing user — for someone who already belongs to another organization in your Depfloy account. The list shows users not yet in the current organization, with an "in N orgs" badge so you know who is where. They are added immediately, without a separate invitation email.
Both flows let you set the role and scope at invite time. You can change either later from the member's row.
Edit a member
Click a member's row to edit their role or scope. Changes take effect on the member's next page load — no sign-out required.
Remove a member
Click Remove next to a member to remove them from the current organization. The user account itself is not deleted; if they belong to other organizations in your Depfloy account, those memberships are unaffected.
Migration notes
If you are reading this after upgrading from an earlier version:
- Members who used to have the legacy "member" role are now Viewers. Re-assign them to a more appropriate role if they were doing more than viewing.
- Members who used to have "Deployer" are now Developers. The capability set is unchanged; only the name changed.
- The new Manager role sits between Admin and Developer — it is a good fit for someone who needs to manage the team and infrastructure but not billing or organization settings.