Roles and Responsibilities
AosEdge supports collaboration between several organizations and user roles.
This page explains the roles at product level. It does not define exact permissions or replace detailed access-control documentation.
For exact permissions, use the relevant AosCloud and Reference documentation.
Why roles matter
AosEdge is used by different organizations that do not have the same responsibilities.
The platform separates responsibilities so that each participant can work within its own scope.
This helps the OEM keep governance over the product ecosystem while allowing Service Providers and Fleet Owners to participate in controlled workflows.
OEM
The OEM owns or controls the connected product ecosystem.
In an automotive context, the OEM may be a vehicle manufacturer or another organization responsible for the connected product architecture.
The OEM is usually responsible for:
- Defining how Units are managed
- Organizing Units into fleets and Unit Sets
- Controlling deployment governance
- Coordinating Fleet Owners and Service Providers
- Managing lifecycle policies
- Monitoring operation across the product ecosystem
- Ensuring that platform usage follows business, security, and compliance requirements
The OEM typically uses AosEdge to maintain control over connected Units after production.
Recommended next pages:
Service Provider
A Service Provider delivers software-defined functionality into OEM-managed environments.
The Service Provider does not necessarily own the Unit or the full fleet. Instead, it works within the governance and access model defined by the OEM.
The Service Provider is usually responsible for:
- Preparing Deployable Items
- Providing software-defined functionality for OEM-managed Units
- Participating in verification workflows
- Monitoring delivered functionality where access is permitted
- Coordinating with the OEM when deployment or operational issues require action
The Service Provider benefits from AosEdge because it receives a structured way to deliver and manage functionality without requiring unrestricted access to the OEM environment.
Recommended next pages:
Fleet Owner
A Fleet Owner operates a set of Units assigned by the OEM.
The Fleet Owner may represent an organization responsible for day-to-day operation of a fleet.
The Fleet Owner is usually responsible for:
- Monitoring assigned Units
- Managing fleet or Unit Set operation within the assigned scope
- Participating in deployment and verification workflows
- Tracking operational issues
- Supporting investigation of Unit health, alerts, and deployment results
The Fleet Owner benefits from AosEdge because it gets visibility and operational control over assigned Units without taking ownership of the whole platform.
Recommended next pages:
Admin
An Admin manages platform-level configuration, organizations, users, access, and operational settings.
The Admin is usually responsible for:
- Creating and managing organizations
- Managing users and access configuration
- Supporting platform setup
- Maintaining platform-level settings
- Helping resolve access or configuration issues
- Supporting governance across OEMs, Service Providers, and Fleet Owners
Exact Admin capabilities depend on the configured access model.
Recommended next pages:
How roles work together
The roles work together through controlled ownership and access boundaries.
A typical collaboration flow may look like this:
- The OEM defines the product ecosystem and governance model.
- Admin users configure organizations and access.
- Service Providers prepare Deployable Items.
- OEMs or authorized users control deployment scope and verification.
- Fleet Owners monitor and operate assigned Units.
- AosEdge reports state, telemetry, logs, and alerts to support operation and troubleshooting.
This model allows several organizations to participate without removing OEM control over Units and fleets.
Where to find exact permissions
This page explains responsibilities at a product level.
For exact permissions, access rules, API behavior, and configuration details, use:
Related documentation
For the main product introduction, see AosEdge Overview.
For terminology, see Key Concepts and Glossary.
For scenario examples, see Typical Use Cases.