Projects
Projects help you organize Edge Gateways into a purposeful, easy-to-navigate scope.
Think of a project as a working context: a curated set of gateways plus the dashboards, reports, and resources that matter for a specific customer, site, machine line, or initiative.
Projects are especially useful when you want to:
- browse and operate a subset of gateways without relying only on company/fleet filters
- attach project-specific dashboards and reports
- link software resources that should be available to all gateways in the project (for example, a simulation package)
- Fleet = standardization at scale (shared baseline across similar gateways).
- Project = targeted grouping for navigation and project-specific assets. Many setups use both: fleet for governance, project for context. Notice a project can not be shared with subcompanies.
Project overview page
The Projects overview page shows:
- a list of all projects you can access
- project metadata (depending on your environment)
- quick search and filtering
As with other list pages, you can customize the visible columns using the eye icon on the right.
Project detail page
Open a project to see its detail page.
This page collects everything that belongs to the project in one place: gateways, dashboards, reports, and resources.
Info
The Info section is the project’s home base for documentation: what it is, why it exists, and how to use it.
- Description stored as Markdown
- Editor supports writing and previewing in one view (edit + render)
Use Info for:
- scope definition (which sites / lines / gateways belong here)
- operational runbooks (who to contact, escalation steps)
- deployment notes (version expectations, known constraints)
- links to dashboards/reports that operators should open first
Short, practical, and kept current.
If it’s not helpful during an incident, it’s too long—or too stale.
Edge Gateways
The Edge Gateways section lists all gateways assigned to this project.
This is the core value of projects: instead of hunting through the global gateway list, you get a targeted inventory aligned with a real operational need (site, customer, pilot, etc.).
Common use cases:
- quickly confirm the project’s gateway membership
- validate that all expected gateways are included
- open a gateway detail page without leaving the project context
Dashboards
The Dashboards section provides a project-scoped list of dashboards that apply to the gateways in the project.
Reports
The Reports section contains reports linked to the project.
This allows a project to carry its own reporting package: shift reports, weekly summaries, compliance exports, or acceptance-test PDFs.
Project reports are useful when the reporting scope is tied to:
- a customer deliverable
- a site-specific acceptance flow
- a pilot or rollout stage
Project dashboards for real-time monitoring.
Project reports for scheduled or packaged outputs.
Resources
The Resources section manages software resources linked to the project.
Linking a software resource to a project means:
- every gateway in the project gains access to that resource
- gateways can use any available version in the linked resource
This is ideal for project-specific additions such as:
- simulation tooling (e.g., Dual simulation)
- customer-specific binaries
- temporary rollout packages for a pilot
Project resources apply to all gateways in the project.
If only one gateway should receive the software, link it on the Edge Gateway instead.
If every gateway of a standardized group should receive it, link it via a Fleet.
Next steps
- Use Fleets to standardize configs, dashboards, and alerts across similar gateways
- Use Edge Gateways for device-level operations, variables, and cloud storage
- Use Configurations for reusable templates and consistent rollouts