Hi, I’m on a Publisher Pro plan and have not used Security Filters before as they previously required user sign-in, which we don’t need as we have no sensitive data. However, I noticed that it is now possible (maybe it always was?) to enter a security filter without enabling user sign-in, by using a UserSettings parameter which defines a class of user.
So, I have set up a simple security filter of UserSetting(Name)=[Name] on one table, reduce 1400 rows of data down to 4 rows being sync’d.
Unfortunately, I am now getting a warning saying I need a Pro Secure plan, even though I am not requiring user sign-in.
The documentation on the availability of of the Publisher Pro plan says that it has all the features of the Pro plan, which in turn has Security Filters included. As far as I can see, there is no mention in the security filter documentation of user sign-in being a requirement for this feature.
Just wondering if a) the documentation of what is included in Publisher Pro is incorrect or b) the back-end plan checking is out of step with current plan inclusions.
thanks for your help