diff --git a/config/permissions.yaml b/config/permissions.yaml
index f03950ab329c3dc53875d8e87449d0d1998f8a80..1a91239097a226f49713cf4109cbe0f4fdf3f165 100644
--- a/config/permissions.yaml
+++ b/config/permissions.yaml
@@ -1,4 +1,4 @@
-# Copyright (c) 2022  InterDigital Communications, Inc
+# Copyright (c) 2024  InterDigital Communications, Inc
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -758,7 +758,59 @@ services:
         roles:
           admin: 'allow'
           user: 'allow'
- #------------------------------
+  #------------------------------
+  #  IOT Service (Sbox)
+  #------------------------------
+  - name: 'meep-iot'
+    path: '/iots/v1'
+    sbox: true
+    default:
+      mode: 'allow'
+    fileservers:
+      - name: 'Api'
+        path: '/api'
+        mode: 'verify'
+        roles:
+          admin: 'allow'
+          user: 'block'
+      - name: 'UserApi'
+        path: '/user-api'
+        mode: 'verify'
+        roles:
+          admin: 'allow'
+          user: 'allow'
+    endpoints:
+      - name: 'Index'
+        path: '/'
+        method: 'GET'
+        mode: 'block'
+  #------------------------------
+  #  Sensors Sharing Service (Sbox)
+  #------------------------------
+  - name: 'meep-sss'
+    path: '/sens/v1'
+    sbox: true
+    default:
+      mode: 'allow'
+    fileservers:
+      - name: 'Api'
+        path: '/api'
+        mode: 'verify'
+        roles:
+          admin: 'allow'
+          user: 'block'
+      - name: 'UserApi'
+        path: '/user-api'
+        mode: 'verify'
+        roles:
+          admin: 'allow'
+          user: 'allow'
+    endpoints:
+      - name: 'Index'
+        path: '/'
+        method: 'GET'
+        mode: 'block'
+  #------------------------------
   #  FED Service (Sbox)
   #------------------------------
   - name: 'meep-federation'
diff --git a/js-apps/frontend/src/js/containers/home/home-page-container.js b/js-apps/frontend/src/js/containers/home/home-page-container.js
index ea50792b75d6f51ed4002d65c4817423ba3e08c1..38b1d81be6da1cd4cf8d9851ae0b3e60a7510f19 100644
--- a/js-apps/frontend/src/js/containers/home/home-page-container.js
+++ b/js-apps/frontend/src/js/containers/home/home-page-container.js
@@ -71,7 +71,7 @@ class HomePageContainer extends Component {
                 (4G, 5G, Wi-Fi, MEC Federation) and terminal types. Combining these assets in a geolocated environment, a user can gain
                 hands-on experience on the behaviour and capabilities of the Location (MEC013), Radio Network
                 Information (MEC012), Traffic Management APIs (MEC015), Device application interface (MEC016), Application Mobility (MEC021), WLAN Information (MEC028),
-                V2X Information API (MEC030) service API, MEC Federation Service API (MEC040) service APIs and Sensors-Sharing Services (MEC046). 
+                V2X Information API (MEC030) service API, MEC Federation Service API (MEC040) service APIs and Sensors-Sharing Services (MEC046).
                 MEC Sandbox provides also a support for Edge Native Connector (3GPP TS 29.222: 3rd Generation Partnership Project; Technical Specification Group Core
                 Network and Terminals; Common API Framework for 3GPP Northbound APIs).
               </p>
@@ -81,8 +81,8 @@ class HomePageContainer extends Component {
               </p>
               <p>
                 <b>Important Note: If MEC Federation Service API (MEC040) is used (e.g. by activation 4g-5g-wifi-macro-v2x-fed network scenarion), MEC services and
-                  MEC applications will be visible from other MEC Platform using also MEC Federation Service API (MEC040). 
-                  If you choose to use MEC Federation Service API (MEC040), you accept to establish MEC federation between two partners as specified in ETSI GS MEC 040 V3.2.1 (2024-03) Clause 5.2.4.1 Introduction. 
+                  MEC applications will be visible from other MEC Platform using also MEC Federation Service API (MEC040).
+                  If you choose to use MEC Federation Service API (MEC040), you accept to establish MEC federation between two partners as specified in ETSI GS MEC 040 V3.2.1 (2024-03) Clause 5.2.4.1 Introduction.
                 </b>
               </p>
               <p>