Shine a light on shadow apps

ConductorOne Docs

Configure application details

Configure key details about an application on the application's details page, including setting an application owner, choosing app-level policies, and entering a per-seat cost.

Rename the application

An application’s name is automatically chosen by the connector when the integration is set up. If you want or need to change the application’s name as it appears everywhere in ConductorOne, you can do so. This is especially helpful when you have multiple applications with the same name or need to provide context about which application your colleagues should choose when requesting access or setting up an access review campaign.

  1. In the navigation panel, open Apps and click Applications.

  2. Click the name of the application you want to rename.

  3. On the application’s details page, click the pencil icon next to the application’s name.

  4. Enter the application’s new name, then click Save.

The application’s name is now updated throughout ConductorOne.

Set an application owner

Set one or more owners for the application. By default, the application owner is the person who created the application, but you can change this assignment or add additional application owners if needed.

The application owner is the fallback provisioner for new access to the app if other provisioning methods aren’t set or available. Based on the policies set up by your organization, the application owner might also be required to review access to the application during UAR campaigns or to approve access requests.

  1. In the navigation panel, open Apps and click Applications.

  2. Click the name of an application.

  3. In the Details section of the page, click Edit.

  4. Use the Owner dropdown to select one or more owners for the entitlement.

  5. Click Save.

The application owners are now set, and you can update them at any time.

Set a per-seat cost

You can make a note of the per-seat cost for the application. This information will be included in the Insights section on review tasks. Setting a per-seat cost is optional, but it can provide helpful context to reviewers.

  1. In the navigation panel, open Apps and click Applications.

  2. Click the name of an application.

  3. In the Cost section of the page, click Edit.

  4. Enter the per-seat cost in U.S. dollars per month. Use whole numbers only.

  5. Click Save.

The per-seat cost will now be shown on the task details page of any access request or review for this application.

Set application-level policies

Set the policies to be used when reviewing, requesting, or revoking access to this app. Note that application-level policies are overruled by entitlement-level policies when entitlement-level policies are set. If a review policy is not set here, the campaign’s review policy will be used.

  1. In the navigation panel, open Apps and click Applications.

  2. Click the name of an application.

  3. In the Application policies section of the page, click Edit.

  4. In each field, use the dropdown to select from the list of available policies and choose the policy you want to assign to the application.

    ConductorOne automatically sorts the available policies by type, so you’ll only see Request policies in the Access requests field, Revoke policies in the Access revocations field, and Review policies in the Access reviews field.

  5. If you want to remove a default policy entirely, click the x in the dropdown.

  6. When you’ve made your selections, click Save.

Your application-level policies will now be applied to request, revocation, and review tasks for this application (unless an entitlement-level policy is set that overrules the application-level policy). Click any policy’s name to see more details about it, including its description and steps.