Search

Skip to end of metadata
Go to start of metadata

On Monday 3 September we launched a new reporting interface to meet the demands of the modern admin-user.

Documentation can be found in the reporting section - what follows is a summary of the new functions.

Current functions

  • NEW - Dashboard
  • NEW - Account reports
    • Totals
      • By type
      • By status
      • By activity
    • Authentication
    • Usage
      • By group
      • By permission set
      • By any custom schema attribute
      • By country
      • By network
      • By organisation
  • Resources
    • Usage
      • By groups
      • By permission sets
      • By organisation (download only)
      • NEW - by almost any schema attribute
      • NEW - by resource and any reportable attribute
  • Scheduling
    • Monthly schedule
    • NEW - daily schedule
    • NEW - weekly schedule
    • NEW - any report type
    • NEW - any breakdown
    • NEW - read-only view for non-admins

All are available for the current organisation and totalled for the sub-organisations of the current organsation.

Additional functions under consideration

  • Additional dimensions (eg split by resource and by group) - DONE
  • API access
  • Breakdowns by user ID and other 'core' attributes - DONE

Making the most of the new functions

There are several things you can set up to make the most of the new features.

Since you now have the ability to report on almost any attribute you add to your schema you can generate reports by any criteria that are important enough to you to add to your accounts.

For example you could create additional schema attributes for departments / schools / offices / courses. Because you have the option to control the possible values for these at the domain level they can be consistent across any and all sub-organisations you might have. This will work for both personal accounts and local accounts if you have those connected, and the great advantage of this is that you can get the information you need in reports that are already aggregated by your choice of attribute so there is no need to manually cross match data between systems.  

Relevant help pages:


.

  • No labels