As a part time administrator of a few DSS instances, I would like a more intuitive and discoverable way to setup DSS security / access control that helps me understand my use case and helps me make the adjustments in all of the various security settings spread throughout the system. This would give me more confidence in deploying important applications to users throughout my organization.
Does this need to be looked at from scratch?
Does this suggest the need for an alternate overall security module that supplements the security settings spread throughout the system.
Is an DSS Academy security course needed?
This idea started as a question about:
As an administrator working with inexperienced end-users, I'd like to share an application that can have read-only shared data sets with the original project. The need to copy datasets when using an application limits the size of the dataset that is realistic to use with applications.
This should be an option. The current behavior should continue to be the default behavior for backward compatibility.
Below please find a thread about setting up this use case. That ended totally else where all about a group of folks working together with read access to a dataset.