The Admin Portal consists of modules that you can offer your customers and users.
Each module contains features for SaaS businesses. For instance, the modules include features for Profile, Privacy & Security, Account Details, Audit Logs, API Tokens, and more.
Decide which modules and features to enable for the Admin Portal. If you enable a module, users can access and use its features. You can control which users can access features with roles and permissions. If you disable a module, its features are not available to any users.
It takes just 5 minutes to add the Admin Portal to your application.
Just choose your tech stack and go.
In just minutes, your customers will have the ability to fully manage:
- Add a link to the Admin Portal in your application like in the section above
- Log in to your app and click the button invoking the
Upon clicking the button, the Admin Portal appears like in the image below.
The options a user sees in the Admin Portal depend upon two main things.
You might turn on Security and SSO in the Builder and configure roles and permissions so that Admin users can view and edit Security and SSO settings but Read Only users cannot. In this scenario, Admin users have Security and SSO in the Admin Portal but Read Only users do not.
For Admin Portal style customizations to take effect, use the following or later Frontegg package versions:
@frontegg/react - 4.0.14
@frontegg/nextjs - 4.0.14
@frontegg/angular - 4.12.0
@frontegg/vue - 1.0.9
Go to Home ➜ Builder.
These features are available within the Admin Portal tab in the builder.
Toggle a feature on for users to see and update those values in the Admin Portal. Toggle a feature off for it to not appear in the Admin Portal.
If a feature has a gear (⚙️) and you toggle it on, click the gear to configure the settings for that feature.
Start working with the Admin Portal using the guides below.
In addition to which features you enable, the options a user sees in the Admin Portal depends up on the user's roles and permissions.
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.
After integrating the Admin Portal, the next step is to publish to a Frontegg production environment.
After publishing to production, the final step is to manage your clients.
Updated 6 months ago