Teams & Organizations

Organizations are the top-level workspace for servers, sites, members, and billing. Invite your team, assign roles, and collaborate with a clear permission model.

Overview

Everything in Deploynix belongs to an organization: servers, sites, databases, certificates, cloud provider credentials, Git repositories, DNS providers, and the subscription that pays for it all. You sign up as the Owner of your first organization, and you can be a member of any number of organizations owned by other people. Who gets to see or change each of those resources is decided by the member's role in the organization — one of Owner, Admin, Manager, Developer, or Viewer.

Organizations

When you register, Deploynix creates your first organization automatically and makes you its Owner. From there:

• Create another organization — use the workspace switcher in the top navigation to spin up a new one. Each organization has its own plan, members, and resources.
• Switch organizations — pick a different organization from the workspace switcher. The whole dashboard scopes itself to whichever organization is active; your servers list, sites list, settings, and billing all reflect it.
• Join someone else's organization — by accepting an invitation they send to your email.

Roles

Deploynix uses five built-in roles, stacked from most to least privileged. Each role has a numeric level that controls who can manage whom — you can only assign or change a role below your own.

Permissions at a Glance

Inviting Members

1. Open Settings → Members.
2. Click Invite Member.
3. Enter the person's email address and pick a role. You can only pick a role below your own level.
4. Click Send Invitation.

The invitee receives an email containing your organization's name, the role you're offering, your name as the inviter, and an Accept Invitation button. Invitations expire after 7 days; resend or cancel pending invitations from the same Members page. If the invitee isn't a Deploynix user yet, they'll register first and then be added to the organization on first login.

Managing Members

Change a Role

From Settings → Members, click the role dropdown on any row and pick a new role. You can only promote or demote members to a role below your own level, and you cannot change the Owner's role here — use ownership transfer for that.

Remove a Member

Click the Remove action on the row. Access is revoked immediately: the member is signed out of the organization's context on their next request and loses visibility of every resource. Their user account still exists — removal is organization-scoped.

Leave an Organization

Any member can leave an organization from their account settings. Owners can't leave without first transferring ownership (see below) or deleting the organization.

Transferring Ownership

Only the current Owner can transfer ownership to another existing member. Open Settings → Members, pick a member, and choose Transfer Ownership. On confirmation:

• The chosen member becomes the new Owner.
• The previous Owner is demoted to Admin so they keep working access but lose ownership-only powers.
• Billing stays with the organization — it doesn't follow the old Owner.

Switching Between Organizations

If you belong to more than one organization, the workspace switcher in the top navigation lists each one. Clicking an organization sets your active context — every subsequent page in the dashboard, every API call you make from the browser, and every link you follow scopes itself to the selected organization. Switch back and forth freely; Deploynix remembers where you were last.

Organization Settings

Admins and Owners can edit organization-level settings from Settings → Organization:

• Name — the display name users see. Changing the name doesn't affect any resources.
• Members — invite, change roles, remove, and see pending invitations.
• Billing — subscription, plan, payment method, invoices. See Billing & Plans.
• Transfer ownership — Owner only.
• Delete organization — Owner only; requires explicit confirmation.

Best Practices

• Give everyone the least privilege that does the job. Default new teammates to Developer or Manager and promote only when needed.
• Keep a backup Owner. Even though only one member holds the Owner role, make sure an Admin on the team can be promoted quickly if the Owner is unreachable.
• Remove members immediately when people leave. Role changes are live — don't wait for the next billing cycle.
• Separate production and staging into different organizations if you want hard isolation between credentials and billing. Put them in the same organization if you prefer shared resources and a single dashboard view.