Improved email change experience

The dashboard now explains each step of the email change flow with clearer pending, success, and error messages.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

We improved the email change experience in the dashboard settings.

Changing an account email has two verification steps: first, approving the change from the current email address, and then verifying the new email address. Previously, the flow could feel unclear because approving the first email returned you to the settings page without enough context.

Now the dashboard shows the current state directly around the email field. After the first approval, it highlights the email field and explains that the verification email has been sent to the new address. If a verification link expires or cannot be used, the dashboard shows a clear error dialog instead of silently returning to settings. Once the new email is verified, the dashboard confirms that the email address has been changed successfully.

Email change verification pending state

This should make the flow easier to follow and reduce support requests from customers who are not sure whether the first approval finished the email change or whether another verification step is still required.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
Async, Webhooks, and Extra Limits

Async, Webhooks, and Extra Limits

May was a great month and full of new and exciting updates. Let's check them out quickly.

Read more

1 min read

Add ScreenshotOne to n8n workflows

Add ScreenshotOne to n8n workflows

You can now use ScreenshotOne in n8n workflows to render website screenshots, PDFs, scrolling screenshots and videos.

Read more

1 min read

Improving performance and stability by consolidating validation and access check logic in the API gateway

Improving performance and stability by consolidating validation and access check logic in the API gateway

For the past few days, I have been working on improving the stability and performance of the ScreenshotOne API. I started from low-hanging fruits—moving validations and access key management from rendering services to ScreenshotOne's API gateway. The API will be more stable and performant as a result. If you are curious why, please continue reading.

Read more

2 min read

Automate website screenshots

Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.