This message was deleted.

@ripe-book-6760 I do agree that our permission scheme can be simpler, and we do aim to make it easier to parse. We’ll also be updating our documentation in the following months. In the meantime we’re happy to help with any specific questions you have. Some of the features you mentioned, like Customers, are from Stacker Classic, so I won’t deal with those at the moment. The newest version of Stacker has: • Roles • Permissions When it comes to users, it has: • Workspace users (collaborators) • App users Roles help you set different types of users. Within the roles, you set up basic access rights • Which pages can the role access? • Should the role be able to see and modify everything? You can then set different permissions for each table within an app. You can assign a permission scheme to one or multiple roles. Workspace users (collaborators) can add and edit apps, as well as manage the workspace. One workspace user will have access to all non-private apps by default. App users can only add and edit information within the app. You can have a different set of users for each app. Hope that clarifies the newest permission scheme at least a little bit. If you have any specific questions, I’m happy to answer them.

@elegant-eve-85294 This helps a lot. Thank you! I am using the new Stacker, however I still see the Customer Access feature within my App Settings. Should I avoid using that feature for now?

@ripe-book-6760 ah, it sounds like you are in that in-between state. We can turn off Customer access for you, or you can use that feature. If you keep the feature, the user model is slightly different then. I’ll follow up with you in a DM