Talk to our team

Documentation

✉️ Email Delivery

Documentation, reference material and tutorials for CRM-NG SMTP Email: setup guides for every mail service, troubleshooting, and one article per error message.

Error: Authenticated user not authorized to send (SendGrid)

Updated

By Duane GarnerChief Executive Officer (CEO)
Summarize: Claude ChatGPT View Markdown
On this page

SendGrid knows your API key but will not let it send mail. The key lacks Mail Send permission or the account is restricted.

This article is for sites using the SendGrid mailer where a send fails with "The authenticated user is not authorized to send mail" (or a similar "not authorized to send" message).

The error as you see it

authenticated user is not authorized to send mail

Shown by the SendGrid mailer, in the failed-send banner, in Tools → Debug Events and in the Email Log. SendGrid returns it with HTTP status 401 or 403.

What this error means

The API key is real, so SendGrid knows who is asking. But the key, or the account behind it, is not allowed to send email right now. That is either a permissions question (what the key may do) or an account question (whether the account may send at all).

Common causes

  • The API key has no Mail Send permission. A Restricted Access key created for reading statistics, or with Mail Send left at No Access, cannot send.
  • The account is under review or suspended. New accounts are sometimes checked before they may send, and SendGrid can pause accounts with high bounce or spam rates.
  • The account has used up its sending allowance for the day or month on its current plan.
  • The key belongs to a subuser that was disabled or lost its sending rights.
  • Two-factor sign-in was never set up on the account. SendGrid requires it for accounts, and an account without it can be limited.

How to fix

  1. Check the key's permissions

    Sign in to https://app.sendgrid.com/ and go to Settings → API Keys. Open the menu for the key your site uses and choose Edit API Key. Under Access Details, set Mail Send to Full Access and save. You do not need to change the key in WordPress after editing permissions.

  2. Or make a fresh key

    If you cannot find the key, choose Create API Key with Restricted Access and Mail Send at full access. Copy it, then in CRM-NG SMTP → Settings → General use Remove API Key, paste it into API Key, and press Save Settings.

  3. Check account status

    Look for a banner at the top of the SendGrid dashboard, and check your email for messages from SendGrid support about a review or suspension. Answer any review request; sending resumes only after SendGrid clears the account.

  4. Check usage

    Open your account's plan or usage page (in the account menu) and see whether you have reached your sending limit for the period.

  5. Check subusers

    If the key belongs to a subuser, the parent account can see under Settings → Subuser Management whether that subuser is active.

  6. Send a test

    Go to CRM-NG SMTP → Tools → Email Test, fill in Send To and press Send Email.

Verify it worked

The test page shows "Test email sent successfully! Check your inbox to confirm delivery." and the message appears in SendGrid's Activity Feed.

Notes

  • Restricted keys with only Mail Send are the safest choice: if the key ever leaks, it cannot change your SendGrid account.
  • If SendGrid instead says the authorization grant is invalid, the key itself is unknown. See Authorization grant invalid or expired.
  • Repeated limit errors mean the site sends more than the plan allows; see Email sending limit reached.
Go to Top