Policy-driven configuration

We believe that as a brand you should have the ability to make changes big and small, without needing to borrow developers or raising support tickets. To do this, the technology behind your CIAM solution needs to be solid, with state-of-the-art security mechanisms, features up to the latest industry standards, and operating in a resource-efficient way to ensure those changes are sustainable throughout the product lifecycle.

Policy-driven configuration

That’s how we approach policy-driven administration. It’s like a starter kit full of CIAM capabilities that only require a few clicks to be implemented.

What is a policy?

A policy is a group of reusable common settings that determine the customer journey for sign-in, sign-up, and self-service—when working together with applications—or define the administrative experience when applied to the Strivacity platform.

All Strivacity capabilities are based around a simple policy framework and the assignment of policies to an application.

They're flexible

Strivacity's clicks-not-code approach provides you the flexibility to build amazing customer journeys without needing to crack open a CIAM manual. Many scenarios can be implemented with zero code through policy configuration. You have at your fingertips

  • pre-built journeys,
  • account management solutions,
  • customization tools,
  • out-of-the-box integrations,
  • and security best practices

that cover a wide range of CIAM use cases. Configuring an MFA option, adding a new social login, or changing the background of the login screen all comes down to selecting an item from a drop-down, turning on radio buttons, or uploading some content.

And if these no-code options don’t seem to be enough, you can always turn to our extensibility platform for more capabilities.


We recommend exhausting policy-driven approaches before reaching for the power of our extensibility platform.

They're reusable

Policies are designed to be reused as many times as you need them. You can assign the same policy to multiple applications or apply it as an override to multiple organizations. This not only saves you time but reduces risk through misconfiguration.


You should be careful when editing a policy deployed in production. Any changes you save will take effect immediately and will affect all users using those applications that the policy is assigned to!

Configurable policy capabilities

Strivacity policies each provide a distinct set of capabilities.

You can find out more about them at the links: