See how Ramp uses ConductorOne
ConductorOne

ConductorOne Docs

Generate reports

Access review campaigns have built-in reports that show the progress and prove the outcomes of the campaign. Reports can be generated at any time after a campaign has started.

  1. In the navigation panel, click Campaigns.
  2. Click the name of the campaign you’re interested in.
  3. Click Reports > Generate Report and confirm your action.
  4. The report is compiled for you. Depending on the size of the campaign, this might take several minutes, so please be patient.
  5. When the report is ready, click Download to receive the report in Excel format.

How to read reports

The report is generated as a spreadsheet with two tabs. Read on to learn about the contents of each report tab.

Overview

CategoryDescription
Target Completion DateDate the Campaign Owner selected as the end date when preparing the campaign
Actual Completion DateDate the Campaign Owner actually ended the campaign
Total ReviewsThe number of reviews included in the campaign
Marked Out of ScopeThe number of reviews excluded from a campaign (often these are service accounts)
Selection CriteriaProvides the policies, entitlements, entitlement description, and number of reviews included

Access reviews

CategoryDescription
Review IDUnique ID assigned to each review [task] included in a Campaign
ApplicationThe Application included in this Campaign [the Application is determined when selecting Entitlements]

Ex: GitHub, AWS
App Identity[Local User Account] C1 maintains an optional mapping from the local account identity in the Application to a ConductorOne user account

This is also viewable under Applications >> find the App >> click Identities

Ex: smith.jane@gmail.com
User NameFull Name associated with an individual found within the associated Application

This is also viewable under Applications >> find the App >> click Identities

Ex: Jane Smith
Identity TypeUser or Service Account
Account OwnerThe account in your HR or IdP system that is associated with the user account in the app.

Ex: Jane Smith
Account Owner EmailEmail associated with the above account owner

Ex: smith.jane@acme.com
Entitlement NameThe name of the Entitlement in the specified Application. A row is created for each Entitlement

Ex: Repo Contributor T5 or AWS App Access
Entitlement ResourceThe subject Resources for an Entitlement

Ex: The Repository name in a Github
Entitlement TypeEx: Repository, Advanced Server Access, Application
Entitlement DescriptionDescribes the access rights of that Entitlement

Ex: access to AWS in Okta
In Scope[True or False] When preparing a Campaign, an ADMIN can determine if certain account types should be excluded.

This will confirm if that task was included [True] or excluded [False] from the Campaign
Review Started OnDate an ADMIN clicked "Start Campaign"
Due DateDate an ADMIN choses when creating a Campaign
ReviewersThe individuals required to action the review [task]
Reviewed ByThe individuals that actioned the review [task]. This will also include the name of the new Approver if a task is re-assigned
Review DecisionOptions Include: Approve, Approve with Comment [comment included in Audit Trail], Deny, Skipped

An ADMIN can chose to "Skip" review when ending a Campaign and a user has not yet actioned the review [task]
Audit TrailThe API representation of the audit event [Campaign]. This will contain all the raw data.
Tenant IDA unique internal identifier for the Campaign