Home > Forum > User Voice > Decouple the default <Users and Groups> data source filters from the user synchronization cache

Decouple the default <Users and Groups> data source filters from the user synchronization cache
0

MVP

Hi,

the default data source `<Users and Groups>` currently appears to have a direct impact on the `CacheOrganizationStructure`. This behavior is unexpected and can lead to severe administrative issues.

The **User List Synchronization Configuration** already provides an **Advanced** tab where synchronization filters can be defined. Because of this, it is not obvious why additional filters configured on the default `<Users and Groups>` data source also affect the synchronized user and group cache.

For example, adding a simple **Group Members** filter to the `<Users and Groups>` data source, with the intention of displaying only employee accounts by default in user pickers, causes users and groups outside that filter to disappear from the `CacheOrganizationStructure`. As a result, even WEBCON developers and administrators can become inactive in the cache and lose access to both the Portal and the Designer Studio.

This coupling between the presentation/filtering behavior of the `<Users and Groups>` data source and the internal user synchronization mechanism is difficult to understand and can easily lead to accidental lockouts.

**Suggestion**

Please decouple the default `<Users and Groups>` data source filters from the synchronization process and the `CacheOrganizationStructure`.

The data source filters should only influence what is returned by the data source itself, while user synchronization should be controlled exclusively by the dedicated **User List Synchronization Configuration** (including its existing **Advanced** filters).

If this coupling is intentional for technical reasons, it should at least be clearly documented in the Studio and administrators should receive an explicit warning before configuring filters that may affect the synchronized user base.

This change would make the behavior much more predictable and help prevent administrators from unintentionally locking themselves and other users out of the system.

Kind regards
Sébastien

PS: If anybody runs in this problem one can use this file on the application server "C:\Program Files\WEBCON\WEBCON BPS Designer Studio\WEBCON BPS System Administrators\WEBCON BPS System Administrators.exe" to activate admin access to the Studio and to delete the filter in the default data source `<Users and Groups>`.

Nobody has replied in this thread yet.