# Allow name removal using SSO

**URL:** <https://meta.discourse.org/t/allow-name-removal-using-sso/141691>\
**Category:** Feature\
**Created:** [February 15, 2020, 5:23pm UTC](https://meta.discourse.org/t/allow-name-removal-using-sso/141691 "2020-02-15T17:23:39Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mentalstring](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mentalstring/32/168934_2.png) [@mentalstring](https://meta.discourse.org/u/mentalstring)\
**Post date:** [February 19, 2020, 12:47pm UTC](https://meta.discourse.org/t/allow-name-removal-using-sso/141691/7 "2020-02-19T12:47:48Z")

</div>

We are not removing everyone’s names — the users are updating their own data whenever they update their account on our website (SSO provider). We rely on `/admin/users/sync_sso` to keep data in sync (username, name, avatar, etc) in their Discourse account. Name is an optional field and can be set to blank/empty.

I just realized the issue happens not just with name but also with updating bio, avatar, etc: it’s not possible to keep those SSO records in sync through `/admin/users/sync_sso` if they need to be updated to blank/empty, regardless whether they are mandatory fields or not.

I understand the point that people may be relying on existing behavior (although nobody reported this issue before?), but if this is the protocol, it seems it has significant limitations for its purpose of synchronizing SSO records.

---

_[View the full topic](https://meta.discourse.org/t/allow-name-removal-using-sso/141691)._
