Org and Apps
Imagine you’ve been invited to a luxurious resort. The resort consists of various buildings and amenities, such as huts, a swimming pool, a restaurant and bar, a spa, a fitness center, and more. In this scenario, the entire resort can be seen as a “parent organization” (or org), while the individual buildings and amenities represent different applications (or apps) within that organization.
If we think about it, the main appeal of the resort lies in its facilities. Without these features—like the pool, restaurant, or spa—the resort wouldn’t have much to offer its guests. In the same way, an organization without apps lacks functionality and purpose, making it of little value.
On the flip side, these facilities wouldn’t exist without the resort itself. They need a specific piece of land and infrastructure to be built and maintained. If there was no resort, there would be no huts, pool, or spa—they can’t just float in the air without a physical foundation. Similarly, apps cannot exist independently; they need an organization to be created within. An app needs the context of an org to function and be accessible, just like the amenities need the resort premises to serve their purpose.
In summary, the relationship between a resort and its facilities is similar to that between an organization and its apps: both depend on each other for value and existence. The resort offers a space where amenities can be built, and these amenities give the resort its unique appeal. Likewise, an org provides a framework where apps are developed, and these apps provide the functionalities that make the org useful and valuable.
Note: The term Org is often replaced with Workspace since both refer to the same concept. However at some places only Org is used to distinguish it from the app. e.g. Org User is the term commonly used instead of Workspace User.