Self-hosted QFieldCloud: best practice to manage organization-level secrets for all projects?

[JLHI_JLHI]

Hi,

I’m currently running a self-hosted QFieldCloud instance (Docker setup) and I’m trying to understand the best way to manage secrets across multiple projects.

From the documentation, I understand that QFieldCloud supports organization-level secrets, which should be available to all projects as a fallback.

However, in a self-hosted setup:

• I don’t see a way to manage secrets via the admin/UI

• It’s unclear how organization-level secrets are supposed to be configured

• I haven’t found clear examples for this use case

My goal

I would like to:

• Define a default PostgreSQL connection (or pg_service) once

• Make it available automatically to all projects

• Avoid configuring secrets individually per project

What I tried

• Looking for secrets configuration in Django admin → not available

• Reviewing documentation → mostly refers to QFieldCloud SaaS

• Considering configuring credentials directly in the QGIS Docker container (pg_service.conf, env vars, etc.)

My questions

1. Is there a supported way to configure organization-level secrets in self-hosted QFieldCloud?

2. Are these secrets expected to be set via:

   • database?

   • environment variables?

   • API only?

Any feedback or real-world setup examples would be greatly appreciated

Thanks!

[fggs-pascal]

What QFC version are you on? I never used organization-level secrets, but we have a Secrets tab in the organization settings (I believe we are around version 26.3).