What is the ConductorOne application and where do I find it?

The ConductorOne application contains current data on user access to ConductorOne and user permissions within ConductorOne. It lets you review and manage access to ConductorOne … with ConductorOne. It’s more than a bit self-referential, true, but we promise it’s useful.

You’ll find the ConductorOne app on the Applications page. Note that it’s the one with the purple logo.

If you create another application named “ConductorOne”, this is given a white logo.

What can I do with the ConductorOne app?

Key uses for the ConductorOne app include:

• Include ConductorOne user roles in an access review campaign. ConductorOne user roles are shown as roles in the ConductorOne app. You can add these roles to an access review campaign to audit whether ConductorOne users have the appropriate level of permissions in the app.

• Allow users to request new ConductorOne roles. You can add ConductorOne user roles to request catalogs and bundles, allowing users to request new permissions in ConductorOne.

  You cannot set app-level access configuration rules on the ConductorOne app, but you can configure access request settings on the individual roles.

What are the limitations of the ConductorOne app?

Because of the special, self-referential nature of the ConductorOne app, it lacks some functionality that’s present on all other apps:

• You cannot rename the ConductorOne app or its entitlements.

• The ConductorOne app does not support linked entitlements.

• You cannot bind entitlements in the ConductorOne app to entitlements in other apps.

• There are no provisioning settings for the ConductorOne app’s entitlement, as role provisioning and deprovisioning is completed by ConductorOne itself.