HOPEX Aquila EN

PLATFORM - SaaS Self-Services > Objective

Objective

Self-Services are designed for SaaS solutions, enabling their administrators to independently manage key features, reducing reliance on Mega Cloud Services (MCS).

Prerequisites

To access the Self-Services, the following profiles and roles must be provided by MCS:

• HOPEX Administrator - SaaS profile to access Self-Services in HOPEX Administration.

• Delegated Administrator role to access Self-Services in the HAS console.

Scope

Self-Service	Purpose	Access	Required Profile/Role
API Key Management	Securely establish sessions with HOPEX. See Managing API Keys.	HOPEX Administration	HOPEX Administrator - SaaS
Named Licenses Management	Assign or revoke named licenses based on user profiles. See Managing Named Licenses.	HOPEX Administration	HOPEX Administrator - SaaS
Web Site Generation	Ensure continuous synchronization of data between the repository and the Web site. See Generating a Web Site.	HOPEX Administration	HOPEX Administrator - SaaS
Creation of Delegated Administrators	Allow selected users to use the HAS console. See Creating a Delegated Administrator.	HAS console	Delegated Administrator
Single Sign-On (SSO) Configuration	Enable the end user to access multiple applications or services with a single login (same username and password). See Configuring Single Sign-On (SSO) as a Delegated Administrator.	HAS console	Delegated Administrator
SMTP Server Configuration	Configure email transmission. See Configuring the SMTP Server.	HAS console	Delegated Administrator
Move to Production & Down Alignment	Ensure consistency and reliability across environments. See Move to Production & Down Alignment.	HAS console	Delegated Administrator