The User object represents a User.

Organizations are the top level entity in the source application. Users are associated with an organization.

Groups are a collection of users in the source application. In some applications, they might also be called Teams.

Workspaces represent concepts like teams, workspaces, projects in apps that support them

Attachments are the files associated with a ticket or a comment.

Tickets and contacts can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. Yo…

Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments.

Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them.

Teams represent the grouping system used for Users. These are usually called groups, teams, agent groups, etc. in the underlying products. A User can belong to one or more Teams.

Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product.

Fields represent the attributes defined for various entities in the underlying product. Depending on the underlying product, custom attributes can be defined by a User on various entities like Ticket,…

Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc.

Organization represents the company or the entity using the ticketing system. An Organization can have one or more Workspaces and Users.