Timeline for How to add a property to all users to check in a visibility filter?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2020 at 22:04 | comment | added | David Reed | You don't have to keep assigning permission sets. You can assign an arbitrary number of Custom Permissions to your existing Profiles and Permission Sets as features become part of your production setup. | |
| May 31, 2020 at 22:03 | comment | added | Andy Ray | This isn't ideal for our use case because we don't want to have to keep blanket assigning permissions sets to all users as we build features. That's an additional cleanup step later of removing the permissionset from all users after we remove the visibility filter from the code. We'd rather it be the opposite, a way to detect all users have the feature without having to modify all users (which is more common in feature flagging) | |
| May 31, 2020 at 21:57 | history | answered | David Reed | CC BY-SA 4.0 |