Setting permissions in lifecycle states community wise
![]()
In lifecycles, we have three options for permissions in states - No change, Override modify, and Override All. Is it possible that we do not set any of these option in master lifecycle and set it at community level.
Our requirement is not to inherit permissions of states of lifecycles from master to community lifecycle. We need it to be set at community level. One community may have "No change" option set for "Draft" state and the other community may have "Override All" option set for "Draft" state. Please let us know if there is any way to do this? |
2 answers
![]()
If the permission of "No Change" is selected at the master lifecycle, you can choose whatever level of permission you want at the community level.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.