Settings
Roles, privacy rules and portability. The owner holds final control over every gate in this control plane.
Portability guarantee
Lovable is a development tool only. This control plane exports to your own cloud; production credentials are configured after deployment in Google Secret Manager and are never embedded in the generated frontend.
Active role
Owner
Demo role switcher
Roles defined
9
Applications
7
Audit events
10
Roles & permissions
Owner has final control
| Role | Purpose | Approves deployment | Edits secret refs | Final control | Act as |
|---|---|---|---|---|---|
| Owner | Final control over every environment, connector and release. | yes | yes | owner | |
| Security Admin | Secret references, IAM plan, vendor access, emergency disconnect. | yes | yes | no | |
| Platform Admin | Cloud mappings, environments, deployment pipelines. | yes | no | no | |
| Developer | App factory specs, backlog, build jobs in dev only. | no | no | no | |
| Clinical Reviewer | Clinical accuracy sign-off on content and future EHR scaffolds. | no | no | no | |
| Policy Reviewer | Policy approval, crosswalks, accreditation evidence. | no | no | no | |
| Publishing Editor | Chapter workflow, QA gates, export and LMS jobs. | no | no | no | |
| Auditor | Read-only across audit logs, evidence binders and approvals. | no | no | no | |
| Read Only | View dashboards. No writes anywhere. | no | no | no |
Data classification policy
What may be stored where
- Public
Publishable outside the organization.
- Internal
Staff-only operational data.
- Confidential
Contracts, pricing, security design.
- PHI / PII Restricted
Requires explicit security + compliance approval before any deployment.
Privacy rules enforced by this build
Non-negotiable
- • No real employee records, PHI, private company records or production data — seeded demo data only.
- • No passwords, API keys, service-account JSON or access tokens in code, storage, logs or prompts.
- • Integrations store secret reference names only; values live in Google Secret Manager.
- • Short-lived credentials via Workload Identity Federation; no long-lived service-account keys.
- • Restricted-classification projects cannot deploy without explicit security and compliance approval.
- • EHR modules remain scaffolds until clinical, security, interoperability and compliance validation.
Export package
Take the control plane with you
The snapshot contains applications, connector metadata and the audit stream. Combine it with the deployment manifest from the Cloud center to stand the platform up in your own Google Cloud project.