From ea01c273de9dcb038757ab11950999816418fdf3 Mon Sep 17 00:00:00 2001
From: Jannik Heym <66784399+Jannik-Hm@users.noreply.github.com>
Date: Wed, 14 Aug 2024 16:41:30 +0200
Subject: [PATCH] Added instructions on how to restrict Omada User privileges
 for widget

---
 docs/widgets/services/omada.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/widgets/services/omada.md b/docs/widgets/services/omada.md
index f42e73a6..f70de402 100644
--- a/docs/widgets/services/omada.md
+++ b/docs/widgets/services/omada.md
@@ -5,6 +5,19 @@ description: Omada Widget Configuration
 
 The widget supports controller versions 3, 4 and 5.
 
+In order to restrict the user for API access to the bare minimum, one has to follow these steps:
+
+1. Change organization to `Global View`
+2. Go to `Account` settings in the lower left corner
+3. Navigate to `Role` in the upper bar and add a new Role with the following priviliges
+    1. Site - `Dashboard Manager` to `View only`
+    2. Site - `Log Manager` to `View only`
+4. Choose a name of your liking
+5. Go back to `User` in the upper bar and create a new user for your homepage with the just created Role
+6. Select the sites, this API User should have access to
+
+Now you can use the `username` and `password` of this User, having only the required privileges for all allowed fields.
+
 Allowed fields: `["connectedAp", "activeUser", "alerts", "connectedGateways", "connectedSwitches"]`.
 
 ```yaml