# Supabase signup process in one command or several commands

**URL:** <https://community.weweb.io/t/supabase-signup-process-in-one-command-or-several-commands/15484>\
**Category:** How do I?\
**Tags:** authentication, supabase\
**Created:** [January 21, 2025, 6:26am UTC](https://community.weweb.io/t/supabase-signup-process-in-one-command-or-several-commands/15484 "2025-01-21T06:26:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kdjamo](https://avatars.discourse-cdn.com/v4/letter/k/45deac/32.png) [@kdjamo](https://community.weweb.io/u/kdjamo)\
**Post date:** [January 21, 2025, 6:26am UTC](https://community.weweb.io/t/supabase-signup-process-in-one-command-or-several-commands/15484/1 "2025-01-21T06:26:23Z")

</div>

Hi,

I’m setting up a user signup process and found @Joyce videos on onboarding and using a separate table in the Supabase public schema very helpful.

I’d like to collect additional info at signup (e.g., name, country, timezone) and store it in selected public tables while enrolling the user. Joyce suggests adding JSON to the `raw_user_meta_data` field, but I’m concerned the trigger/function to transfer data from the auth table to public tables might fail without flagging an issue in WeWeb.

Is it recommended to use a single signup transaction using the `raw_user_meta_data` field and triggers, or splitting it into several workflow commands to send all the data to the required supabase tables?

Thanks!

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [January 21, 2025, 7:40am UTC](https://community.weweb.io/t/supabase-signup-process-in-one-command-or-several-commands/15484/2 "2025-01-21T07:40:50Z")

</div>

It’s the same thing. Just make sure to test it properly 🙂 Both options are viable.