Skedulo Objects and Fields

Skedulo objects and fields serve a similar purpose to database tables and their columns. They organize and structure data within the Skedulo platform. For instance, one of the primary objects in Skedulo data model, Jobs, represents a unit of work that needs to be undertaken, utilizing one or many Resources. A Job captures the primary information about a unit of work, for example, the location, when the work will occur, and the anticipated duration. Each occurrence of an object, known as a “record,” corresponds to a specific instance of that entity. Records are akin to rows in a database table.

Skedulo provides two types of objects: standard objects, which are predefined by the platform, and custom objects, which users can create through Skedulo’s web interface.

While this guide outlines all available standard objects within Skedulo, your environment(s) interact only with objects for which you have authorization. Access to objects is governed by your organization’s setup, including configuration, user permissions, access settings, and data sharing policies, which are typically managed by your Skedulo administrator.

Most objects accessible through the Skedulo GraphQL API and support both read, write and delete operations.