> ## Documentation Index > Fetch the complete documentation index at: https://docs.jengolabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Property OS core features > Properties, maintenance, scheduling, workflows, and more Property OS — Listings, units, or maintenance Issues view ## Portfolio and listings ### Properties (listings) A **property** is a building or site you manage. Each has a name, address, and optional type or category. You can have many properties in one workspace. * **Listings** or **Properties** in the menu: view all, add a property, open one to see units and linked vendors. * Edit or archive when needed. ### Units **Units** are the spaces inside a property (e.g. apartments, offices). Each has a number or name, rent, and optional details. You can assign a tenant to a unit. * From a property, open **Units** and add, edit, or remove units. Set rent and link tenants. ### Tenants (residents) **Tenants** are the residents linked to units. You use them for messaging, scheduling (vendor–tenant visits), and lease management. * Manage tenants from the property or unit, or from a **Tenants** / **Residents** list. Link each to a unit and contact info. ### Vendors **Vendors** are contractors or service providers (e.g. plumbers, electricians). You assign them to work orders and link them to properties when your setup uses property–vendor links. * **Vendors** in the menu: add vendors (name, contact, specialties), link to properties. ### Owners (optional) If your organization uses **Owners**, you can link properties or units to owners and manage them from **Portfolio** → **Owners**. *** ## Operations: maintenance ### Issues An **issue** is a maintenance request (e.g. leak, broken HVAC). It has a title, description, category, status, and is linked to a unit and property. * **Operations** → **Issues** (or **Maintenance** → **Issues**): view all, filter, add an issue, open one to assign a vendor or start a workflow. * Use the activity feed on the issue to see what was done. ### Work orders **Work orders** are the tasks tied to an issue: assign a vendor, schedule the visit, mark the work done. Workflows often create or update work orders and use scheduling so vendor and tenant agree on a time. * From an issue, assign a vendor or create a work order, then use **Scheduling** to get an agreed time and create the appointment. ### Maintenance analytics **Operations** → **Analytics** (or **Maintenance** → **Analytics**): dashboards and reports on issues, work orders, resolution times, and vendor activity. *** ## Scheduling **Scheduling** coordinates visits: the vendor proposes time slots, the tenant accepts or counter-proposes until both agree, then you confirm the appointment. * Start a session from an issue or work order (**Scheduling** or **Propose times**). Vendor and tenant use the app or links to propose and respond. When status is **Agreed**, create the appointment. *** ## Workflows **Workflows** are step-by-step processes (e.g. maintenance: assign vendor → schedule → complete → close). You start a workflow on an issue; the app runs the steps. * Open an issue → **Start workflow** → choose the workflow (e.g. default maintenance). See [Using workflows](/property-os/how-to-workflows). *** ## Communication and integrations * **Inbox / messaging** — Conversations with tenants, linked to tenant, unit, or issue. Agents can handle or triage. * **Notifications** — Email or SMS for scheduling, work order updates, reminders (when configured). * **Integrations** — Stripe, Slack, email/SMS, etc. Configured by your admin in **Settings** or **Integrations**. *** ## Agents and AI Hub * **Agents** — Create and configure chat, phone, or email agents. Use them for tenant support, triage, or running workflows. See [Agents](/agents/overview). * **AI Hub** — **Behaviour**, **Workflows**, and **Knowledge base** are configured here and used by agents across Property OS.