Content
View differences
Updated by Klaus Zanders 20 days ago
**As** an administrator a \[enter role of user\]
**I want to** mark custom fields with special roles \[enter objective\]
**so that** they correctly depict their semantic meaning \[enter desired result\]
**Acceptance criteria**
* In user attributes there <br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is a new setting where we allow selecting what purpose the field is linked to. this feature visible?_
* First implementation of this _When is the "job title" field, but we will have other fields in the future (i.e. a user field with purpose "manager" might come to mind)
it not visible?_
**Translation considerations**
* Only one field should be allowed to have _Key terms and phrases in the purpose set and a field can only have one purpose key languages_
**Technical notes** **Out of scope**
* There should <br>
_Set the_ **To be proper scopes informed/consulted teams** _field to quickly get include all teams necessary to be informed of the custom field/custom value by the purpose's identifier
**Permissions and visibility considerations**
* _admin only manageable_ changes._
**I want to** mark custom fields with special roles
**so that** they correctly depict their semantic meaning
**Acceptance criteria**
* In user attributes there
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom
* First implementation of this
**Translation considerations**
**Technical notes**
* There should
_Set the_ **To
**Permissions and visibility considerations**
* _admin only manageable_