supabase/web/docs/client/auth-update.mdx

---
id: auth-update
title: "auth.update()"
slug: auth-update
---

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

Updates user data, if there is a logged in user.

<Tabs
  defaultValue="js"
  groupId="libraries"
  values={[{ label: 'JavaScript', value: 'js' },{ label: 'Python', value: 'py' }]}>

<TabItem value="js">

```js
const { user, error } = await supabase.auth.update({ 
  data: { hello: 'world' } 
})
```


</TabItem>
<TabItem value="py">

```py
# Not yet implemented
```


</TabItem>

</Tabs>

## Parameters


<ul className="method-list-group">
  
<li className="method-list-item">
  <h4 className="method-list-item-label">
    <span className="method-list-item-label-name">
      attributes
    </span>
    <span className="method-list-item-label-badge required">
      required
    </span>
    <span className="method-list-item-validation">
      <code>UserAttributes</code>
    </span>
  </h4>
  <div class="method-list-item-description">

No description provided. 
  
  </div>
  
</li>

</ul>


## Notes

It's generally better to store user data in a table inside your public schema (i.e. `public.users`). 
Use the `update()` method if you have data which rarely changes or is specific only to the logged in user.










## Examples

### Update a user's metadata.



<Tabs
  defaultValue="js"
  groupId="libraries"
  values={[{ label: 'JavaScript', value: 'js' },{ label: 'Python', value: 'py' }]}>

<TabItem value="js">

```js
const { user, error } = await supabase.auth.update({ 
  data: { hello: 'world' } 
})
```


</TabItem>
<TabItem value="py">

```py
# Not yet implemented
```


</TabItem>

</Tabs>