Skip to main content

Deliver access data optimally for web projects

Providing credentials for web projects is a critical step that must be done securely and efficiently to ensure the smooth operation and maintenance of the website. In this guide you will learn how to optimally provide access data for a Joomla CMS, FTP and your web host.

CMS access for Joomla

To allow a developer or team access to your Joomla content management system (CMS), you must provide the following information:

  1. Username : Create a unique username that is easily identifiable (e.g. DeveloperName_Admin).
  2. Password : Generate a strong password. Use a combination of letters, numbers and special characters to increase security.
  3. User Group : Assign the user to the Super User group to grant full access to the CMS. This allows you to manage website content, extensions and settings.

FTP access

For FTP access, ideally SFTP (Secure File Transfer Protocol) for secure transfer, you need:

  1. Host : The address of the FTP server, often an IP address or a domain.
  2. Username : A unique username for FTP access.
  3. Password : A strong password used only for FTP access.
  4. Port : The port for SFTP is usually 22.

To increase security, ensure access is limited to only directories relevant to the project.

Web host access

Access to the web host is required to manage domain settings, email configurations and other hosting-related tasks. To do this you need:

  1. Login area : The URL to the login area of your web host.
  2. Credentials : Username and password to access the web hosting account.
  3. 2-factor authentication : If set up, ensure the developer or team has the necessary information or devices to confirm 2-factor authentication.

Providing access data securely

To ensure that all access data is transmitted securely, it is important to use secure transmission methods. Here are improved suggestions:

  • Password manager : Use a password manager to securely share credentials. These services allow you to securely share passwords with other users without them actually having to see the passwords.
  • Encrypted emails : If you need to send login details via email, you should use an email service with encryption functionality. This ensures that your messages are protected during transmission.
  • By telephone : Another secure method of transmitting credentials is a telephone call. This avoids the risk of sensitive information being intercepted in written form. Make sure you are speaking to the right person on the call before revealing any sensitive information.

Note that there is no physical record when sharing credentials over the phone, which can be both an advantage and a disadvantage. It is advisable to encourage the person receiving the credentials to store them securely and follow all standard security protocols, such as changing passwords regularly and using strong, unique password combinations.

Continue to avoid transmitting sensitive information over unsecured channels such as unencrypted email or text messages. After the credentials have been successfully submitted and confirmed by the recipient, you should review the access rights and ensure that only the necessary permissions have been granted. This helps ensure the security of your web projects.