---
title: Understanding Roles and Access Levels
description: "# **Understanding Roles and Access Levels** Roles and access levels in uAuditor determine what each user can **view, create, edit, or manage** inside the platform. They ensure that users only access the information and tools relevant to their responsibilities while…"
url: "https://uauditor.com/help-center/platform-basics/platform-overview/understanding-roles-and-access-levels/"
updated: "2026-04-17"
category: Platform Basics / Platform Overview
---

# Understanding Roles and Access Levels

# **Understanding Roles and Access Levels**

Roles and access levels in uAuditor determine what each user can **view, create, edit, or manage** inside the platform.

They ensure that users only access the information and tools relevant to their responsibilities while maintaining operational control and data security across locations.

Administrators configure roles to match the organization’s structure and workflows.

## **Why Roles and Access Levels Matter**

Proper role configuration helps organizations:

- control access to sensitive data
- assign responsibilities clearly
- restrict editing permissions
- manage location-level visibility
- ensure accountability across teams
- support structured inspection workflows

This is especially important for multi-location operations.

## **What Roles Control**

Roles define access to major platform modules such as:

- Dashboard visibility
- Inspections
- Scheduled inspections
- Tasks
- Actions
- Templates and resources
- Reports and analytics
- Broadcasts
- Violations
- Client reviews
- Settings and administration

Each role determines whether a user can:

- view data
- create records
- edit content
- delete items
- assign tasks
- configure workspace settings

## **Access Levels in uAuditor**

Access levels typically operate across three dimensions:

### **Workspace-Level Access**

Controls whether a user can:

- manage company settings
- configure templates
- create schedules
- access reports across all locations
- administer users and roles

Usually assigned to administrators.

### **Location-Level Access**

Limits visibility and actions to selected locations only.

Users can:

- perform inspections within assigned branches
- manage actions related to their locations
- view reports for their operational scope

This is common for branch managers and supervisors.

### **Personal-Level Access**

Restricts visibility to items created by the user or assigned directly to them.

Users can:

- complete assigned inspections
- manage their own tasks
- update assigned actions

This level is typically used for inspectors or field staff.

## **Example Role Types**

Organizations commonly configure roles such as:

**Administrator**

Can manage:

- workspace settings
- templates
- users and roles
- locations and zones
- reports and analytics

**Supervisor**

Can manage:

- inspections within assigned locations
- corrective actions
- scheduled inspections
- team performance monitoring

**Inspector**

Can:

- perform inspections
- complete assigned tasks
- respond to actions
- upload evidence

Access is usually limited to assigned locations.

**Viewer**

Can:

- view dashboards
- access reports
- review inspection results

Cannot create or edit operational data.

## **Assigning Roles to Users**

Roles are assigned when creating or editing users inside:

**Settings → Roles**

Administrators can:

- create custom roles
- adjust permissions
- assign access scope
- modify role behavior at any time

This allows organizations to adapt access rules as operations grow.

## **Best Practices for Role Configuration**

For effective access control:

- assign administrator access only when necessary
- restrict template editing permissions
- define location-based roles clearly
- review access regularly
- align roles with operational responsibilities

Structured role configuration improves platform security and usability.