> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Permissions and Visibility

> How roles control what users can see and do in the ZEDEDA console, including predefined roles and how to manage users and roles in each service area.

## Introduction

Both Edge Infrastructure Services and Edge Inference Services use role-based access control (RBAC), but each service has its own role system, its own set of predefined roles, and its own administration workflows. This article covers both systems.

## Roles in Edge Infrastructure Services

### How roles work

A role maps permissions to resource types across a defined scope. Permissions correspond to four operations: Create, Read, Update, and Delete (CRUD). Scope controls which projects a role applies to. A role can apply across all projects in an enterprise or be restricted to projects matching a specific tag.

Your visible navigation, available actions, and accessible data all reflect your assigned role and the selected enterprise or project context.

### Predefined roles

Edge Infrastructure Services includes four predefined system roles: SysAdmin, SysManager, SysOperator, and SysMonitor. System roles are read-only and cannot be modified or deleted. You can also create custom roles with any combination of permissions and scope. For the full permission matrix, see [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md).

## Roles in Edge Inference Services

Edge Inference Services uses a separate role system scoped to organizations rather than projects. Access control has two layers: system roles and organization roles. For the full role definitions, see [Organizations, Users, and Roles](https://zededa.mintlify.site/new-ui/edge-inference-services/organizations-users-and-roles.md).

### System roles

The same four system roles used in Edge Infrastructure Services (SysAdmin, SysManager, SysOperator, SysMonitor) also control access to the Inference tab in the ZEDEDA console. A user who does not have a system role cannot see the Inference tab.

### Organization roles

Within Edge Inference Services, access to models, deployments, and settings is controlled by organization roles. An organization is the logical container for a team's ML models. Organization roles are assigned per user per organization and are independent of the system role. A user can hold a system role, one or more organization roles, or both.

## Next Steps

> [card] [Sign In and Switch Context](https://zededa.mintlify.site/new-ui/start/sign-in-and-switch-context.md)
>
> Access your account and switch between enterprises or projects.

> [card] [Navigate the ZEDEDA Console](https://zededa.mintlify.site/new-ui/start/navigate-the-zededa-console.md)
>
> Orient yourself in the sidebar, service areas, and key navigation patterns.

> [card] [Administration and Security](https://zededa.mintlify.site/new-ui/infrastructure-services/administration-and-security.md)
>
> The full set of enterprise configuration, identity, and access procedures.