I'm reaching out for guidance on setting up a solution in Retool that allows us to connect to our API using user-specific tokens. Each user will require specific variables that are not visible to other users. I explored configuration variables, but they don't appear to be user-specific.
Could you please advise on the best approach to achieve this within Retool?
Hi @Anastazie_Sedlakova ,
Thanks for reaching out! Would adding metadata to the current_user object work for your use case? You can read more about that here.
Thank you. Are these metadata visible to other users?
Metadata is only available on Business and higher. Unfortunately, I don't think this will be possible on Freetool.
To add metadata to a user in Retool, go to Settings > User attributes, where you can create custom fields with names, labels, and data types to store extra user info. This effectively adds metadata to each user profile, which you can access in your Retool apps by referencing the current_user object.
With business or higher you can also set permissions and create groups for users to control who has access to what.
Something else that may be useful and is included in Freetool is localStorage. Here's our doc on how to set localStorage up. Let me know if this helps!
Would this be the same if my use case is that the response for my login query has a sessionId that I want to set as a variable, so I can call that variable as the value of a key in the body of another query in my app?
Thanks for reaching out. What do you mean by login query? Are you logging in to an api resource and then using the sessionId in another query to the same resource? If so, I recommend setting up custom authentication