Private Notes / Conditional Content – Security Group Selection
backlog
C
Common Barracuda
- When adding a private note using the Advanced WYSIWYG editor, the Security Group dropdown lists all security groups within the project, including those that do not have access to the current workspace.
Example:
Group A → Access to Workspace A
Group B → Access to Workspace B
While creating a private note in Workspace A, both Group A and Group B appear in the dropdown.
Although assigning Group B does not cause functional issues (as they cannot access Workspace A), it creates confusion and is not contextually relevant.
- When configuring conditional content in a workspace, the Reader Group dropdown lists all reader groups in the project, including groups without access to that workspace.
Example:
Reader Group A → Access to Workspace A
Reader Group B → Access to Workspace B
While setting conditions in Workspace A, both groups appear in the dropdown.
Although this does not cause publishing issues (Group B users cannot access Workspace A), it is not ideal behavior.
It would be great if the below enhancements are available;
When creating a private note in a specific workspace:
The dropdown should display only the security groups that have access to that workspace.
Irrelevant groups should be filtered out.
When defining conditional content within a workspace:
Only reader groups with access to that workspace should appear in the dropdown.
Non-relevant reader groups should be automatically filtered.
Log In
D
D360 Product Management
marked this post as
backlog