Shares
A share gives one of your domain users SFTP or FTPS access to a folder in your account's home directory.
Your provider can remove the file-transfer server from a small server. Then there's no SFTP or FTPS access, the panel doesn't show the Shares page, and the API and MCP server don't have the share operations.
Two typical uses: a web designer maintaining one site's files without your panel account, or a colleague needing a place for large files.
Every access authenticates as a domain user you created. To make files publicly reachable over the web, put them in a website's document root or in a directory mount.
How a person uses a share
A share uses the domain user's identity. If you share a folder named
website with [email protected], Anna signs in to the file-transfer
server with:
| Username | [email protected]: her address, with the share's name after a plus sign. |
| Password | Her normal email password. |
| Server | Her mail server's domain. |
| Protocol | SFTP on port 2222, or FTPS with explicit TLS on port 21 or implicit TLS on port 990. |
The share's page shows the exact name and ready-to-use connection examples.
Anna sees only the shared folder, not the rest of your home directory. There's no separate share password, so she learns nothing new and you distribute nothing; if her email password is reset, the share follows it.
A user who can only use a passkey can't use a share, and neither can one whom a policy stops from signing in with a password.
Create and manage a share
Create a share from the Shares page, or directly from the Share action on a folder in the file manager.
A share has three parts:
- the domain user it belongs to
- a short name, in lowercase letters and digits, which becomes the
+namepart of the login - the folder, as a path relative to your home directory
Ordinary file permissions control what the user can do inside the folder. No setting on the share does.
Deleting the share stops the access immediately; the folder and its contents stay.