Skip to content

Key Considerations

A summary of essential factors and potential constraints to review before proceeding with your configuration.

Accessing Portal Studio

To access Portal Studio, customers must complete both one‑time setup activities and per‑user access configuration. These steps ensure the environment, tenant, and users are correctly provisioned.

The following steps are typically completed once during customer onboarding:

  • The customer needs to be onboarded through the IFS Cloud onboarding journey or via ai onboarding journey. SKU purchased, custom URLs etc. needs to be captured in this process.
  • Customer Admins must be declared as part of onboarding. For existing customers, this step is required if not already completed in order to run the provisioning pipeline.
  • Once provisioning is triggered, SKU and Custom URL are stored in LEC and a notification email is sent to the Super Admins.
  • The required capabilities for the customer must be added as part of onboarding by SNOW in THOR.
  • Tenants are created by the Tenant Management Service via iCloud pipelines and are provisioned with the configured capabilities.
  • The Customer Admin accesses LEC using the link provided in the onboarding email and navigates to Access Studio.
  • The tenant card becomes visible in Access Studio, allowing configuration of the Identity Provider (IDP).

Per‑User Setup (Access & Role Configuration)

The following steps are required for each user who needs access to Portal Studio and its associated portals:

  • User accounts are provisioned and managed through the User Management (UM) system, which allows customers to configure their Identity Providers (IdPs)
  • Access to Portals is limited to users that exist in the configured and supported Identity Provider
  • Guidance for setting up and managing IDP groups is available here.
  • Using User Management, IDP groups must be mapped to the relevant access groups. At this stage, selected IDP groups are assigned the Super Admin role.
  • Super Admin users can then access Portals designer.
  • Within Portal Designer → Admin Configurations → Portal Admins, Super Admins can assign additional users as Portal Admins. Portal Admins are responsible for building portal applications and managing portal‑level access.

image-20260218-132737

Portal_admin

  • Portal Admins can manage end‑user access by mapping users or IDP groups to Portal Access Groups via Portal Studio → Admin Configurations → Access Group Management, controlling which B2B(Authenticated) portal applications are accessible to which users.

image-20260218-133651image-20260218-133753

Note: For issues related Portal Studio functionality:

· Refer to Nexus product documentation

· Contact the Nexus support or platform team