discuss.channel.member: fields, relations and API
The discuss.channel.member model ("Channel Member") is a persistent model declared by the Discuss module, then extended by 1 other module. It exposes 27 fields, 21 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
discuss.channel.member- Label
- Channel Member
- Type
- Persistent (models.Model)
- SQL table
discuss_channel_member- Origin module
- Discuss (
mail) - Extended by
- im_livechat
- Inherits from (mixins)
- bus.listener.mixin
Model fields
21 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
27 of 27 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| agent_expertise_ids | Agent Expertise | many2many | computed added by Live Chat ( |
| channel_id | Channel | many2one | required |
| chatbot_script_id | Chatbot Script | many2one | computed added by Live Chat ( |
| custom_channel_name | Custom channel name | char | |
| custom_notifications | Customized Notifications Use default from user settings if not specified. This setting will only be applied to channels. | selection | Values: |
| fetched_message_id | Last Fetched | many2one | |
| guest_id | Guest | many2one | |
| is_pinned | Is pinned on the interface | boolean | computed |
| is_self | Is Self | boolean | computed |
| last_interest_dt | Last Interest Contains the date and time of the last interesting event that happened in this channel for this user. This includes: creating, joining, pinning | datetime | |
| last_seen_dt | Last seen date | datetime | |
| livechat_member_history_ids | Livechat Member History | one2many | inverse: added by Live Chat ( |
| livechat_member_type | Livechat Member Type | selection | computed Values: added by Live Chat ( |
| message_unread_counter | Unread Messages Counter | integer | computed |
| mute_until_dt | Mute notifications until If set, the member will not receive notifications from the channel until this date. | datetime | |
| new_message_separator | New Message Separator Message id before which the separator should be displayed | integer | required |
| partner_id | Partner | many2one | |
| rtc_inviting_session_id | Ringing session | many2one | |
| rtc_session_ids | RTC Sessions | one2many | inverse: |
| seen_message_id | Last Seen | many2one | |
| unpin_dt | Unpin date Contains the date and time when the channel was unpinned by the user. | datetime | |
| 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
- chatbot.script: chatbot_script_id
- discuss.channel: channel_id
- discuss.channel.rtc.session: rtc_inviting_session_id, rtc_session_ids
- im_livechat.channel.member.history: livechat_member_history_ids
- im_livechat.expertise: agent_expertise_ids
- mail.guest: guest_id
- mail.message: fetched_message_id, seen_message_id
- res.partner: partner_id
Fields of other models pointing here
- discuss.channel: self_member_id
- discuss.channel.rtc.session: channel_member_id
- im_livechat.channel.member.history: member_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/discuss.channel.member/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["channel_id","new_message_separator","fetched_message_id","guest_id","partner_id"],"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}/discuss.channel.member/search_read",
headers=headers,
json={"domain": [], "fields": ["channel_id","new_message_separator","fetched_message_id","guest_id","partner_id"], "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/discuss-channel-member">discuss.channel.member (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.