Create the website under its account
Select the intended active account, then use the website workflow to choose its primary domain, aliases, static/PHP mode and relative document root. Supply complete lower-case names without schemes or ports.
Use only the PHP versions actually reported by the installed capability response. The current qualification records review PHP 8.3; this is not a promise of arbitrary version switching. Apache compatibility is a separate per-site option for supported rewrite behaviour, not a reason to assume Nginx interprets .htaccess.
Review the resulting operation and local health before testing external access. DNS and SSL begin as separate pending states; a successful loopback website response does not mean public routing or trusted HTTPS is ready.
Manage files and data deliberately
Website workspaces expose authorised modules such as Files, Database, PHP, Email, SSL, Backups, Logs and Applications according to installed capability. A missing registration must stay unavailable rather than being treated as a healthy service.
Customer MariaDB is distinct from the panel's private PostgreSQL metadata. Create databases and users in the correct account and retain application credentials privately. Do not grant a website access to panel metadata or assume a database export contains its users/grants/passwords.
Before changing website domains with managed HTTPS, follow the release's certificate-state and ownership checks. Keep the original operation and resource references when investigating interrupted changes.