Content
View differences
Updated by Marc Alcobé 11 months ago
**As** a user \[enter role of user\]
**I want to** see my settings in a Primer style \[enter objective\]
**so that** there is UI coherence in all the app \[enter desired result\]
**Acceptance criteria**
* [ ] Primerise the UI of the user account using the border boxes of Primer.
* [ ] Introduce the new input form style for text based, switch and bottom sheet inputs. (This requires <mention class="mention" data-id="65588" data-type="work_package" data-text="###65588">###65588</mention> to be completed before).
* [ ] Introduce the option of table box headers with descriptions.
* [ ] Ensure all the description texts are updated.
* [ ] Specific `User account settings`:
* [ ] Remove the hidden click of user information header, expanding information below it with ID, admin…
admin...
**Technical notes**
* [ ] Specific `Sign out`:
<br>
**Permissions and visibility considerations**
* [ ] The currently signed in information _To whom is only available in developer mode.
**Technical notes**
this feature visible?_
* <br> _When is it not visible?_
**Out of scope**
* Create the help and feedback entries and flows. <br>
**I want to** see my settings in a Primer style
**so that** there is UI coherence in all the app
**Acceptance criteria**
* [ ] Primerise the UI of the user account using the border boxes of Primer.
* [ ] Introduce the new input form style for text based, switch and bottom sheet inputs. (This requires <mention class="mention" data-id="65588" data-type="work_package" data-text="###65588">###65588</mention> to be completed before).
* [ ] Introduce the option of table box headers with descriptions.
* [ ] Ensure all the description texts are updated.
* [ ] Specific `User account settings`:
* [ ] Remove the hidden click of user information header, expanding information below it with ID, admin…
**Technical notes**
**Permissions and visibility considerations**
**Technical notes**
**Out of scope**
* Create the help and feedback entries and flows.