**As** a user requesting a new project
**I want to** assign roles to users as part of the project initiation request
**so that** these users are assigned to the project

[https://www.figma.com/design/tlD4wYMNV8S1DeQlGzku0s/Project-creation?node-id=2019-44957&m=dev](https://www.figma.com/design/tlD4wYMNV8S1DeQlGzku0s/Project-creation?node-id=2019-44957&m=dev)

### Begin of the insertion

**Acceptance criteria**End of the insertion Begin of the deletion Implementation alternativesEnd of the deletion

Begin of the deletion <br>

End of the deletion * Begin of the insertionUserEnd of the insertion Begin of the deletion Adding role assignments toEnd of the deletion project attributes Begin of the insertionadministration receive a new tab "Interlinked Role Assignment"End of the insertion

* Begin of the insertionA warning banner is shown explaining the consequences:

* _**Warning:** You are about to link aEnd of the insertion Begin of the deletion Extend global administration UI so that userEnd of the deletion custom Begin of the insertionfield with a role. This will give users with the "Edit Project Attributes" permission to add members to the project and they will be assigned the linked role. This may lead to privilege escalation because usersEnd of the insertion Begin of the deletion fieldsEnd of the deletion can Begin of the insertionassign themselves higher privileges than intended. Please make sure you understand the implications of this action._

* AEnd of the insertion Begin of the deletion receiveEnd of the deletion role Begin of the insertionselection field

End of the insertion Begin of the deletion selections

End of the deletion * Begin of the insertionGivable project roles are shown

* When a user, group, or placeholder user is selectedEnd of the insertion Begin of the deletion need to keep membershipsEnd of the deletion in Begin of the insertionthe project

* The given roleEnd of the insertion Begin of the deletion sync with these special attributes, whichEnd of the deletion is Begin of the insertiongranted regardlessEnd of the insertion Begin of the deletion a weird side-effectEnd of the deletion of Begin of the insertionpermissions of the granting user (as long as they have "Edit project attributes")

* That user membership is deleted when unset

* If the same user already hasEnd of the insertion a Begin of the insertionmembership, it is "taken over" and removed on unselect

* When theEnd of the insertion custom field Begin of the insertionexists before a role is assigned

* Existing selected users are updated to grant a membership(<mention class="mention" data-id="69158" data-type="work_package" data-text="#69158">#69158</mention>)End of the insertion Begin of the deletion updateEnd of the deletion

* Begin of the insertionWhen the selected role is changed

* Existing selected users are updated

* Previous membership role is removed

* New membership role is added

* When tryingEnd of the insertion Begin of the deletion Adding member specific stepsEnd of the deletion to Begin of the insertiondeleteEnd of the insertion a Begin of the insertionroleEnd of the insertion Begin of the deletion project template,End of the deletion that is Begin of the insertionassignedEnd of the insertion Begin of the deletion unrelatedEnd of the deletion to Begin of the insertionaEnd of the insertion custom Begin of the insertionfield

End of the insertion Begin of the deletion fields


&lt;br&gt;

**Acceptance criteria**

End of the deletion * Begin of the insertionAn error/warning is shown that it is in use


End of the insertion Begin of the deletion &lt;br&gt;


End of the deletion **Technical notes**

* <br>


**Permissions and visibility considerations**

* _To whom is this feature visible?_

* _When is it not visible?_


**Translation considerations**

* _Key terms and phrases in the key languages_&nbsp;


**Out of scope**

* <br>


_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._