Overview

A single FTP/SFTP/SHELL user can own each domain you host with GreggHost. This page discusses how to configure this on the server, as well as how to change a user’s domain.

How users and domains are assigned to each other
In your control panel, you can create a website user who can access several domains. This is illustrated in the graphic below:

00.png 00.png 00.png 00.png
Resellers and web developers who manage several domains will benefit from this setting.

However, you cannot assign many users to a single domain, hence the inverse is not possible:

1user 03.png 1user 03.png 1user 03.png 1
When you add a second website user, they can only see their own home directory and the files and folders included within it. They won’t be able to access the website files if they log in as someone else.

1user01.png is a picture of a single user.
Changing the website user to which a domain is assigned
At any moment, you can alter the user to whom a domain is allocated.

Go to the Manage Domains section.
Under the Web Hosting column, click the Edit option to the right of the domain.
Scroll down to the Users, Files, and Paths area on the next page, as illustrated in the following:
relocate the user
Choose another current user or ‘Create a New user’ to create a new username on your server from the Run this domain under this user selection.
At this point, you have the option of moving all files to the new user. Check the box next to ‘Migrate files to the new user?’ if you want to move all of your website files.

To save your changes, scroll down and click the Change settings button.
Depending on how much data the original user needs to copy to the new user, migrating the data to the user takes longer.

The DNS must propagate before the site resolves online to the new user and servername if the new username is on a separate server.

Verify the domain is resolving from the new username
To make sure the site is responding from the new account, follow these steps.

Go to the webpage and load it.
Use SFTP or SSH to connect to your server.
Go to the following document. /home/username/logs/example.com/http/access.log /home/username/logs/example.com/http/access.log /home/username/logs/example.com/http/access.log /home/username/logs/example.
Check for current entries by opening this file.
Naming your website user
It’s best to offer a new website user a generic name like ‘Domain Admin’ when creating one that will be used by numerous persons.

Example
You need to create a user for your company’s website, and this FTP user login will be used by various people.

You wouldn’t want to give your User Account a name like Bob Smith.
Use a more domain/company-centric moniker, such as Domainname Admin, instead.
Allowing developer access to your site
It may become necessary to engage a developer to work on your website at some point. A developer may need access to your site in a variety of ways in order to work on it. The level of access you give a developer is determined by the tools they’ll need to finish the work you hired them for.

For more details on how to provide your developer only the access they need, see the following article.

Providing developers with access to your website