User Guide

This guide is for operators and administrators who work with the Provision Portal UI through the browser.

It focuses on practical use, how the portal is organised, and what to expect — without requiring backend, build, or deployment knowledge.

Who should read this guide

Use this guide if you:

  • provision or manage CPE through the Provision Portal day to day,

  • need to understand how to navigate and operate the portal,

  • support other users working in the portal.

If you are a developer or maintainer looking for architecture, build, or deployment details, use the Technical Documentation instead.

What the portal is

The Provision Portal UI is a single Angular application served by Nginx. It gives you a graphical way to provision "services" on devices instead of dealing with low-level TR-069 objects. It talks only to the Provision Portal backend REST API; everything else (the ACS, the database) is reached through the backend.

If you are new to the portal, follow this order:

  1. Getting Started — sign in and orient yourself.

  2. Navigation Model — how the UI is laid out.

  3. Provisioning Operations — what each page does.

Roles & permissions

Access in the Provision Portal UI is governed by the signed-in user’s permission, enforced by the backend and by client-side route guards.

User

Day-to-day operator. Can perform provisioning operations (single / multiple device, replace, status, logs) but is blocked from User Management (PermissionGuard redirects USER to the single-device page).

Administrator

Operator capabilities plus User Management (create, update, delete users).

What you can see and do is determined by your permission. Some pages are additionally gated by server-side feature flags — for example Deactivate Service appears only when the backend enables it. If an action is not available to you, contact an administrator to review your access.
If you do not see an action described in this guide, your permission may not allow it, or a server-side feature flag may hide it. Contact an administrator to review your access.

Help and troubleshooting

If something does not work as expected:

  • Check Troubleshooting.

  • Review any validation messages and errors shown in the UI (they appear as toast notifications).

  • Contact an administrator if access or permissions are missing.

Glossary

If a term is unfamiliar, see Glossary.


This guide is written so you can jump directly to the operation you need. You do not have to read it from start to finish.