Introduction

In this update, Magic introduces a new feature aimed at simplifying the onboarding process for users creating new workspaces with custom domains.

Previously, email verification was mandatory for every new workspace, requiring users to confirm their email addresses via a link sent to their inbox.

This process, although essential for security, sometimes caused inconvenience—emails landing in spam folders or not arriving at all. To address these issues, Magic has implemented a flexible setting allowing partners to disable email verification altogether, streamlining user access and improving user experience.

Key Details of the Update

1. Background and Motivation

• Previous process:
  Every new workspace and custom domain required email verification.
  Users received an email with a verification link, which they had to click to activate their account.

• Common issues reported:

  • Emails going to spam folders.

  • Users not receiving verification emails.

  • Frustration due to delays or missed emails.

• Goal of the update:
  To reduce friction during user onboarding by providing an option to bypass email verification.

2. New Settings for Email Verification

• Location of the setting:
  Accessible via the Partner Weather Label Settings in the main workspace.

• Steps to disable email verification:

  1. Navigate to Partner Settings.

  2. Scroll down to find the "Sign Up Email Verification" toggle.

  3. Disable the setting to turn off email verification.

• Effect of disabling:

  • Users who sign up can log in immediately after registration.

  • No need to check email or click verification links.

  • Simplifies onboarding, especially for small-scale or internal projects.

3. API Integration and Developer Control

• Availability in Partner API:
  The new feature is also accessible programmatically via the Partner API.

• How it works in API:

  • When creating a workspace through the API, there is a parameter to control email verification.

  • Parameter options:

    Parameter Name	Description	Values
    require_email_verification	Determines if email verification is needed	yes or no

• Implication:
  Developers can automate the process and set preferences dynamically based on their needs.

4. Impacts and Use Cases

Summary

This update offers a significant improvement in user onboarding flexibility, giving partners and developers more control over the verification process. By allowing the disabling of email verification both through the settings interface and the API, Magic empowers users to optimize their workflows and reduce onboarding friction. This change is especially beneficial for small teams, internal projects, or scenarios where email delivery is unreliable.

Magic emphasizes their commitment to listening to user feedback and continuously enhancing their platform to meet evolving needs. The new feature is a small but impactful step toward making workspace creation more seamless and user-friendly.

Final Thoughts

• Flexibility:
  The ability to toggle email verification on or off provides customization suited to various use cases.

• Ease of Use:
  The intuitive interface and API support make it simple for both non-technical users and developers to implement.

• Future Outlook:
  Magic is likely to continue refining onboarding processes, possibly adding more granular controls or additional customization options.

Summary Table: Key Points at a Glance

Closing Remarks

This update exemplifies Magic’s dedication to enhancing user experience through practical features that address real-world challenges. By providing more control over email verification, Magic ensures that partners can tailor their onboarding processes to best suit their operational needs, ultimately fostering a more efficient and user-friendly environment.