Is there a mechanism to attach a role to a user th...
# support-questions-legacyv
vishjain.
11/03/2022, 5:45 PMIs there a mechanism to attach a role to a user that hasn't yet signed up in Supertokens?
r
rp_st
11/03/2022, 5:45 PMhey @vishjain.
rp_st
11/03/2022, 5:46 PMyou can pass any unique ID to the user roles function and it will attach those roles to that ID
rp_st
11/03/2022, 5:46 PMeven if that ID does not exist in supertokens as a user
v
vishjain.
11/03/2022, 5:47 PMCool, I wanted the ability for creation of new users (emails) + roles in the supertokens database preferably but not physically create the user everywhere until the sign up is complete.
r
rp_st
11/03/2022, 5:48 PMI see.
rp_st
11/03/2022, 5:48 PMYou would still need some unique ID to attach a role
v
vishjain.
11/03/2022, 5:50 PMWhen the user actually signs up, I can avoid having a new id created for that user, right? Just want to make sure I'm not scrambling up any id's here.
r
rp_st
11/03/2022, 5:50 PMsupertokens will create an ID for that user, but then you can use the useridmapping recipe to associate that new ID with the older one you had, and everything should fall in place
v
vishjain.
11/03/2022, 5:52 PMGot it, so I'll create a random id and map it to a particular role and user email. Later when the user is signing up I can do some association
r
rp_st
11/03/2022, 5:53 PMyup
v
vishjain.
11/03/2022, 5:53 PM(sorry bit confusing, just want to make sure an admin in our dashboard only can let select people in an organization join)
r
rp_st
11/03/2022, 5:53 PMfair enough!
rp_st
11/03/2022, 5:53 PMfeel free to ask more questions 🙂
v
vishjain.
11/09/2022, 5:37 AMHey - quick question @rp_st on the thread here. Is storing a mapping of the randomly generated id to email possible in the user context (is that the purpose of usr context)?
vishjain.
11/09/2022, 5:37 AMOr is there another struct I can do this when attaching a role to a random role id before official sign up happens? Otherwise, I'll have to find my own way of persisting it
r
rp_st
11/09/2022, 5:43 AMYou can store the ID as cookies - would be the easiest way to handle this case i guess. And then this ID would be available during sign up request from the request cookies
v
vishjain.
11/09/2022, 5:47 AMWould prefer to store the id /cookie in the backend not in the browser, if possible, if there's some supertokens construct for me to associate made up user id with email
r
rp_st
11/09/2022, 5:48 AMyea, you can use the user metadata feature where the ID is the email, and the JSON associated with it contains the randomly generated ID.
And then on sign up, you can remove that metadata object once you create the actual user