<p>The server blocks creating a new account through GRANT when NO_AUTO_CREATE_USER mode is active or privileges are insufficient.</p>
<p>MySQL Error 1410: ER_CANT_CREATE_USER_WITH_GRANT appears when GRANT tries to create a user while NO_AUTO_CREATE_USER mode or privilege limits forbid it. Create the account first with CREATE USER or remove NO_AUTO_CREATE_USER to fix the issue.</p>
You are not allowed to create a user with GRANT
The error fires with SQLSTATE 42000 and message You are not allowed to create a user with GRANT. It means the GRANT statement attempted to create or modify a user account but the server currently disallows that implicit user creation.
Most commonly it happens when sql_mode includes NO_AUTO_CREATE_USER, which blocks GRANT from auto-creating accounts. It can also appear if you lack global CREATE USER privilege or if you append WITH GRANT OPTION to CREATE USER in versions that prohibit it.
The operation usually runs inside deployment scripts or CI pipelines. Leaving it unresolved halts role provisioning, breaks application startup, and can lock teams out of production databases. A fast remedy restores automated user management and application uptime.
See details in the next section.
Three proven methods exist: explicitly create the user first, remove NO_AUTO_CREATE_USER from sql_mode, or run the statement as a superuser with proper privileges. Choose the option that best matches your security policy.
Dev environments often inherit production sql_mode settings that include NO_AUTO_CREATE_USER, so local scripts fail. Continuous-deployment pipelines may also hit the error when they try to initialise fresh databases. The solutions below resolve both scenarios.
Always separate CREATE USER and GRANT statements in migration files, version-control sql_mode settings, and run privilege audits. Tools like Galaxy highlight sql_mode differences across environments, helping you prevent the mistake before deployment.
See the Related Errors section below for quick references to 1133, 1044, and 1142 issues.
When sql_mode contains NO_AUTO_CREATE_USER, MySQL blocks GRANT from auto-creating accounts, triggering Error 1410.
If the target account is missing, GRANT tries to create it implicitly and fails under restrictive modes.
Users need both CREATE USER and GRANT OPTION privileges to create or modify other accounts. Lacking either one raises the error.
Some administrators wrongly append WITH GRANT OPTION to CREATE USER, which MySQL does not allow and surfaces as Error 1410.
Occurs when you try to drop or alter a user that does not exist.
Raised when the current account lacks privilege to access the target database.
Shows up when a statement requires privileges not granted to the account.
It allows GRANT to create users implicitly, which can be convenient but may hide mistakes. Keep it disabled only if your process controls user names precisely.
Not safely in modern MySQL when NO_AUTO_CREATE_USER is active. Separate the statements for clarity and portability.
Your local server likely lacks NO_AUTO_CREATE_USER, while production enables it. Align sql_mode settings across environments.
Galaxy highlights sql_mode differences, suggests privilege fixes via its AI copilot, and lets teams version-control CREATE USER and GRANT scripts to avoid surprises.
.avif)
.avif){kind=logo}
