This message was deleted.
# questions
b
This message was deleted.
๐Ÿ‘€ 1
f
Hi Ruchika, We have phased out customer access in the new user model, please have a read through the docs - https://help.stackerhq.com/fundamentals/workspace-users/app-users
m
@freezing-car-89097 when did this happen๐Ÿ˜… it still works in my other apps
f
Recently, hence you have both. Sorry about that, there should have been an update to let you know!
r
@freezing-car-89097 Is the changelog getting updated with these changes? I wasn't aware either, but it looks like the last update to that was the 15th. We rely on that for changes, but I've noticed there are a number of things that have changed and are not reflected there.
โž• 1
d
@freezing-car-89097 I just build and about to launch a new app with customer access, should I hold off and update to v2.0? What are the advantages to v2.0?
r
Yeah, I was just reading through the docs as well and not sure how this works with roles. For example, our apps haven't launched yet as we are still building but reliant on the default Admin and then User role that came with Customer Access (that's all we needed), if that is changing and no longer available, then moving to the plan with roles is too expensive for us and we'll have to scrap the months of work so far.
@gorgeous-queen-48490 Would you be able to assist with this Customer Access user change as well? It's all a little unclear what's happening here and how the changes affect folks, what abilities they bring, how they affect the default Admin/User role, and what the process is to getting to v2? Since the roadmap doesn't appear to be updated with recent changes, it's unclear what's happening with Stacker at this time. Thank you!
โ˜๏ธ 1
m
@freezing-car-89097 uh oh .. there really needs to be better communication on the changes. How does this impact the existing apps? How different is it from the earlier user setup? It seems quite different, especially the fact that there can't be two different user tables๐Ÿค” I've pitched Stacker to a new client with some of these assumptions.
@gorgeous-queen-48490 +100 to all that @ripe-manchester-80360 raised. This is very concerning.
โ˜๏ธ 1
@freezing-car-89097 I have followed the steps as in the link you shared, however, I don't see any users in the list, even though there are users in the Airtable table.
c
@freezing-car-89097 Im with @millions-army-64326 Stacker need to up their game on production change tracking & Comms. Let me be super clear on the implications of this: if stacker release changes into production like this that either break our apps or introduce significant delays to building solutions (as we have to learn new stuff before we are ready), then the value prop of using Stacker will be off and we will start moving to a platform exit strategy rather then our current platform onboarding strategy. ie we will migrate back onto simple hand built react apps. No hard feelings, we have a small team of seniors and donโ€™t have the capacity for dealing with poor version/release management. In this case we already migrated to using V2. And it was painful. But its in the back mirror. However I still find stacker comms and versioning sub-par. Most other Saas platforms have a changes update in the app that tells you what has happened that you need to be aware of. Minor changes are just in a notification feed and Major are in the notifications feed and in a Modal when you login next time. Something like this is absolutely necessary for any kind of software tool.
s
I'm in the middle of my transition to the new Stacker from Stacker Classic, and am having a very difficult time working through all the changes. Now I'm not even sure if I'm on Version 1.0 or Version 2.0. Was Stacker Classic Version 1.0, or have I missed a whole step? I love all of the new features that have been added recently, and still see huge potential for this platform, but agree 100% with the others that are finding it hard to figure out what has all changed, and how it impacts our current apps versus new apps, etc. To make it worse, some of the support materials refer back to the old version, while others refer to the new version. Now we're talking about Version 2.0 instead of Stacker X and I'm not even sure when Version 2.0 came about, what that means for the app I'm building, how I go about inviting app users, how app users differ from workplace users, etc. I'm going to continue trying to work this out, but I have to say, what was once a very easy platform to build with and navigate has become 5x more difficult to use in the past year.
Regarding the app users link and "Customer Access", does this mean that I now have to take an additional step to remove access for a user beyond removing them from my Airtable base? If so, that's not ideal, especially given the lack of access in Airtable to information about who has registered with my Stacker portal.
h
Looks like V2 has some advantages but Iโ€™m also right in the middle of build a new app on Stacker X (currently using Classic) so now not sure exactly what I should be doing, especially as took me ages to get my head round all the customer access stuff ๐Ÿ˜œ
f
Hi All, Thank you so much for the feedback here. There definitely needs to be more updates on features that are being released, I will be passing all this feedback onto the team.ย  With regards to customer access and the new user model - If you have set up customer access and are happy with this then it will remain as it is, we are not forcing the new user model. However if you do want to trial it let me know, I can get that enabled for you. @clever-art-10420 - Changes update in the platform would be great and something we would like to work towards.ย  @stale-judge-11647 - If you still need additional help with your setup, please contact support and we can set up a call to help you set up. @millions-army-64326 - I have replied to your query on the issue raised through support. If you do have any further questions, please email support@stackerhq.com or DM me!
๐Ÿ‘ 1