convex-better-auth-user-management

To manually update Better Auth user data in Convex, export the data to JSONL using the Convex CLI, modify the records locally, and reimport the file with the replace flag to apply changes without writing app mutations.

Yes, you can bypass email verification for Better Auth users during local development by exporting the user table to JSONL, setting the emailVerified field to true for the target user, and reimporting the data back into the Convex component tables.

The best way to view and audit Better Auth session and account data in Convex is by running the Convex CLI data command with the betterAuth component specified, allowing you to inspect records directly without modifying application code.

No, updating Better Auth user records through the Convex CLI does not require changes to app mutations, because you can directly export, locally edit, and reimport the JSONL data into the component tables using CLI commands.

You need to export and reimport Better Auth data from Convex when debugging login issues or testing development flows, as it allows you to manually review, adjust, and apply changes to user, session, and account records safely.

Adjusting Better Auth user data directly in Convex component tables is intended for development and debugging scenarios, meaning manual modifications to user, session, or account records should be carefully managed to avoid unintended data inconsistencies.