Tom Hopcraft Awesome! Thank you sir! Please also see my note on the 2FA feature; as these two features are related.

Tom Hopcraft Any update on the status of being able to restrict certain views to certain users? I have fulfillment team members I want to get onboarded. And I'd also need to enforce 2FA on them, as per company policy (which is another feature I've requested previously). As you know, I find Setary tremendously useful, but I'll be forced to look for an alternative solution 😢 if I can't onboard my team in the required manner.

James Joseph Finn 2FA can roll out very soon. With regards to restricting VIEWS per user, I don't think this will be possible due to the VIEWS just being pre-defined filters, so this would mean a user can just change the filter/columns theirselves. How would you actually like to lock it down? What are you specifically hiding to team members?

Tom Hopcraft Thanks so much for the fast reply! That's great news about 2FA. As a related question, I'm not seeing in the UI how to add and manage team members (although, as mentioned, I've currently no desire to do so absent the ability to enforce 2FA, and also restrict their access to certain views / columns).

I have two solid use cases for "views / columns user permissions"; which, if implemented (and Setary already has the perfect foundation in place), would uniquely position Setary as having a simple and elegant "spreadsheet based" solution to team / user capability / permission management; that is fully decoupled from WP admin! This is evidently desirable because of how notoriously unpleasant it is to wrangle perms inside the admin area.

The first use case is for my fulfillment team. I would like to grant them access to only certain columns (such as stock status, price, sale price, and the like); and obviously also be able to restrict their access to anything outside of their scope of responsibility.

In like manner, my second use case is for content creators. For them, the only columns they would need access to are short and long descriptions; and all other columns should be similarly inaccessible.

Lastly, I'll reiterate a word of gratitude: After playing around with the new "Views" feature, I have found it to be very useful indeed. Thank you again for not only being receptive to feedback, but also for implementing it! Peace.

Tom Hopcraft Thank you sir. I can't imagine any of your users, if the functionality were made available, as not making use of more granular capabilities management.

We're a very small store, and even we would benefit from being able to restrict and grant access to woo fields on a per-user basis.

In addition to the "stock manager" use-case already mentioned, another use-case is a copywriter, who could be given access to only description and short-description.

Permit me one last pitch on this idea: Any time an admin can find a way to grant someone access to store data without having them log in to WP-Admin, that's a win. Perms management in WP has always been a pain; and since your app interfaces with product data, providing a way to manage perms can greatly expand the use cases for your app beyond mere admin purposes.

Thank you again.

James Joseph Finn I do like this granular permissions idea. Let us get “Teams” launched and we will revisit this. Thanks for the eloquent response.