clock Last Modified: Jul 16, 2018

Site access on Presslabs

Let us introduce you to your site’s access map! See how you can access your site’s files directly in our Presslabs dashboard, e.g. your code repository, database and media files, along with secure wp-admin access.

This section is meant to give you information about the way you can access your site’s files. There are multiple ways to access your site and you’ll find them described below.

1. Gitea access

We have designed a new, simple, and straightforward web app based on Gitea, allowing you to easily manage your site’s source code. Find out more in our Gitea tutorial.

To sign in, simply access the link and enter your Presslabs Dashboard credentials.

This link can be seen in our Dashboard, on Sites -> Access -> Git.

Access your site's code in Gitea
info Access your site's code in Gitea

From here you can easily get the clone URL’s in order to clone your code locally:

  • HTTPS url:<site_owner>/<instance_name>.git
  • SSH url:<site_owner>/<instance_name>.git

2. Git Access

The recommended way for accessing your site’s code (themes, plugins, and the files from the root of your site) is by using Git.

To clone your code locally, you can get the Git clone URLs from our Gitea interface as shown above, or from the Access section of the Presslabs Dashboard:

Details for accessing your code via git on the Presslabs Dashboard
info Details for accessing your code via git on the Presslabs Dashboard

You have two options for cloning your code:

  • via HTTPS: this is the recommended way, as you can simply clone your source code using your Presslabs Dashbord credentials

    git clone<site_owner>/<instance_name>.git
  • via SSH: to clone your code via SSH, you need to have a SSH key configured on your Presslabs Dashboard

    git clone<site_owner>/<instance_name>.git

3. wp-admin Access

Our support team has, by default, secured access to your site’s wp-admin. While the support account needs to have a password, which is randomly generated from 64 characters, we don’t use a password to connect, but a secured token that is only active for a limited amount of time. If for any reason, you don’t want to give access to our support team to your site’s wp-admin, you can drop us an email to Please note that without wp-admin access, we might not be able to offer you a proper support.

4. Database access

We’re not allowing direct DB access using phpMyAdmin, or other similar tools because of security reasons. We, therefore, recommend using the needed DB operations by following our development guidelines. If that’s not possible, please submit a support request and we’ll gladly help you out with those operations.

You can request a database snapshot from our dashboard, in the Snapshots section.

5. Media Files access

To access the uploads folder, we recommend using the plugin File Manager, which allows you to easily manage your media files and folders.

Access your media files through the File Manager plugin
info Access your media files through the File Manager plugin

6. Collaborator access

In case you need to give access to one or more developers to your site’s code, there are 2 alternatives:

  • You can add their public SSH Key in the SSH Keys menu from the Presslabs Dashboard. In this way, they’ll be granted Git access to all the sites from your account.
  • You can add them as a collaborator to the site in question, either from the Presslabs Dashboard, or from the Gitea interface, in the Collaboration section:
Give access to collaborators through Gitea
info Give access to collaborators through Gitea

You can notice you already have a collaborator in your Gitea account, the Oxygen Bot, which we use to have access to your site’s code.

You can only add someone with a Presslabs Dashboard account. If you want to add a developer that does not have a such an account, you can send him an invitation via email from our Dashboard.


I have a new developer on board, how can I give him access to a single site?

You can grant him acccess to a single site from our Gitea interface at Go to your repository’s settings, in the Collaboration tab, and enter your developer’s username, along with the rights you wish to grant him, more details can be found in our Access section.