ADM10 - User Last Log on Analysis
- ADM01 - FastTrack Analytics Report and Metadata Configuration
- ADM04 - Configuration Summary
- ADM09 - Grant Audit
- ADM10 - User Last Log on Analysis
- Last updated
- Save as PDF
Overview
This report provides an analysis of the history of user log-on to Planview Enterprise. It allows the analysis of this data by user role and resource attributes (if the user is associated to a resource).
The report can be controlled to report on all log-ins or just daily unique log-ins using the Login Processing user parameter.
The report does not report on system usage, only actual logins. A user will typically only log in once during the day, but, depending on the session timeout, they could be asked to log in more (or less) often.
This report provides personal named users information and customers must therefore consider whether their data protection rules allow this information be to reported on. The personal data can be hidden, providing a summarized version of the report, by setting an administrator level configuration option, full details of which are provided below - Hide Personal Data in Report.

ADM10 example
Business Outcomes
- Drive adoption of Planview Portfolios by providing statistics on user log on frequency.
Supporting Capabilities
- Operational Administration
Report Detail
Report shows four graphs:
|
![]() |
|
![]() |
|
![]() |
|
![]() |
Following the graphs are three small table that shows:
|
![]() |
Finally, the detail table provides a full list of all log in records by user role, and User Name, ordered by time. Export to excel to further analyze this log in table information. |
![]() |
Report Business Rules
- This report is only supported for Planview Portfolios 12 and onwards because it uses an enhancement introduced in Planview Portfolios 12 that maintains a history of every log on event. In prior versions only the last log on event was stored in the Planview Portfolios database.
- This extended logging functionality needs to be enabled by the setting of a hidden global option. The global option can only be enabled by execution of a database script, which can be done by CloudOps, via a Customer Care ticket. Information on this global option is provided below.
- This report will by default, contain a user role feature to restrict this report for use by users who have the Add/Delete Users Planview Feature enabled on their User Role. Other users who try to execute this report will see an alert message. Remove the the Add/Delete Users feature on the Report Tile. to allow other users to access the report.
- When creating the ADM10 tile, the correct RDL file will be used based on the global option and presence of the audit table (PV12+). Existing ADM10 tiles will need to be manually re-pointed, as we do not update existing tiles.
- The login counts include duplicate logins by the same user on the same day. So if a user logged in at 10am and then logged in again at 4pm, both will appear in the counts. However, only the first login counts for the top five users table.
- Report Legend:
- The legend only appears on the bottom chart (when viewed interactively).
- When exported the legend appears in each chart (since each chart is exported to a separate page).
- Charts will appear taller when exported to accommodate the legend.
Administration: User Parameter Configuration
Parameters | Description | Configuration Options | Default/Example Settings |
Range Start: | Starting date of the range of returned data | Start date can be selected via the user parameter only | Default not configurable |
Range End: | End date of the range of returned data | Finish date can be selected via the user parameter only | Default not configurable |
Slice by: | Attribute used for slicing in the report | The list of slicers consists of the following:
NOTE Keep in mind that users aren’t always associated with resources so choosing a resource attribute could result in some “No Resource” slicer records. If colors are assigned to the slicer (alternate structure) they will be used by the charts as well.
|
slicer=role_user |
Section by: | Attribute used for sectioning in the report | The list of section by selections consists of the following:
NOTE Keep in mind that users aren’t always associated with resources so choosing a resource attribute could result in some “No Resource” slicer records.
|
section_by=none |
Filter By: | Attribute used for filtering in the report | The list of Filter by selections consists of the following:
NOTE Keep in mind that users aren’t always associated with resources so choosing a resource attribute could result in some “No Resource” slicer records.
|
filter_by_attrib=none |
Aggregate By | Attribute used for time aggregation in the report | The default value can be configured using the following parameter:
|
breakdown_by=auto |
Login Processing: | This parameter controls the way the report processes login information. The report can be controlled to report on all log-ins or just daily unique log-ins using the Login Processing user parameter. A user will typically only log in once during the day, but, depending on the session timeout, they could be asked to log in more (or less) often. This option would ignore any secondary logins by a single user throughout a day. |
The default value can be configured using the following parameter:
|
login_selection=all |
Administration: Hidden Parameter Configuration
Parameters | Description | Configuration Options | Default/Example Settings |
Hide Personal Data in Report | To support the protection of sensitive personal data, this Admin level configuration setting (hidden parameter) can be used to hide all user data on the report. Hiding user data (Configuring 'Yes') will:
|
Options are:
|
hide_user_details=N |
Report Title | Configurable report title that appears at the top of the report. | If a longer report title is required, then create additional report_title=xxx entries and these will be concatenated together based on the order in which they are listed in the configuration structure. | report_title=User Logon Analysis |
Enabling the Report
This report relies on a hidden global option (4202) being enabled (set to “Y”). The report will not run if the global option is not set.
The report can only display data as far back as when the global option was set.
The report will provide a warning if the user chooses a start date prior to when it was enabled
- Example: Warning: Data is not available for the selected date range - detailed login auditing starts on 28th December 2016
For On-Premises customers, the global option can be set by running the following script
- update ip.global_options set option_value='Y' where option_id=4202
For SaaS customers, please raise a customer care ticket to request that the global option is enabled.
Technical/Database Information
Report (RDL) Location | .../Reports/RPM_PROD/Admin_RPM/RPM-ADM10/RPM-ADM10.rdl |
Database | This report uses the transactional database and updates will be real-time. |
Framework | This report does not use the framework and as such is NOT configurable. |