More finely grained application of Roles and Permissions for artifacts and associated attributes to protect content from "unauthorized" editing.

This would allow the protection of specific content in DNG to the benefit of the team members working in the tool.

Protection of "Content" and attributes from inadvertant (or intentional) changes by "unauthorized" team members by role would be desireable.  Basically - each Role/Permissions assigned to Artifact/Attribute could lock out team members from changing artifact/atributes that they are NOT process responsible/involved with in a "live" editable stream.

Each artifact and attribute would default to a "wide-open" Role/Permission (for those who do NOT want to work with this concept)...only those artifacts and/or attributes that NEED a restriction would have that restriction applied.

For example, a "Requirement" artifact: 

Artifact Type: SRS Req
Contents/Primary Text: "Some requirement statement."

Attributes:
In Scope: Boolean
Responsible Domain: Enumeration (single select)
System Architect:  User
System Requirements Engineer: User

Roles: 
“SRE” and “Architect” and “Commenter”.

Permissions:
SRE: Edit anything (Artifact Type, Contents, In Scope?, Responsible Domain, System Architect, System Requirements Engineer) and make Comments.
Architect: Edit Responsible Domain and System Architect ONLY as well as make Comments.
Commenter: Make Comments ONLY (essentially read only)

Each artifact and/or attribute would need a permissions definition associated...Members in the Project Area would, obviously, have to have the Process Role to work on the artifact/attributes of the Role.

This would be a more granular role/permission structure.