This message was deleted.

Yes, the latest version only allows single table for user. It's extremely confusing since there seen to be different versions now, Stacker classic, Stacker X and new version for some features in Stacker X. 🤷🏽‍♀️

Yes it is very confusing! Especially as I changed my whole data design to work around multiple user tables! What I'm hoping is the plan is to reintroduce multiple tables (fingers crossed), and if that is the case what the timelines might be.

Hey @happy-easter-55311 @millions-army-64326 @happy-easter-55311 Thanks for expressing your concerns so clearly. I’ll try to address all of them, but please call me out if I miss any. User model - latest version The latest user model is based on roles and permissions, and works from a single table. The idea is that you have a field that defines the user’s role. You can then set a conditional automatic role assignment based on that field. I’ve attached the screenshot to show what it looks like. Multiple user tables Looking at the feedback we get from customers, it seems clear that you folks like the ability to have multiple user tables. We believe that the new system should make things better and easier without multiple tables, and that (in the near future) you should be able to do pretty much most of the things that you could until now. Having said that, I would love to understand why you feel having multiple user tables is useful to you, as opposed to having one table with role assignments. Multiple versions of the app I completely understand where you’re coming from. We’re working hard to make a model that will be definite and one you can rely on for years to come. It will take us a bit to get to that point, but I believe it will be worth it. As we build solid migration tools, we will get in touch about app upgrades—you can use your apps as they are until then. As your apps make the switch to newer models, we in the support and success teams are happy to help you navigate through any changes, and come up with solutions that will work for you. I realize some transitions might not be as seamless as we all would want, but you will not be left in the dark to figure things out on your own.

@elegant-eve-85294 Thanks for the very clear answer, it’s much appreciated.

@happy-easter-55311 thanks for sharing your use case, and for giving me candid feedback. In the future you should not need to have such a convoluted user setup, but I don’t have exact details for you just yet. As for the lack of clear communication, we hear you, and we’re working on it. This is by no means an excuse, but clear communication and feedback require quite a bit of effort and preparation. As we hire more people, this will become easier because the workload will be spread across the team. An example of these efforts is a post from our (wonderful) @gorgeous-queen-48490: https://stacker-customers.slack.com/archives/CMZK26G76/p1638959820068300 While I can’t promise every single thing you suggest will be implemented, I can assure you that it will be heard and considered.

Thank you @happy-easter-55311 for all your feedback – I definitely echo @elegant-eve-85294's sentiments here. When we revisit the model it would be really great to have a conversation about it, plus ask you and other customers to have a look at some designs and prototypes. We definitely want you to be part of the conversation!

Excellent, thanks both, I appreciate the response :) And I don’t want to sound overly negative, I think you guys are doing a great job and overall the product is fantastic so keep up the good work!

Hi @happy-easter-55311, I'm Sze Wing, a Product Manager at Stacker. Are you keen on jump on a call with me later this week or next week to discuss how Stacker X has been for you - as someone who used to use Classic? You can book a call with me here - https://calendly.com/szewing/30min-1?month=2022-02 🙂