One of the most important milestones you reach in your CIAM journey is setting up the work environment for your administrative and customer support team. Instance configuration contains everything you need to know about configuring your Admin Console.
First of all, you should hand out the necessary permissions to your administrators. You can start onboarding your crew to the Admin Console by sending account invitations. Another way is to create admin accounts from scratch.
No matter which way you choose to onboard your team, you will need roles that define the level of permission they will have in the Admin Console. You can create roles that let you delegate access management to team members who can continue provisioning.
You can add your enterprise SSO with ease to the admin experience. You can also decide which login workflow will be the most practical for your administrators.
Admin account events capture the activities of administrative users during registration and login. Account events can help identify points of failure in case your team has problems with their accounts. You can also pull up the history of administrative changes your team made in Audit logs.
Strivacity aims to promote brand unity not just externally but inside your company. You can add your branding to the Admin Console so you can ensure consistency across the different tools and platforms your team uses. You can also style and manage the notifications your team receives in during their journey as an admin.
In case you're in need of the most basic information about your Strivacity instance, you can always look it up at Instance information.
Strivacity allows brand administrators very granular control over REST API permissions exposed by their instance. Administrators control access to the admin REST APIs at the read, write, or delete level.
Updated 5 months ago