Skip to main content
Since PADS4 version 2025.2, you manage personal user information, role assignments, and license assignments in the PADS4 Web Portal. You still manage specific CMS 1.0 or Workspace information, like room access, in the corresponding Crystal Administration pages.

PADS4 Web Portal

  • When you assign licenses (PADS4 CMS 1.0 User and/or PADS4 Workspace User) to a user, PADS4 adds the user to the CMS 1.0 and/or Workspace user list. From there, you manage access to specific parts of these applications in the user profiles. For more information, see User profiles (CMS 1.0 & Workspace).
Cms Ws1
  • Assign license “PADS4 Workspace User” to give the user access to Workspace. This license is enough by itself to allow access to the Workspace app. You still manage room access and other Workspace-related settings through Workspace Administration.
  • Assign license “PADS4 CMS 1.0 User” to give the user access to Crystal CMS/CMS (legacy)/ CMS 1.0 and/or administrator pages (for CMS 1.0, Workspace or both).
    This license is NOT enough by itself to allow access to Crystal modules or its administrator pages. The user needs a user profile that allows access to certain parts of the Crystal platform: CMS 1.0, CMS 1.0 Administration Page, Workspace Administration Page, Wayfinding, etc.
  • Users that have sufficient licenses/rights will see corresponding app icons in the app selector on the login page.
Cms Ws2
  • As well as on the sidebar once you are on the Home page.
Cms Ws3

Core user information & creation

  • Previously, you created users in each app separately. Now, you always start by creating the user in PADS4 Ctrl Center. When you assign the user a CMS 1.0 and/or Workspace license, the user automatically appears in the CMS 1.0 Administration Page and/or Workspace Administration Page, depending on the license.
You now manage core information like username, first name, last name, NFC, and email address in PADS4 only. You can no longer update this information through a CMS 1.0 Administration Page.
Cms Ws4
  • You can still create a user through a Crystal Administration Page. To do so, select the PADS4 user. There’s also an option to automatically assign the user profile. More about this user profile assignment is explained later in the document.
Cms Ws5
  • If the current user has sufficient access to manage users in PADS4 Ctrl Center, you can select the link below the user dropdown menu. This redirects you to the user management page in PADS4 Ctrl Center, where you can manage (new) users.

User profiles (CMS 1.0 & Workspace)

  • You still manage CMS and Workspace user profiles, and therefore user access, in the corresponding administration page. PADS4 Role Mapping settings in the CMS 1.0 Administration Plugins Page now assign these profiles automatically. You can disable this automatic assignment per user.
Cms Ws6
  • The Auto assigned profile checkbox shows a preview of the assigned profile below it. PADS4 selects the profile based on the PADS4 Role(s) that are assigned to the selected PADS4 user and the PADS4 Role Mapping Settings you have configured. When you clear this checkbox, you can change the profile to any profile you want.
Take into account that this user will NOT update its profile based on the PADS4 Roles assigned to the linked PADS4 User when this setting is disabled. You can update the “Auto assigned profile” setting on the user at any time.

PADS4 role mapping

  • You can find these settings in CMS 1.0 Administration -> Plugins -> PADS4 Role Mapping. These settings are a big part of proper user management because they determine which user profile PADS4 assigns to each user:
  • PADS4 Role Mapping automatically assigns a profile to a user when synchronized with a PADS4 User. Since a PADS4 user can have multiple roles, you can use ’-’ as the profile value in a mapping. This tells the synchronization to collect all mappings linked to the user’s roles and select the profile based on the order defined in the table below (top to bottom). If no mapping matches any of the user’s roles, the default profile will be applied.
Cms Ws7
  • With the table above, PADS4 assigns the following profiles in different PADS4 Role assignment situations.
Some things to note from this example:
  • The Default profiles are used as a fallback and can be changed to another profile. When the PADS4 User does not have a role assigned or none of its roles are mapped in this table, it will use the default profile.
  • The ’-’ means it does not have a CMS or Workspace user profile mapped and will continue looking for other mapped roles. This means that the mapped role could end up with a default profile.
  • Mapping is optional. You do not have to map all PADS4 Roles, and you do not have to map a profile to a PADS4 Role.
  • The table is ordered. When a PADS4 User has multiple mapped roles, PADS4 always takes the role that is highest in the table. If that role maps to ’-’, PADS4 continues down the list until it finds a mapped profile or the default (fallback) profile.

CMS 1.0 admin plugins

  • PADS4 now handles most user information, including LDAP, User Provisioning/SCIM, SMTP, and Single Sign-On. These settings have moved from the Plugins page to PADS4 Identity providers.