Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| getting_started:wizard [2024/02/11 05:11] – system | getting_started:wizard [2024/02/11 07:00] (current) – system | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| * [[: | * [[: | ||
| </ | </ | ||
| - | * When the root user or any admin user log into RADIUSdesk, the system | + | * When the root user or any admin user logs on to RADIUSdesk, the system |
| - | * If this is the case, it will launch | + | * If none is defined yet, it starts |
| - | * The Setup Wizard is the recommended way to create a new cloud. | + | * <wrap em>The Setup Wizard is the recommended way to create a new cloud.</ |
| - | {{ : | + | |
| ====== What does the Setup Wizard do? ====== | ====== What does the Setup Wizard do? ====== | ||
| + | <panel type=" | ||
| + | {{: | ||
| + | </ | ||
| - | * Step 1 contains | + | ===== Step 1 ===== |
| + | |||
| + | * Contains | ||
| * When the wizard is complete you can simply add Access Points to your networks and you are good to go! | * When the wizard is complete you can simply add Access Points to your networks and you are good to go! | ||
| * Adding a new Cloud should take no longer than 5 minutes!! | * Adding a new Cloud should take no longer than 5 minutes!! | ||
| Line 17: | Line 21: | ||
| * Let’s assume you sign up a hotel chain called Royal Hotel. Then the following items will be created. | * Let’s assume you sign up a hotel chain called Royal Hotel. Then the following items will be created. | ||
| - | ===== Cloud ===== | + | <panel type=" |
| - | Called Royal Hotel | + | ^Item |
| + | |Cloud | ||
| + | |Realm | ||
| + | |Dynamic RADIUS Client | ||
| + | |Dynamic Login Page |With the name Royal Hotel owned by the Royal Hotel Cloud | | ||
| + | |Access Point Profile | ||
| + | * Named Royal Hotel (APdesk) owned by the Royal Hotel Cloud. | ||
| + | * Open SSID callled Royal Hotel Guest that has a login page (Captive Portal). | ||
| + | * Secure SSID called Royal Hotel Wireless that is bridged to the LAN. | ||
| + | </ | ||
| + | |Mesh Network | ||
| + | * Named Royal Hotel (MESHdesk) owned by the Royal Hotel Cloud. | ||
| + | * Open SSID callled Royal Hotel Guest that has a login page (Captive Portal). | ||
| + | * Secure SSID called Royal Hotel Wireless that is bridged to the LAN. | ||
| + | </ | ||
| + | |Permanent Users |< | ||
| + | * Named royal_hotel with password as designated owned by the Royal Hotel Cloud | ||
| + | * Named click_to_connect@royal_hotel with password as click_to_connect owned by the Royal Hotel Cloud | ||
| + | </ | ||
| + | </ | ||
| + | ===== Step 2 ===== | ||
| + | <panel type=" | ||
| + | {{: | ||
| + | </ | ||
| - | ===== Realm ===== | + | ==== Location and Customer Options |
| - | Called Royal Hotel owned by the Royal Hotel Cloud | + | * Enter the location here and decide how customers will access your hotspot. |
| + | * Select one or more | ||
| - | ===== Dynamic RADIUS Client ===== | + | === Vouchers |
| - | Called Royal Hotel owned by the Royal Hotel Cloud | + | * Select this option if you want your customers to use an easy-to-remember voucher. |
| + | * This option is suitable for situations where your customers are unlikely to be regular customers. | ||
| - | ===== Dynamic Login Page ===== | + | === Permanent Users === |
| - | Called Royal Hotel owned by the Royal Hotel Cloud | + | * Permanent users use a combination of username and password. |
| + | * Emails can be used as a username. | ||
| + | * Permanent users are normally allowed if a customer uses your hotspot regularly. | ||
| + | * Permanent users can register themselves if this option is configured on the login page. | ||
| - | ===== Access Point Profile ===== | + | === Click-To-Connect |
| - | * Called Royal Hotel (APdesk) owned by the Royal Hotel Cloud. | + | * Allows customers to connect |
| - | * Open SSID callled Royal Hotel Guest that has a login page (Captive Portal). | + | |
| - | * Secure SSID called Royal Hotel Wireless that is bridged to the LAN. | + | |
| - | ===== Mesh Network | + | ===== Step3 - Branding |
| - | * Called Royal Hotel (MESHdesk) owned by the Royal Hotel Cloud. | + | <panel type=" |
| - | * Open SSID callled Royal Hotel Guest that has a login page (Captive Portal). | + | {{: |
| - | * Secure SSID called Royal Hotel Wireless that is bridged to the LAN. | + | </ |
| + | * Here you can upload a Logo to brand your account. | ||
| + | * We recommend | ||
| + | * The width can vary from 100px to 200px. | ||
| + | * | ||
| + | ===== Step4 - Login Page Customization | ||
| + | <panel type=" | ||
| + | {{: | ||
| + | </ | ||
| + | * Here you can upload images that will appear on your login page. We recommend .png or .jpeg format with file sizes of 400Kb or less each. | ||
| + | * The first image will be the background image on your login page. | ||
| + | * The first image and subsequent images will also appear in the gallery application which is built into the login page. | ||
| - | ===== Permanent Users ===== | + | ===== Step5 - Theme |
| - | * Called royal_hotel with password as designated owned by the Royal Hotel Cloud | + | <panel type=" |
| - | * Called click_to_connect@royal_hotel with password as click_to_connect owned by the Royal Hotel Cloud | + | {{: |
| + | </ | ||
| + | * The last step is a legacy formality which you can just click through. | ||
| + | ====== Fine tune admin settings ====== | ||
| + | * Once you have created the cloud and its various elements, you can specify which cloud should be displayed by default when you log in. | ||
| + | * At the top right is a dropdown button with a Settings option that brings up the following screen. | ||
| + | <panel type=" | ||
| + | {{: | ||
| + | </ | ||
| + | * Once you have saved the new settings, please log out and log back in to confirm that they are working as intended | ||