# Use the WordPress database and admin access

> Find built-in WordPress credentials, open WP Admin or phpMyAdmin, and rotate the database password safely.

Every managed WordPress site includes a built-in database. AppLaunch creates and configures it during site provisioning.

## Find the connection details

Open the site and select **Database**. The page shows:

- Built-in database name and username.
- Database password when available.
- Internal host and port for code running inside the WordPress container.
- External host and port for tools running on your own computer.
- WP Admin user information.

Use the internal values from WordPress itself. Use external values only from an external MySQL client. Copy values exactly; managed names may contain prefixes.

## Open WP Admin

Under **WordPress Access**, click **Open WP Admin**, or visit `https://YOUR-DOMAIN/wp-admin`. Use the WordPress administrator credential, not the MySQL user or your AppLaunch password.

## Open phpMyAdmin

Click **Open phpMyAdmin** and sign in with the built-in database credentials shown on the same page. phpMyAdmin directly changes production data. Export affected tables before bulk updates, and never run a query copied from an untrusted source.

## Rotate the database password

1. Create a completed backup.
2. Open **Database → Built-in Database**.
3. Choose the password rotation action and confirm.
4. Save the new password immediately.
5. Wait for the operation to finish.
6. Confirm both the public site and `/wp-admin` load.

AppLaunch updates the managed WordPress configuration as part of its supported rotation flow. Any external script or saved database client using the old password must be updated separately.

## Avoid common mistakes

- Do not change `siteurl` or `home` directly unless you understand the domain migration effect.
- Do not delete WordPress option, user, or post metadata rows to solve a display problem.
- Do not expose the external database port or credentials in public code.
- Do not share a database export without removing personal data and secrets.

Use [WordPress backups and logs](/wordpress/backups-and-logs/) before risky changes.
