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.
The sort of login credentials you give your developer is determined on the task they must complete.
Make sure you’re just granting them access to the information they need.
This page describes the many levels of access you can give a developer, as well as the various login credentials associated with each option.
Your control panel is accessible.
The ability to access the web server
The database server is accessible.
Your website application’s access
You can simply grant Account Privileges to a developer that only requires access to your GreggHost panel.
Overview of Account Privileges
Account Privileges allow you to provide a single user access to specified pages in your panel. When they no longer require access, make sure you deactivate the Account Privileges.
What are the steps for adding or removing account privileges?
Server access to the website
GreggHost enforces a one-user-per-domain policy for security reasons. This ensures that a domain on the server can only be accessed by a single username.
This implies that in order for the developer to access into the server and work on your site, you must provide the developer with the username and password details of your website user.
Before handing over your website credentials, make sure you trust your developer!!!
Sharing GreggPress login credentials
GreggPress websites are not covered by the guidelines below. This is due to the fact that a GreggPress site’s username cannot be changed. If you require a developer to work on your GreggPress site, make sure your Shell username password is up to date first.
Password should be changed (Website users)
Once the developer has completed their job, change the password to guarantee that only you have access.
Before you go any further, double-check that your website’s code does not include any absolute file paths that involve your username. They’d look somewhat like this:
If this is the case, you’ll need to change those references both when the website moves to the new developer username and when it flips back to the original username. Otherwise, your website will not work properly.
Create a new user for the developer on the server first.
The process of adding a user to a service
Make the necessary changes to your website to reflect the new username. Make sure the option to copy files to the new user is selected.
Changing a domain’s allocated user
You can share the new credentials with your website developer after the website is operational under the new username.
Change the username back to your original username once the website developer is completed with their task. This ensures that only you have access to your site once more.
Finally, delete the developer user you established.
Delete a website user and all of their information
Your website’s database may also be needed by a developer. For the developer, you should always create a new database user.
Adding and removing users from a database
When the developer no longer requires access, make sure to delete the user.
WordPress (or another CMS)
Content Management System (CMS) software, such as WordPress (or another CMS), allows you to download a program and construct a website on top of it. Here are several examples:
WordPress (or another CMS)
If your developer simply needs to work on this type of site, they may only need the software program’s login credentials, not the user’s credentials needed to get into the server. For more information, click on the following links:
Users of the website and the application
In this situation, you’d just create a new user for the developer in your CMS. This article, for example, describes how to add a user to WordPress:
How do I add a user to WordPress?
When the developer no longer requires access, make sure to delete the new user.