Add admin page

[neatonk]

\/admin\/users → Admin page for user management. (1 day)

• [x] [Provided by supabase dashboard] User account listing, including email address, user name, ~account type~ and last login date.
• [x] Account types include admin, user ~and collaborator~.
  • [x] [Provided by supabase auth] Admin accounts can do anything and are intended for MESA employees.
  • [x] [Provided by supabase auth] User accounts are for normal users and can be used to manage projects and add collaborators.
  • [x] ~Collaborator accounts can only be used to collaborate on projects they've been added to.~
• [x] [Provided by supabase dashboard] Button to add a new user account by email address and account type.
  • [x] ~Add a new account of the specified type for the given email address.~
  • [x] Send an email invite link to the email address.
• [x] ~Option to upgrade collaborator account to normal user account.~

[neatonk]

Much of this functionality is provided by the supabase auth control panel.

[neatonk]

One option is to implement collaborator-only accounts account metadata:

• Add collaborator: true or similar to metadata when creating a new collaborator account.
• Remove collaborator: true or similar from metadata to remove upgrade to normal user.

An alternative would be to implement collaborator accounts using a separate table

[neatonk]

Add a new account of the specified type for the given email address. Send an email invite link to the email address.

In my testing, this is not very smooth yet. It may be necessary to update the email templates to avoid the implicit auth flow and/or support the implicit auth flow in the client. By default the invite and confirmation emails redirect back to the app with something like this, which we do not currently handle:

https://mesa-wallet.vercel.app/en#access_token=<TOKEN_HASH>&expires_at=1698556517&expires_in=3600&refresh_token=<REFRESH_TOKEN>&token_type=bearer&type=invite

See https://supabase.com/docs/guides/auth/server-side/email-based-auth-with-pkce-flow-for-ssr#update-email-templates-with-url-for-api-endpoint, for example.

[neatonk]

Closing in favor of using the Supabase auth dashboard to manage users. As discussed on our call today, signups will be open to all and there will be no restricted collaborator role. See #32