{"id":6073,"date":"2026-07-10T05:33:03","date_gmt":"2026-07-10T02:33:03","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6073"},"modified":"2026-07-10T05:33:04","modified_gmt":"2026-07-10T02:33:04","slug":"create-ftp-sub-user-spanel","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/create-ftp-sub-user-spanel\/","title":{"rendered":"How to Create an FTP Sub-User in SPanel"},"content":{"rendered":"\n

In Spanel, you create an FTP sub-user under Files > FTP Accounts<\/strong> using the New FTP Account form, where you set a username, a document root, and a password. SPanel namespaces every sub-user under your account, so the name you type becomes <account>_<subuser>, and the document root confines that login to one folder. This gives a developer or contractor access to a single directory without your main credentials. <\/p>\n\n\n\n

Note that plain FTP is unencrypted, so use FTPS for the connection.<\/p>\n\n\n\n

Who this is for<\/strong><\/h2>\n\n\n\n

This is for a site owner giving a developer, contractor, or agency FTP access to one part of their hosting account – a theme folder, a staging directory, or a single site root – without exposing everything. If you want a scoped, revocable login rather than your own credentials, this is the feature.<\/p>\n\n\n\n

What problem this solves<\/strong><\/h2>\n\n\n\n

Handing out your main FTP login is risky: it grants access to the entire hosting account, and you cannot revoke it without changing your own password and breaking your own clients. An FTP sub-user fixes that. You create a separate login, point it at one folder, and delete it when the work is done – your own access is untouched.<\/p>\n\n\n\n

How SPanel solves this<\/strong><\/h2>\n\n\n\n

Open Files > FTP Accounts<\/strong>. The page lists any accounts you already have and shows a New FTP Account<\/strong> button. <\/p>\n\n\n\n

Click it to open the create form, which has three fields: FTP username<\/strong>, Document Root<\/strong> (the home directory path the login is confined to), and Password<\/strong>, which shows the placeholder “Enter a Password”. Fill in those three fields and save; SPanel creates the account and it appears in the Existing FTP Accounts<\/strong> list. SPanel enforces the username format and binds the login to the folder you chose. You still choose a strong password, hand the credentials to the right person, and point their FTP client at the correct host and port.<\/p>\n\n\n\n

Why this is different in SPanel<\/strong><\/h2>\n\n\n\n

Two details are specific to SPanel. <\/p>\n\n\n\n

First, username namespacing<\/strong>: SPanel keeps every sub-user under your account, so the effective login is <account>_<subuser>. You cannot create a bare username, and that format prevents collisions with sub-users on other accounts on the same server. <\/p>\n\n\n\n

Second, the home directory is set at creation<\/strong>, so the sub-user stays in the document root you enter rather than browsing the rest of your account.<\/p>\n\n\n\n

Before you start<\/strong><\/h2>\n\n\n\n
    \n
  • Sign in to SPanel<\/strong> with your normal account login – this is done in the user interface, no admin access required.<\/li>\n\n\n\n
  • Know the exact folder the sub-user should be confined to<\/strong> before you open the form.<\/li>\n\n\n\n
  • Have a strong, unique password<\/strong>; do not reuse your account password.<\/li>\n\n\n\n
  • Know the FTP host and port<\/strong> the person will connect to, since SPanel does not configure their client.<\/li>\n<\/ul>\n\n\n\n

    Step-by-step<\/strong><\/h2>\n\n\n\n
      \n
    1. Open Files<\/strong> > FTP Accounts<\/strong>. You will see the FTP Accounts page with your existing accounts and the New FTP Account button.<\/li>\n<\/ol>\n\n\n\n
      \"How<\/figure>\n\n\n\n
        \n
      1. Click New FTP Account<\/strong>. The create form opens with the FTP username, Document Root, and Password fields.<\/li>\n<\/ol>\n\n\n\n
        \"How<\/figure>\n\n\n\n
          \n
        1. Enter the FTP username<\/strong>. The effective login will be namespaced as <account>_<subuser>, so keep the part you type short and recognizable.<\/li>\n\n\n\n
        2. Set the Document Root<\/strong> to the one folder this login should reach – in our example, \/home\/yoga\/kb-test\/. Double-check this path before saving: it is the boundary that keeps the sub-user out of the rest of your account, so a wrong path can over-expose your files.<\/li>\n\n\n\n
        3. Enter a password in the Password<\/strong> field (it shows “Enter a Password”). Use something strong and unique.<\/li>\n\n\n\n
        4. Save<\/strong>. The account is added and appears in the Existing FTP Accounts list. From there you can hand off the credentials and delete the account later when access is no longer needed.<\/li>\n<\/ol>\n\n\n\n

          What happens behind the scenes<\/strong><\/h2>\n\n\n\n

          When you save, SPanel registers the sub-user under your account name and ties it to the document root you entered. The namespacing keeps your sub-users distinct from everyone else’s on the same machine, and the home directory binding enforces the folder boundary – so the confinement is a property of how the account is created, not something the person connecting can opt out of.<\/p>\n\n\n\n

          Limitations and edge cases<\/strong><\/h2>\n\n\n\n
            \n
          • The username is namespaced.<\/strong> SPanel enforces the <account>_<subuser> format, so you cannot pick a standalone name. This means: tell the person their full login is the prefixed form, or their client will fail to authenticate with the short name alone.<\/li>\n\n\n\n
          • A sub-user is not a separate system identity.<\/strong> It is an FTP login scoped to a home directory, not a Linux user or a separate filesystem identity. If you need OS-level separation or shell access, an FTP sub-user is the wrong tool.<\/li>\n\n\n\n
          • Plain FTP is unencrypted.<\/strong> Credentials and file contents travel in clear text. Use FTPS so the login and data are encrypted in transit; see Connect over FTP and FTPS in SPanel for the host, port, and client settings.<\/li>\n<\/ul>\n\n\n\n

            Troubleshooting<\/strong><\/h2>\n\n\n\n
            Symptom<\/td>Likely cause<\/td>What to do<\/td><\/tr>
            Login is rejected with the name you typed<\/td>The client is using the short name, not the namespaced one<\/td>Connect with the full <account>_<subuser> login<\/td><\/tr>
            Sub-user sees more or fewer files than expected<\/td>The Document Root was set to the wrong path<\/td>Delete the account and recreate it with the correct folder<\/td><\/tr>
            New account is not in the list<\/td>The form was not saved, or a field was empty<\/td>Reopen New FTP Account, complete all three fields, and save<\/td><\/tr>
            Connection works but credentials look exposed<\/td>Connecting over plain FTP, not FTPS<\/td>Switch the client to FTPS and reconnect<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            When to use this \/ when not to use this<\/strong><\/h2>\n\n\n\n
            Use this when<\/td>Skip or use something else when<\/td><\/tr>
            You want to give one person scoped FTP access to a folder<\/td>You need shell or SSH access<\/td><\/tr>
            The access should be easy to revoke later<\/td>You need a true separate system user identity<\/td><\/tr>
            You want your own credentials to stay private<\/td>The person needs to manage databases or email<\/td><\/tr>
            Work is limited to a known directory like a site root<\/td>The task is better done in WordPress Manager or the file manager<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            FAQ<\/strong><\/h2>\n\n\n\n

            Q:<\/strong> What username will the developer log in with?<\/strong><\/p>\n\n\n\n

            A:<\/strong> The namespaced form, <account>_<subuser>. SPanel enforces this, so the short name you type will not authenticate on its own.<\/p>\n\n\n\n

            Q:<\/strong> Can the sub-user reach folders outside the document root?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. The home directory you set at creation confines the login to that folder. To change it, delete and recreate the account with the right path.<\/p>\n\n\n\n

            Q:<\/strong> Is the FTP sub-user a separate Linux user?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. It is an FTP login scoped to a directory, not a system user or filesystem identity, and cannot be used for shell access.<\/p>\n\n\n\n

            Q:<\/strong> Is the connection encrypted?<\/strong><\/p>\n\n\n\n

            A:<\/strong> Not over plain FTP – that is clear text. Use FTPS to encrypt credentials and data in transit; the FTPS article covers the settings.<\/p>\n\n\n\n

            Q:<\/strong> How do I remove access when the work is done?<\/strong><\/p>\n\n\n\n

            A:<\/strong> Delete the account from the Existing FTP Accounts list. Your own account and other sub-users are unaffected.<\/p>\n\n\n\n

            Q:<\/strong> Does creating a sub-user change my main FTP login?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. The sub-user is separate, so your own credentials and access stay exactly as they were.<\/p>\n\n\n\n

            Q:<\/strong> Can two accounts on the server have the same sub-user name?<\/strong><\/p>\n\n\n\n

            A:<\/strong> The namespacing prevents a collision: each name lives under its own account, so the effective logins stay distinct even if the typed part matches.<\/p>\n\n\n\n