Entity
A generic node in the project network — the flexible umbrella term for anything that participates.
What Is an Entity?
An Entity is a broad, flexible term for any node or participant in the project network. It is the umbrella concept the platform uses when it needs to talk about something that can be added to the network, connected to something else, or included in a process.
Think of "entity" as the general label before you get more specific:
- A System can be treated as an Entity
- A Connector can be attached to an Entity
- An Automation can interact with an Entity
- Connections are created between Entities
Why Does This Term Matter?
Not every user starts by thinking in technical system architecture. The term "Entity" allows the platform to present a network view without forcing too much technical detail too early. It is the concept that simply says: "This thing participates in the project network."
This flexibility is valuable because it lets you map your business landscape first, then gradually add specificity (Systems, Assets, Connections) as you build.
Real-World Example
A property management service project might include entities such as:
- A finance system
- A maintenance ticketing system
- A customer portal
- An internal approval service
Each one is a participant in the network. Each one can be represented as an Entity, connected to other participants, and included in data flows.
What an Entity Is Not
An Entity is not always the deepest technical object. It is not automatically a machine credential. It is not necessarily the same as a Connector or Automation. It is a general project-network concept — the building block from which more specific types (like System) are derived.
Short Definition
Entity: A generic node within the project network that can be connected, orchestrated, and included in data flows.