Launch Checklist

Complete this checklist on the domain and infrastructure your team will actually use. Use a normal staff account for access checks as well as an administrator account.

Installation and infrastructure

• The intended domain resolves to the correct host.
• HTTPS serves a valid certificate and the canonical APP_URL matches.
• The application restarts successfully under its service manager.
• PostgreSQL is reachable and core migrations completed.
• Startup logs contain no module loading or migration failures.
• System Health shows the intended database, storage, license, and modules.
• WebSocket connections work through the proxy.
• Redis is configured for independent processes or the production workload that requires it.

Identity and access

• Company name, contact information, locale, and relevant defaults are correct.
• The initial administrator password has been changed where provisioned.
• Two-factor authentication and recovery information are configured as appropriate.
• Staff have individual accounts with the intended roles.
• A regular staff account can do its required work and cannot access unrelated administration.
• The organization retains access to the portal owner email and domain registrar.

Integrations and persistence

• Outgoing mail reaches an external inbox.
• A password-reset link points to the correct public URL and works.
• Provider callbacks and signatures are configured for this environment.
• Payment integrations have been tested before enabling live transactions.
• An uploaded test file survives an application restart.
• Multiple replicas share uploads or use a supported external provider.
• Cloud funding, sender verification, and spending controls are ready where used.

Recovery and operations

• A recent database and local-upload backup has been created.
• External files and environment configuration are backed up separately.
• A protected backup copy exists away from the application server.
• Someone is assigned to test restores, apply updates, and monitor logs.
• The current release archive and checksum are retained.
• Renewal dates and infrastructure responsibilities are recorded.
• Staff know where to find Documentation in the CMS and how to request support.

If a check fails, use troubleshooting before inviting users or depending on the affected integration.