# Concepts

> Core concepts that underpin how OneFuse works, including modules, policies, jobs, and workspaces

---

Site [llms.txt](/llms.txt)

---

## Terminology

| Abbreviation | Term |
| --- | --- |
| CMP | Cloud Management Platform |
| FQDN | Fully Qualified Domain Name |
| GUID | Globally unique identifier |
| kwargs | Python dictionary of keyword arguments |
| OVA | Open Virtualization Appliance or Application |
| RBAC | Role-based access control |
| UI | (Web) User Interface |
| VM | Virtual Machine |

---

Section pages:

- [Job](/docs/onefuse/concepts/job/): A job is a unit of work created when a OneFuse Policy is executed
- [Module](/docs/onefuse/concepts/module/): A module is an integration service that automates and connects hybrid cloud infrastructure components
- [Managed object](/docs/onefuse/concepts/managed-object/): A managed object is a resource created by a module policy and maintained by OneFuse
- [Policy](/docs/onefuse/concepts/policy/): A policy is a centralized configuration that governs how a module delivers its integration service
- [Tracking ID](/docs/onefuse/concepts/tracking-id/): A tracking ID is a GUID used to group all executions of OneFuse modules
- [Templating](/docs/onefuse/concepts/templating/): Templating uses variables and the OneFuse Template Engine to produce dynamic configuration values
- [Upstream providers](/docs/onefuse/concepts/upstream-providers/): An upstream provider is an automation or orchestration tool that consumes OneFuse policies
- [Workspace](/docs/onefuse/concepts/workspace/): A workspace is an independent container for users and policies with role-based access control