Teams

Everything belongs to a team: sites, servers, resources, billing. You get one automatically when you sign up, called Personal, and you can create more — one per client is the usual pattern for an agency.

Switch between them from the sidebar. Everything on screen follows the team you are in.

Roles

There are two.

Owner — the person who created the team. Only the owner can:

• change anything in billing;
• connect or disconnect a git provider;
• add or remove SSH keys;
• add or remove team members.

Member — everyone else. A member can do everything else: create sites, deploy, roll back, add domains, run commands, restore backups, tear down environments.

There is no read-only role and no per-site permission. A member has full operational control of every store in the team. Add people accordingly.

Roles cannot be changed after the fact, and the owner cannot be removed. There is no "leave team" action.

Adding someone

Team → add a member by email.

• If they already have a Nautvia account, they join immediately.
• If they do not, an invitation is recorded and they join automatically the first time they register with that email address.

No invitation email is sent. Nautvia does not email them; you have to tell them to sign up. It is on the list to fix, and until then this page is the warning.

Pending invitations count against your seat limit, so revoke ones that will not be taken up.

Seats by plan, excluding the owner: 0 on Solo, 4 on Studio, unlimited on Agency. See Plans and billing.

Removing someone returns them to their personal team; their account is untouched.

SSH access

Add a public key under SSH keys — owner only. It is installed on every application server the team has, and on new ones as they are built.

ssh nautvia@your-server-ip
cd ~/site/current

The environment header's SSH dialog shows the exact address.

Two boundaries worth knowing:

• You connect as nautvia, not root. It is the user your store runs as, and it can sudo where the deploy needs to.
• Data servers never receive your keys. MySQL, Valkey and OpenSearch machines are closed. Reach the database through a tunnel via the application server — see Databases, cache and search.

Removing a key rewrites authorized_keys on every application server. A server that is powered off catches up when it next comes online.

Your own account

Settings → Security covers your password, two-factor authentication and passkeys. Two-factor is worth turning on: your account can deploy code to, and read the database of, every store in your teams.

Deleting your account under Settings → Profile removes your user record. It does not destroy your teams' servers, volumes or backups, and it does not cancel a subscription — tear those down first. The Privacy Policy describes the full erasure process.