Some corrections below:
1- As FTP user Admin you want to access to all of example.com/
2- As FTP user Jane you want to access via FTP to example.com/folder/subdir1
3- You want to have Jane’s URL jane.example.com to be serving the same content of example.com/folder/subdir1[/quote]
As an administrator, I want access to the entirety of the domain via one administrative (SFTP) login.
As a client user, I want access to only the contents of a subdirectory, which serves all the content for a subdomain.
The subdomain must be able to use relative paths to access files on the domain for authentication reasons. Specifically, for a script which displays a Twitter feed.
All of above is currently not possible with your one user per domain policy.
The client users in this scenario have a basic to intermediate level of expertise for the most part, but who have enjoyed FTP access to their specific subdirectories/subdomains for years without problems at our various previous hosts. Each is running a solo CMS from their subdir/subdom, and it would be inefficient to replace these multiple installations over multiple subdomains just for role management solutions.
As it is, my only solution seems to be placing the Twitter authentication files on each of their subdomains, giving them direct access to it, whereas if their subdomains could simply reference the domain for this, they wouldn’t need access to it – which is obviously much more secure. (And more efficient. If the auth data ever needs updating, I now need to update it on 9 subdomains in addition to the domain.)
I’m on VPS hosting, actually – having upgraded from shared hosting with another company which allowed this without issue – which is why this policy is even more ridiculous.
Every hosting company which supports a cPanel management interface allows this, and plenty of other proprietary backend hosting companies also allow this. This is the first time I’ve encountered such a policy.