Navigation: Schema: helpdesk > Tables

team

Helpdesk Team

Catalog: Odoo

Schema: helpdesk

The data in this table is partitioned per value of the column.

This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.

Table Columns

The columns of the table team are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
access_instruction_message	string	Access Instruction Message	☐
active	boolean	Active	☐
alias_bounced_content	string	Custom Bounced Message	☐	If set, this content will automatically be sent out to unauthorized users instead of the default message.
alias_contact	string	Alias Contact Security	☑	Policy to post a message on the document using the mailgateway.- everyone: everyone can post- partners: only authenticated partners- followers: only followers of the related document or members of following channels
alias_defaults	string	Default Values	☑	A Python dictionary that will be evaluated to provide default values when creating new records for this alias.
alias_domain	string	Alias domain	☐
alias_email_from	string	Alias Email From	☐
alias_force_thread_id	int32	Record Thread ID	☐	Optional ID of a thread (record) to which all incoming messages will be attached, even if they did not reply to it. If set, this will disable the creation of new records completely.
alias_id_label	string		☐
alias_id	string		☐
alias_model_id_label	string		☐	The model (Odoo Document Kind) to which this alias corresponds. Any incoming email that does not reply to an existing record will cause the creation of a new record of this model (e.g. a Project Task)
alias_model_id	string		☐	The model (Odoo Document Kind) to which this alias corresponds. Any incoming email that does not reply to an existing record will cause the creation of a new record of this model (e.g. a Project Task)
alias_name	string	Alias Name	☐	The name of the email alias, e.g. 'jobs' if you want to catch emails for <jobs@example.odoo.com>
alias_parent_model_id_label	string		☐	Parent model holding the alias. The model holding the alias reference is not necessarily the model given by alias_model_id (example: project (parent_model) and task (model))
alias_parent_model_id	string		☐	Parent model holding the alias. The model holding the alias reference is not necessarily the model given by alias_model_id (example: project (parent_model) and task (model))
alias_parent_thread_id	int32	Parent Record Thread ID	☐	ID of the parent record holding the alias (example: project holding the task creation alias)
alias_status	string	Alias Status	☐	Alias status assessed on the last message received.
alias_user_id_label	string		☐	The owner of records created upon receiving emails on this alias. If this field is not set the system will attempt to find the right owner based on the sender (From) address, or will use the Administrator account if no system user is found for that address.
alias_user_id	string		☐	The owner of records created upon receiving emails on this alias. If this field is not set the system will attempt to find the right owner based on the sender (From) address, or will use the Administrator account if no system user is found for that address.
allow_portal_ticket_closing	boolean	Closure by Customers	☐
assign_method	string	Assignment Method	☑	New tickets will automatically be assigned to the team members that are available, according to their working hours and their time off.
auto_assignment	boolean	Automatic Assignment	☐
auto_close_day	int32	Inactive Period(days)	☐	Period of inactivity after which tickets will be automatically closed.
auto_close_ticket	boolean	Automatic Closing	☐
color	int32	Color Index	☐
company_id_label	string		☐
company_id	string		☐
create_date	datetime	Created on	☐
create_uid_label	string		☐
create_uid	string		☐
description	string	About Team	☐
display_alias_name	string	Alias email	☐
display_name	string	Display Name	☐
from_stage_ids	string		☐
fsm_project_id_label	string		☐
fsm_project_id	string		☐
has_external_mail_server	boolean	Has External Mail Server	☐
has_message	boolean	Has Message	☐
id	int32	ID	☐
member_ids	string		☐
message_attachment_count	int32	Attachment Count	☐
message_follower_ids	string		☐
message_has_error_counter	int32	Number of errors	☐	Number of messages with delivery error
message_has_error	boolean	Message Delivery error	☐	If checked, some messages have a delivery error.
message_has_sms_error	boolean	SMS Delivery error	☐	If checked, some messages have a delivery error.
message_ids	string		☐
message_is_follower	boolean	Is Follower	☐
message_main_attachment_id_label	string		☐
message_main_attachment_id	string		☐
message_needaction_counter	int32	Number of Actions	☐	Number of messages which requires an action
message_needaction	boolean	Action Needed	☐	If checked, new messages require your attention.
message_partner_ids	string		☐
name	string	Helpdesk Team	☑
open_ticket_count	int32	# Open Tickets	☐
portal_show_rating	boolean	Ratings on Website	☐	If enabled, portal users will have access to your customer satisfaction statistics from the last 30 days in their portal.They will only have access to the ratings themselves, and not to the written feedback if any was left. You can also manually hide ratings of your choosing.
privacy_visibility_warning	string	Privacy Visibility Warning	☐
privacy_visibility	string	Visibility	☑	People to whom this helpdesk team and its tickets will be visible.- Invited internal users: internal users can access the team and the tickets they are following. This access can be modified on each ticket individually by adding or removing the user as follower.A user with the helpdesk > administrator access right level can still access this team and its tickets, even if they are not explicitely part of the followers.- All internal users: all internal users can access the team and all of its tickets without distinction.- Invited portal users and all internal users: all internal users can access the team and all of its tickets without distinction.Portal users can only access the tickets they are following. This access can be modified on each ticket individually by adding or removing the portal user as follower.
rating_avg_percentage	decimal	Average Rating (%)	☐
rating_avg	decimal	Average Rating	☐
rating_count	int32	# Ratings	☐
rating_ids	string		☐
rating_percentage_satisfaction	int32	Rating Satisfaction	☐	Percentage of happy ratings
resource_calendar_id_label	string		☐	Working hours used to determine the deadline of SLA Policies.
resource_calendar_id	string		☐	Working hours used to determine the deadline of SLA Policies.
sequence	int32	Sequence	☐
show_knowledge_base	boolean	Show Knowledge Base	☐
sla_failed	int32	Failed SLA Ticket	☐
sla_policy_count	int32	# SLA Policy	☐
stage_ids	string		☐	Stages the team will use. This team's tickets will only be able to be in these stages.
success_rate	decimal	Success Rate	☐
ticket_closed	int32	Ticket Closed	☐
ticket_ids	string		☐
ticket_properties	string	Ticket Properties	☐
to_stage_id_label	string		☐
to_stage_id	string		☐
unassigned_tickets	int32	Unassigned Tickets	☐
urgent_ticket	int32	# Urgent Ticket	☐
use_alias	boolean	Email Alias	☐
use_coupons	boolean	Coupons	☐
use_credit_notes	boolean	Refunds	☐
use_fsm	boolean	Field Service	☐
use_helpdesk_sale_timesheet	boolean	Time Billing	☐
use_helpdesk_timesheet	boolean	Timesheets	☐
use_product_repairs	boolean	Repairs	☐
use_product_returns	boolean	Returns	☐
use_rating	boolean	Customer Ratings	☐
use_sla	boolean	SLA Policies	☐
use_twitter	boolean	Twitter	☐
use_website_helpdesk_form	boolean	Website Form	☐
use_website_helpdesk_forum	boolean	Community Forum	☐
use_website_helpdesk_knowledge	boolean	Knowledge	☐
use_website_helpdesk_livechat	boolean	Live Chat	☐
use_website_helpdesk_slides	boolean	Enable eLearning	☐
website_message_ids	string		☐	Website communication history
write_date	datetime	Last Updated on	☐
write_uid_label	string		☐
write_uid	string		☐

01-03-2023 15:29 Version 22.1.135-BETA+3826

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Odoo API Data Model

team

Table Columns

Important Safety and Usage Information