Skip to content

Training Understand Web Access

Craig Scott edited this page Jun 9, 2026 · 1 revision

Training: Understand Web Access

What you'll learn: what a Web Access user (limited or full) sees, why a role is required, and how an administrator gets them working. You need: a login with Web Access to an application (UI label "Tenant"), and — to grant access — an Administrator. Time: 5 minutes.

What "Web Access" means

Web Access is the access type for end users who work inside published screens rather than building the application. It comes in two forms — limited web access and full web access — and both require a role (created by the application administrator) before the user can do anything in the system.

Unlike Administrator and Developer Access, Web Access grants no menu sections on its own. Everything a web user can see or do comes from the role assigned to them.

What a Web Access user sees before a role is assigned

  1. Sign in and open the application. With no role assigned, you land on a welcome / empty-state screen: "You're seeing this screen because you don't have any roles assigned." It points you to the header Search and the System menu. Web Access welcome screen
  2. The left rail reads "NO ROLE OR ACCESS TYPE MENU CONFIGURED" — there are no menu sections, and the role footer shows No role active.
  3. Header Search finds nothing. Searching for an existing screen returns "No results found" — without a role granting access, screens aren't reachable. Search returns no results

First sign-in can take a while to load. Give it a moment before assuming something is wrong.

How an administrator enables a Web Access user

The application administrator does three things:

  1. Create a role with a Menu builder section and the screens the user should see — Training: Create a Role.
  2. Grant the role the right permissions via a policy and policy group — Training: Grant Permissions with Policies.
  3. Assign the role to the user and have them activate it — Training: Manage App Users.

Once a role is active, the user's menu section and assigned screens appear, and they can work.

Check your work

Before a role: welcome screen, empty left rail, Search finds nothing. After an administrator assigns and the user activates a role: the role's menu section appears with its screens.

The access-type ladder

Access type Menu sections before any role
Administrator APP ADMIN and DEVELOPMENT
Developer Access DEVELOPMENT only
Web Access (limited / full) None — a role is required

Related training

Training: Understand Developer Access · Training: Create a Role · Training: Manage App Users

🏠 Home

Getting Started (14)
Training Guides (52)

Applications

Access & Users

Data Models & Schema

Screens

Weather Lookup Series — guided 3-part build

Data Flows & Integrations

Data, Reporting & Monitoring

Enterprise & Organizations

Platform Concepts & Architecture (10)
Screens & Application Design (17)
Data Models & Schema (8)
Data Flows & Scripting (51)

Designing Flows

Data Flow Nodes

JSONata Reference

Scripting

Integrations & Connectors (30)

General & iPaaS

Plex

EDI

IIoT & Edge Gateway (18)

Physical Device Connectors

Edge Data Connectors

Reporting, Documents & Dashboards (8)
Administration & Access Control (27)
Data Management (8)
Accelerators, Templates & Packages (8)
Design Standards (1)
How-To Guides (8)
FAQ & Troubleshooting (1)
Release Notes (117)

2026

2025

2024

2023

2022

2021

2020

Policies & Company (6)

Clone this wiki locally