Open a time-limited site SSH grant for that one website, and send the developer the key.
The developer lands inside that site's directory, can use SSH and SFTP there, and cannot see your other sites or the server itself.
When the grant expires, or when you revoke it, the access ends. No shell account is ever created on the host.
A typical case
A small agency hosts a dozen client websites on one server. A freelance developer needs to fix the theme of one client's site this afternoon.
The agency does not want to give out the server's root login, and it does not want to hand over the passwords of eleven other clients' sites
along with it. What it needs is access that is as narrow as the job: one site, a few hours, a key that stops working by itself.
The grant is for Site B only. Other sites and the host stay out of reach. On a narrow screen, scroll the diagram sideways.
Steps: give one developer access to one site
Pick the site and the length. In the website list, open that site's SSH settings and choose how long the grant should last: 2, 4, 8, 12 or 24 hours. Choose the shortest time that covers the job.
Turn on site SSH. Nodekeeper generates a key for that site and shows the connection details: host, a port dedicated to that site, and the key. The key's password is displayed once, so copy it now.
Send the key and its password separately. For example, the key file by email and the password by chat. Do not send them in the same message.
The developer connects with an SSH or SFTP client. The session is confined to that site's directory.
Access ends. The grant stops when the time runs out. If the job finishes early, or something looks wrong, revoke it from the same dialog and open sessions are closed.
The Site SSH dialog on a member account: the grant is enabled with its dedicated port and remaining time, and the duration is chosen from a list. The Permanent option appears only for groups granted that permission. Domains and paths are redacted.The available durations: 2, 4, 8, 12 and 24 hours, plus Permanent for groups that hold that separate permission.
Which access path to use
Give the least power that still does the job. Nodekeeper offers several ways in, and they do not all need a shell.
Ways to give someone access to one website and what each is suited to
Access path
Best for
Scope
Ends
Browser file manager
A client who edits a few files
That site's files
When you remove the account's access
Site FTP
Tools that only speak FTP
That site's files, as the site's own user
When you turn FTP off
Site SSH and SFTP
Developers: command-line work, deploy scripts, file transfer
That site's directory, key-only
Automatically after 2 to 24 hours
Permanent site SSH
A long-term maintainer you trust
Same as above
Only when you revoke it; a separate permission
Host SSH is a different thing and stays with the administrator. Giving someone site SSH never adds them to the host's SSH configuration.
What the boundary really is
Site SSH is served by a separate Nodekeeper SSH service, not by the host's own SSH daemon. A site SSH account is an access mechanism Nodekeeper manages;
it is not a virtual machine or a container. The boundary comes from how every site is set up in the first place:
Each site's code runs as its own system user and group, which no other site shares.
PHP gets one pool per site. Apache gets one instance per site by default.
The site root is owned by the system, so a site cannot open its own boundary even if its files are set to world-writable.
Archives extracted or restored in the panel never create links that point outside the site.
Who may open grants: permissions by user group
Two questions are easy to mix up: who may open a grant, and who owns the site. Nodekeeper checks both. A permission says what an account may do;
every request also checks that the site belongs to that account, so a member cannot open access to somebody else's site.
Every permission can be assigned per user group. Opening temporary site SSH for your own sites is something ordinary members can do by default.
Permanent site SSH is a separate permission. By default only the administrator group has it. Grant it to a group you create for selected customers or maintainers, not to everyone.
User groups, roles and delegated administration are part of Pro and up. Site isolation, site SSH and FTP work on every plan, including Free.
Panel actions are written to the audit log, so you can see who opened what.
Limits to know before you rely on it
Isolation separates sites from each other. It does not protect against someone who already has root on the host, and it does not replace keeping the host patched.
If you attach several sites to one shared Apache instance, those sites share a runtime user and lose their separation from each other.
One grant is active per site at a time, and after you reset an FTP password the running FTP instance keeps the old one until it is restarted, so restart it after each reset.
Questions people ask
Does the developer need a panel account?
No. They only need the key and its password. The site owner, or the administrator for sites the agency hosts, opens the grant in the panel.
Can the developer use SFTP as well as SSH?
Yes. SSH and SFTP are both confined to the site's directory, so file transfers and command-line work happen inside that site and nowhere else.
How do I take access away early?
Revoke the grant from the Site SSH dialog. Open sessions are closed. To stop FTP, turn it off or reset its password and restart the instance.
Give each person only their own site
See per-site SSH, SFTP and FTP, site isolation and group permissions together on the site access page. Site SSH is included in the Free plan.