Sites: The Operative Unit

The core architecture of Awetonet.io centers on a site-focused design. The Site serves as the primary administrative unit and the central environment for user collaboration.
Every infrastructure asset, automation script, and active network node is contained within a Site. Higher-level abstractions (Organizations, Groups, and Zones) exist solely to simplify how these individual Sites are managed, grouped, and secured across the entire enterprise.
The Unified Multi-Organization Dashboard

To eliminate the need to switch between multiple workspaces, Awetonet.io directs all users to a single, comprehensive Global Dashboard upon login.
- Direct Access: Users can view every individual Site they are authorized to access, regardless of which corporate organization owns it.
- Multi-Tenant Context: To maintain clear operational distinction, each individual Site card clearly displays the name of its parent Organization.
- Seamless Navigation: Engineers can navigate from a site in 'Organization A' to a site in 'Organization B' with a single action, without logging out or authenticating into a different tenant.
Site Groups (Filtering Only)
As networks scale to hundreds of locations, interface complexity can reduce operational efficiency. Site Groups are designed exclusively as metadata tags to organize complex user interfaces.
⚠️ Architectural Rule: Site Groups contain no access control rules. They are used exclusively for user interface sorting, searching, and regional filtering.
- Flat Structure: To prevent complex multi-level directory structures that can cause environment misconfigurations, an individual Site can belong to only one Site Group at a time.
- Functional Separation: Asset organization (Site Groups) is entirely independent from security boundaries (Management Zones), preventing administrative errors during scaling.