Apache Superset Multi-Tenant Setup

I need Apache Superset installed, configured, and secured so that it can serve multiple tenants from a single server. All of our data lives in PostgreSQL and every tenant already has its own separate database on that server. When a user signs in, they must see only their database in Superset, be able to explore data, write SQL, and build dashboards with full read-and-write rights—but never touch anyone else’s data.

You will take the project from a clean install through to production-ready status. That means handling the Superset installation itself, setting up the PostgreSQL connections, mapping each user to the correct database, and putting simple role-based rules or row-level security in place so our compliance team is satisfied that there is no cross-tenant leakage.

Please include a brief outline of the approach you plan to use (native database-level permissions, Superset database-per-user mapping, environment variables, etc.) and any prerequisites you will need from me. At hand-off I expect:

• A working Superset instance reachable via the browser.
• One demo user linked to one demo database as proof of concept.
• A short document or script that shows how to add future users/databases following the same pattern.

I am ready to provision server access as soon as we agree on the plan.