Restricting Access at Stream Level

Although a stream level permissions model sounds appealing, I worry that performance may suffer performing the permissions check. Even if it doesn't, who has the time to maintain a permissions model at the stream level (assuming your a large scale company)? If the purpose of this request is enabling external supplier access, one can do that at a project level. You could also create another ELM instance and manage permissions at a project level with the burden of transferring components between your native production instance and the external supplier ELM instance.

IBM if this change goes forward, please give your customers the opportunity to disable stream level permissions at a project level. Right now, GM uses a single project permission model and inherit it in all other projects with the exception of 3 which have a subset of the total number of users who have access to our main projects.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Requirements Management DOORS Next (formerly DOORS Next Generation- DNG)
Component - Feature

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Requirements Management DOORS Next (formerly DOORS Next Generation- DNG)
Component - DNG

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Requirements Management DOORS Next (formerly DOORS Next Generation- DNG)

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Product & application lifecycle management
Product - IBM Engineering Requirements Management DOORS Next (formerly DOORS Next Generation- DNG)

In order to clarify this enhancement. We understand the need for both READ and also WRITE access controls within streams. If this enhancement specific to WRITE access to a stream or is it asking for streams to be fully private for defined users? i.e. project membership does not mean you can see all streams?

IBM has determined that this request is likely not to be the delivered in the next release, but the theme of this feature is within our strategy