-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
publicMetadata
does not update within the member list object, it is always empty.
#1944
Comments
Hey @pavittarx, seems like you are expecting to read from a OrganizationMembership's publicMetadata but you are populating a User's publicMetadata |
Any update on this issue? I have been told by the Clerk sales team that in order to avoid purchasing the 'Enhanced B2B SaaS add-on', which gives me custom roles and permissions, I can instead build it myself by storing a users role in their public metadata. However the following two options do not work:
Edit: How do I go about raising this as an issue with the core API? |
As a workaround, we had to pass each member's |
Preliminary Checks
I have reviewed the documentation: https://clerk.com/docs
I have searched for existing issues: https://github.com/clerkinc/javascript/issues
I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.
Reproduction / Replay Link
https://replit.com/@PavittarSingh1/ClerkBackendAPI-1
Publishable key
pk_test_aGVscGluZy1qYWd1YXItODguY2xlcmsuYWNjb3VudHMuZGV2JA
Description
Steps to reproduce:
publicMetadata
for any user.Expected behavior:
the member within the organization member list should have their publicMetadata updated.
Actual behavior:
publicMetadata
is updated and correct when fetching individual user data.publicMetadata
is empty inorganizationMembersList
Environment
The text was updated successfully, but these errors were encountered: