Administration

Overview

The service is configured and administered through a cloud-based administration portal. The following configuration options, usage and insights are available in the EasyPSK administration portal.

EasyPSK Context Setup

EasyPSK Context – Create an EasyPSK context and configure / update the Cisco Meraki Dashboard API integration (Meraki WPN) or the RADIUS integration your Cisco Meraki or Catalyst 9800 wireless points at (EasyPSK via RADIUS).

Context Overview / Dashboard – The dashboard displays an overview of the integration usage, licensing and status.

Advanced Network and User Insights – Each EasyPSK context has a corresponding dashboard providing information such as:

• Tracking the number of EasyPSK groups created, active users, and the total connected devices across all groups.
• Real-time device monitoring per group, including:
  • First and last seen timestamps,
  • Group name (indicating the PSK used for access),
  • Serving access point,
  • Data usage (upload/download).
• Search function, based on group name, user, or device MAC address.

Group Management

• Groups page: One page lists the context’s groups, with Devices and Self-Service Users as views on the same page (one row per person, with their groups). Filters and counts by security flavour, site and status, with the site as a column.
• Group Creation: Administrators can create distinct network groups, each configured with its unique PSK for secure access. The security flavour (Instant, Approved or Dedicated) is chosen in the wizard and locked once the group has its first device.
• Bulk Group Creation (EasyPSK via RADIUS): Many groups in one run, either as a numbered series (a prefix and a number range, several rows per run) or from a CSV file, with the security flavour, site, Self-Service Experience, device cap and end date applied to every new group. The run is analysed into a plan, approved, and then carried out; a history of runs is kept.
• Rules: Each group carries a Rules card: its site, Self-Service Experience, device cap, validity (an end date after which devices are denied and the group is archived) and whether the group takes wired devices through MAB. Each rule shows whether it matches the site’s policy. An ended group is kept for the context’s archive retention period; an administrator can reactivate it in one step or delete it.
• Devices: Block or unblock a device from the device list; a blocked device is refused even with the right key and stays in the list marked as blocked. A changed key can be restored within seven days.
• Customizable PSK Settings: Fine-tune the complexity and character composition of PSKs, including options for uppercase/lowercase letters, numbers, and special characters.
• User Management: Each group can have dedicated users with accounts based on email addresses, granting them access to a self-service portal where they can securely retrieve or regenerate their group PSK. Each user can also carry an optional phone number, stored as a contact detail. A self-service user is added through a wizard (person, permissions, invitation) and opens in a dialog where permissions are edited or the user removed. A Self-Service Teams card on the group binds a team with the roles User admin, Password admin or Device admin, optionally with a welcome mail to new members.
• Bulk Provisioning and Sync (Meraki WPN): For the Meraki WPN delivery, an administrator can reconcile a whole context from a single CSV file describing the groups that should exist and the users in each. Uploading the file produces a reviewable plan (create, update, reset, delete) that is applied only after confirmation, and the current state can be exported to the same format as a starting point. Ideal for onboarding or turning over a building of units at once.

Sites and Site managers

Sites – A site is a named set of groups that belong together: the apartments of one building, a wing, a floor, a hall. Each site carries a policy for new groups (Self-Service Experience, security flavour, device cap and validity in days) that gives new groups their defaults, and the groups of a site are what a Site manager reaches.

Beta

A map of the sites and a site’s location are in beta, opened per organization on request.

Site managers – A Site manager is a role, not a person. It names the sites it covers and its members (email addresses or Self-Service Teams), and the administrator switches on what a member may see in the Self-Service Portal (groups, group users, devices, the group key, capacity use) and may do there (create, change and delete groups, regenerate keys, block devices, invite and remove users, print Wi-Fi Key Cards). A new role starts with every switch on. Members work in the Self-Service Portal only and gain no access to the administration portal.

Self-service onboarding

Onboarding rules give a person a group of their own the first time they sign in to the Self-Service Portal. Each rule names who it applies to (email domains, full addresses or Self-Service Teams) and what the new group gets: security flavour, Self-Service Experience, site, device cap (new rules start at 30), validity in days, the member’s roles and how the group is named. When several rules match, the most specific wins. A person who already belongs to a group in the context gets no new group. The page shows the portal address with a QR code, tests an email address against the saved rules, and prints the Self-Service portal poster.

Wi-Fi Key Cards

A printed card per group with the Wi-Fi network name, the key, a QR code, the group name and its end date. Named print designs hold the logo, the heading, message and footer texts, the layout and the language of the labels. The print wizard covers every Instant group, chosen sites and groups, or the portal poster, at 1 to 12 cards per A4 page, as a PDF. Only Instant groups print, since Approved and Dedicated groups need registered devices. Every printed PDF is recorded in the audit log.

Terms of use and privacy notice

Each context can carry terms of use and a privacy notice, with English as the main text and the other portal languages beside it. Nothing is required until an administrator saves them; from then on, self-service users accept them before they use the portal, and again when a new version is published. The texts are versioned.

Self-Service Experience

Six experiences (Home-like Wi-Fi, Co-working, Campus, Expo halls, Hospitality, IoT) set the words the Self-Service Portal, the invitation mails and the key cards use, for example Apartment and Resident, Room and Student, or Booth and Exhibitor. The experience is chosen on the context and can be overridden per site policy and per group. It never affects access or RADIUS.

Organization Administration

Common Settings – Basic configuration at organizational level such as

• Customer name,
• Language support,
• Access restrictions to admin-portal, IP-address-based filter.

Administration and Admin Portal Access

Administrators can log in and handle system configurations, user roles, and other key aspects of the service. Admin accounts can be created with varying access levels based on their assigned roles.

Admin Roles

1. EasyPSK – Administrator:
   • Full access to the EasyPSK service, including configuration.
2. Organization – Administrator:
   • Full access to system-wide configuration and admin user management.

The platform also supports integration with SAML 2.0 for Single Sign-On (SSO). This enables seamless user authentication and allows for mapping user groups in an Identity Provider (IdP) to roles within the platform. This integration streamlines account management and ensures users are automatically assigned appropriate access levels based on their group membership in the IdP.

This structure provides a flexible and secure solution for administrative and user role management.

Related

• Self-Service Portal: what members, Group Administrators and Site managers see and do.
• Sites and Site managers, Self-service onboarding and Wi-Fi Key Cards in the wiki: step by step.
• Self-Service Teams and Identity Provisioning (SCIM).