# Secrets on self-hosted QFieldCloud

**URL:** <https://community.qfield.org/t/secrets-on-self-hosted-qfieldcloud/466>\
**Category:** Ask the Community\
**Tags:** gh-import\
**Created:** [14 May 2025 02:23 UTC](https://community.qfield.org/t/secrets-on-self-hosted-qfieldcloud/466 "2025-05-14T02:23:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 02:23 UTC](https://community.qfield.org/t/secrets-on-self-hosted-qfieldcloud/466/1 "2025-05-14T02:23:36Z")

</div>

Hi all,

We are installing QFieldCloud on our own server. Our goal is to have a connection to a postgis layer.  
I saw that [here](https://docs.qfield.org/reference/qfieldcloud/secrets/) that QFieldCloud deals with a postgis connection using secrets.  
When connecting to my admin interface (port 8011), I see no way to add secrets. The interface is indeed different from the one shown in the screenshot in the qfieldcloud documentation:

 ![image](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/d0ddf752c4f66343e4453d726f5dd423a22a8996.png)

I am therefore wondering if there is a way to make a secure connection to a postgis layer on a self hosted QFieldCloud (I’d like to avoid writing the connection details in clear in the QGIS project file).

* * *

_Imported from [GitHub discussion](https://github.com/opengisch/qfield/discussions/4771) by @SolangeD on 2023-11-16T13:18:44Z_

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 02:23 UTC](https://community.qfield.org/t/secrets-on-self-hosted-qfieldcloud/466/2 "2025-05-14T02:23:37Z")

</div>

Secrets configuration is currently unavailble from Django Admin. It is in our backlog list, but no immediate plans to be integrated. If you are interested to speed up development of the Secrets UI in Django Admin, drop us an email at salesqfield.cloud .

* * *

_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4771#discussioncomment-7588712) by @suricactus on 2023-11-16T14:11:52Z_

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 02:23 UTC](https://community.qfield.org/t/secrets-on-self-hosted-qfieldcloud/466/3 "2025-05-14T02:23:38Z")

</div>

Can you guide me how to access this in the backend so I can add the service file?

* * *

_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4771#discussioncomment-8978095) by @Baptenda on 2024-04-02T01:20:35Z_

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex018/uploads/qfield/original/1X/7d3726da0ef5099a1e135505c03d2f125d527aae.png) [@system](https://community.qfield.org/u/system)\
**Post date:** [14 May 2025 02:23 UTC](https://community.qfield.org/t/secrets-on-self-hosted-qfieldcloud/466/4 "2025-05-14T02:23:40Z")

</div>

Note that secrets can now be added/modified through the admin panel with QFieldCloud version \>= 0.27.0

* * *

_Imported from [GitHub comment](https://github.com/opengisch/QField/discussions/4771#discussioncomment-9674969) by @boardend on 2024-06-05T08:08:33Z_