# What does api.addSaveableUserOptionField do?

**URL:** https://meta.discourse.org/t/what-does-api-addsaveableuseroptionfield-do/381049
**Category:** Development
**Tags:** plugin-api
**Created:** [August 31, 2025, 7:54am UTC](https://meta.discourse.org/t/what-does-api-addsaveableuseroptionfield-do/381049 "2025-08-31T07:54:43Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [August 31, 2025, 7:54am UTC](https://meta.discourse.org/t/what-does-api-addsaveableuseroptionfield-do/381049/1 "2025-08-31T07:54:43Z")

</div>

There’s virtually no documentation on this, and the plugin API file doesn’t have a comment explaining the use of this function. Plus, the only place I can see it used is in plugins, not in core. So what does `api.addSaveableUserOptionField()` do exactly? Is there additional configuration needed to use it?

---

_[View the full topic](https://meta.discourse.org/t/what-does-api-addsaveableuseroptionfield-do/381049)._