res.users.settings: fields, relations and API
The res.users.settings model ("User Settings") is a persistent model declared by the Base module, then extended by 8 other modules. It exposes 28 fields, 22 of them declared directly on the model; 3 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.
Model identity
- Technical name
res.users.settings- Label
- User Settings
- Type
- Persistent (models.Model)
- SQL table
res_users_settings- Origin module
- Base (
base) - Extended by
- web, bus, mail, calendar, im_livechat, google_calendar, project, microsoft_calendar
- Display field (_rec_name)
user_id- Inherits from (mixins)
- bus.listener.mixin
Model fields
22 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
28 of 28 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| calendar_default_privacy | Calendar Default Privacy Default privacy setting for whom the calendar events will be visible. | selection | required Values: added by Calendar ( |
| channel_notifications | Channel Notifications This setting will only be applied to channels. Mentions only if not specified. | selection | Values: added by Discuss ( |
| embedded_actions_config_ids | Embedded Actions Config | one2many | inverse: added by Web ( |
| google_calendar_cal_id | Calendar ID Last Calendar ID who has been synchronized. If it is changed, we remove all links between GoogleID and Odoo Google Internal ID | char | added by Google Calendar ( |
| google_calendar_rtoken | Refresh Token | char | added by Google Calendar ( |
| google_calendar_sync_token | Next Sync Token | char | added by Google Calendar ( |
| google_calendar_token | User token | char | added by Google Calendar ( |
| google_calendar_token_validity | Token Validity | datetime | added by Google Calendar ( |
| google_synchronization_stopped | Google Synchronization stopped | boolean | added by Google Calendar ( |
| is_discuss_sidebar_category_channel_open | Is discuss sidebar category channel open? | boolean | added by Discuss ( |
| is_discuss_sidebar_category_chat_open | Is discuss sidebar category chat open? | boolean | added by Discuss ( |
| livechat_expertise_ids | Live Chat Expertise When forwarding live chat conversations, the chatbot will prioritize users with matching expertise. | many2many | added by Live Chat ( |
| livechat_lang_ids | Livechat languages These languages, in addition to your main language, will be used to assign you to Live Chat sessions. | many2many→ res.lang | added by Live Chat ( |
| livechat_username | Livechat Username This username will be used as your name in the livechat channels. | char | added by Live Chat ( |
| microsoft_calendar_sync_token | Microsoft Next Sync Token | char | added by Outlook Calendar ( |
| microsoft_last_sync_date | Last Sync Date Last synchronization date with Outlook Calendar | datetime | added by Outlook Calendar ( |
| microsoft_synchronization_stopped | Outlook Synchronization stopped | boolean | added by Outlook Calendar ( |
| push_to_talk_key | Push-To-Talk shortcut String formatted to represent a key with modifiers following this pattern: shift.ctrl.alt.key, e.g: truthy.1.true.b | char | added by Discuss ( |
| use_push_to_talk | Use the push to talk feature | boolean | added by Discuss ( |
| user_id | User | many2one | required |
| voice_active_duration | Duration of voice activity in ms How long the audio broadcast will remain active after passing the volume threshold | integer | added by Discuss ( |
| volume_settings_ids | Volumes of other partners | one2many | inverse: added by Discuss ( |
| create_date | Created on | datetime | read-onlyautomatic |
| create_uid | Created by | many2one | read-onlyautomatic |
| display_name | Display Name | char | read-onlycomputedautomatic |
| id | ID | integer | read-onlyautomatic |
| write_date | Last Updated on | datetime | read-onlyautomatic |
| write_uid | Last Updated by | many2one | read-onlyautomatic |
Relations
Models linked from this model
- im_livechat.expertise: livechat_expertise_ids
- res.lang: livechat_lang_ids
- res.users: user_id
- res.users.settings.embedded.action: embedded_actions_config_ids
- res.users.settings.volumes: volume_settings_ids
Fields of other models pointing here
- res.users: res_users_settings_id
- res.users.settings.embedded.action: user_setting_id
- res.users.settings.volumes: user_setting_id
Reading this model through the API
Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.
curl -X POST "https://your-instance.odoo.com/json/2/res.users.settings/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["user_id","calendar_default_privacy","channel_notifications","google_calendar_cal_id","google_calendar_rtoken"],"limit":5}'import requests
BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}
res = requests.post(
f"{BASE_URL}/res.users.settings/search_read",
headers=headers,
json={"domain": [], "fields": ["user_id","calendar_default_privacy","channel_notifications","google_calendar_cal_id","google_calendar_rtoken"], "limit": 5},
)
res.raise_for_status()
print(res.json())- External API access requires Odoo's Custom plan.
- XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
- The access rights and record rules of the key's user apply.
Cite this tool
Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.
<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/res-users-settings">res.users.settings (Odoo 19.0)</a>Sources
Data verified on September 23, 2026 · Odoo 19.0 Community
Have an Odoo project, or want to put your ERP to work with AI? Let's talk
Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.