Getting started with self-service (admin portal)
Part of the builder section of your Frontegg portal, you will find your self-service portal. The Portal allows you to offer SaaS features to your customers from within your application by way of self-service.
First, integrate the self-service portal into your application. Next, make SaaS features available to your customers from within the builder by simply toggling features, adding configuration information where necessary, and granting access by using different roles, permissions or entitlements.
Integrate self-service menu
Integration takes just a few minutes. Choose your client side stack and integrate Frontegg self-service portal into your app.
Activate modules
Enable and configure self-service SaaS features for your customers.
Go to Builder ➜ Admin Portal and click on any of the modules to activate and configure specific features. Changes need to be published to each environment separately in order to appear in the self-service portal.
For instance, clicking on the Profile module takes you to the Profile tab in the builder where you can enable and configure Profile-related features for your SaaS customers to use in the self-service portal.
Profile settings and privacy & security
By default, the Profile Settings and Privacy & Security under the Personal section are automatically enabled when you integrate Frontegg into your app. You can disable Profile Settings only if you have one or more other features enabled for the self-service portal. You must always have at least one feature enabled for the self-service portal.
When you turn on a feature in the Builder, you can preview live in the Builder what it looks like in the self-service portal.
For instance, in the image below where Profile settings, Personal tokens, and Account settings are toggled on, you see in the preview all three features in the self-service portal sidebar.
Commit and publish your changes, and open the self-service portal from your application. You should see the new sections in the sidebar.
Different Environment Configuration
Different Environment Configuration
Consider whether you need to update the authorization configurations in any of your other [Environments] when enabling a new section a feature.
Grant access
In addition to the features you are enabling, the options a user sees in the self-service portal depends up on the user's roles, permissions or entitlements.
Therefore, even if a feature is turned on the the Builder, a user must have a role with permissions that gives the user read or write access to that particular feature or be entitled to that feature.
Learn more about Roles and Permissions.