Clicking on an application will take you to its page, which displays all associated data with the application.

The data points are

• Authorisation status

• The number of active users & change in the number of users compared to last month.

• Average monthly spending & change in spend compared to last month

• Average usage percentage & change in usage

• Upcoming renewal date

• The number of active contracts at present.

• The owner of the application

• Category

• Auto-renewals (on/off)

• Status(Active/Inactive)

• Month-wise usage & spend allocated to departments

To manually assign the spends to departments, you need to click the ‘Edit’ button, as shown in the screenshot. It will open a popup, as shown below.

Click ‘Switch to manual split’.

Enter the department names, assign percentage & click ‘Save’.

Additionally, if potentially overlapping products exist in your organization, this will be identified and other possible alternatives from our master list of applications.

The ‘contracts’ tab on the application overview page lists all the contracts for that particular application. And other details like the owner of the contract, the payment term, the contract end date & status. Clicking on the contract will take you to the individual contract’s page.

The ‘Users’ tab lists the users of the application, email, designation, usage percentage, allocated spend & status. Clicking any user will take you to the individual user’s page.

The ‘Transactions’ tab lists all the transactions mapped to the application.

You can also manually add a transaction for an application by clicking the ‘Add’ button on the top right corner. While adding a transaction you will need to enter the amount, transaction method & transaction date.

Zluri supports the following authorisation status.

1. Managed: These consist of the collection of apps approved by the IT admins and are either centrally deployed across the organisation, managed by a team or by an individual depending upon the usage requirement of the app.

2. Unmanaged: This category lists the apps used by employees of the organisation but not managed or approved by IT admins. These are discovered through your SSO integrations.

3. Restricted: These consist of the collection of apps that have been restricted for employee usage by IT admins. If any user attempts to use such an app, they would be unable to do so, and their user information would appear here.

4. Needs Review: This category hosts the collection of apps in the review due to its security and compliance policies. Once the IT admin assigns the owner and authorisation status for a particular app in this category, it will be shifted to the Managed apps section.

Note: The following sections are repetitive and applicable to each authorisation status.

We can change the authorisation status of applications anytime we want through the “Bulk Edit” option. 

Zluri also supports different types of views on each authorisation status. They are as follows:

• Main view: Contains most essential metrics such as owner, category, type, spend, usage, status(active/inactive), active user count, and cost. 

• Renewal view: Tells us about upcoming renewals in a single view. Contains metrics such as owner, spend, contracts count, next renewal date, vendor count and cost.

• View: This view shortage view shows top applications by usage. Contains metrics such as owner, usage, source, last used, department count, and inactive user count.

• Spends top applications by spending: Contains metrics such as owner, spend, avg spend, and usage cost.

• Custom view: Customers can create their custom view by selecting the columns they want.

To add an application, click the ‘Add’ button on the top right corner of the Application landing page.

Clicking the ‘Add’ button will open a side panel where you can search the applications. If it exists in our global master list of applications, It will appear.

You can select the application, select the owner & click ‘Add Application’ to add it.

If the application is not in our master list of applications, you can add it by clicking ‘Add New Application’ at the bottom of the dropdown list.

You will need to enter the following information & click ‘Add Application’ to add the new custom application.

• Application name - Required

• Website - Optional

• App logo - Optional

• Short description - Required

• Description - Required

• Category - Required

• Owner - Required

• Tags - Optional

You can edit application attributes from the Application landing page or individual application pages.

On the application landing page, you can edit the owner of the application & status through quick edits.

You can select multiple applications and change their authorisation, status & owners. The changes will be applied to all the applications you have selected.

In the individual application page, you can click ‘Edit’ on the top right corner of the page to open the ‘Edit Application’ side panel.

Here you can edit the application owner, status, auto-renewal & tags.

Zluri enables you to export all relevant data associated with the apps managed by the Zluri Dashboard externally. On the Applications menu, you can see the Export button, which can generate data in the form of reports. The report will be generated based on the following parameters:

• Application Name

• Archive

• Status

• Authorisation Status

• User Count

• Licensed User Count

• Unlicensed User Count

• Internal User Count

• External User Count

• Department Count

• Vendor Count

• Active User

• Inactive Users

• Spend

• Cost

• Average Monthly Spend

• Usage

• Type

• Total Contracts

• Threat level

• Risk Score

• Risk Level

• App Discovered Date

• App Last Used Date

• Next Renewal Date

• Is Custom

• Category

• Sub Category

• App Tags

• Owner

• Category Id

• Auto-Renewal

• Renewal Interval

• Renewal Type

• Source

• Logo Present

You can select all parameters or the ones you require to be included in the report.

You can generate the report based on

• All Applications

• Selected Applications

• Filtered Applications.

Please Note 

1. The generated report will be in .csv format.

2. You can also generate a composite report on a scheduled basis from the Reports module in the Zluri Dashboard.

Zluri allows you to upload data on multiple users across multiple apps in one go. Think of a particular app, say Slack. There may be hundreds or thousands of users of Slack in your organisation. Similarly, you may be using hundreds of apps as well. In such a scenario, entering user data for each field may be cumbersome. 

With bulk data upload, you can add all your data in a .csv sheet/report and upload the same in one go.

To bulk upload data, open the Applications module on the Zluri Dashboard and click on the button with the 3-dot column and select the Bulk Update Data option as shown above. 

The process involves three simple steps:

1. Select the fields you want to modify: You can modify data only for existing apps and select fields. Select the fields you'd like to modify and click on OK.

2. Download Editable CSV: Bulk updating application requires a standard file format that maps back to your applications. Click on the Download Editable CSV button, and the standard file format will be shared via email.

3. Upload the modified CSV: Once you have added the data based on the above steps, you can upload the CSV file by clicking on the Upload CSV option.

Once the import process is complete, the changes will be reflected in Zluri, and you will be notified via your registered email ID.

Zluri allows you to take additional actions for each application. Click on a particular application name from the Applications module. Then select the 3-dot button next to the app logo on the left centre of the screen. You can use the menu to perform the following actions: 

• Unmap Application: Used to unmap an application from the current Zluri integration.

• Map to a different application: Used to map an unmapped application with the initially available integration.

• Map to/Merge with another app: Used to integrate with the workspace of another app.

• Archive App: This is used to move the current app to the archive section in the Zluri workspace.

• Action History: Displays the actions marked for the selected app.

Active in the last 30, 60, and 90 days is basically calculated from any activity Zluri has observed for users under an application.

The last activity can be anything like signing in, logs, other activities shared by direct integration agents. That's where the active days get their data from.

It's an addition of all the activity logs we got for an application in the past 30, 60, 90 days. 

The data pipelines are running to get this data updated regularly.

Zluri Application Usage and User Usage Explained 

Customer Facing Documentation

Revision Summary

Disclaimer

This documentation, titled "Zluri Application Usage and User Usage Explained", provides a high-level overview of the logic, calculations, and essential considerations involved in identifying Zluri Application Usage and User Usage. We have made a conscious effort to exclude specific proprietary and confidential information to protect the interests of Zluri and its stakeholders.

The content herein is intended to serve as a general guide for our customers to understand better the conceptual framework of Zluri Application Usage and User Usage. It does not disclose specific details of the algorithms, methodologies, or any proprietary information used in the calculation process.

Readers are advised that the information provided in this documentation is for informational purposes only. It does not constitute a warranty as Zluri's Application Usage and User Usage calculations are subject to updates and improvements, and Zluri reserves the right to modify the methodologies as needed.

For any questions, clarifications, or further details, please contact the Zluri support team.

Thank you for your understanding and cooperation.

Sincerely,

Team Zluri

Overview 

Zluri's scoring system provides valuable insights into employees' applications and user usage within an organization. This document breaks down the context behind the scoring, weight distribution, and calculations considered for measuring 'application usage' and 'user usage' within organizations using the Zluri platform.

Application Usage Scoring

Zluri considers Average Volume (AV), Average Activity Days (AD), and Percentage of Users (PU) as the three primary factors to measure usage scoring for applications. Also, it assigns a Weight Distribution percentage defining the relative importance or contribution of each factor (AV, AD & PU) in the overall calculation of the final application usage score.

Definitions and Examples

1. Average Volume (AV)

Average volume of activity fetched per user per month.

• Definition: Frequency of user activity fetching for a specific application per month. This can be sign-in logs, activity logs, etc.

• Example Scenario: For instance, if a user signs up thrice a month with five activities tracked in the activity log, Zluri calculates these counts based on the proprietary technical logic and assigns a predefined AV score to the calculated number.
  
  

2. Average Activity Days (AD)

Average number of activity days for a month.

• Definition: Number of days any user is active in a month. This can range from 1 day to 31 days a month, depending on the month. 

• Example Scenario: For instance, if a user signs up thrice a month with five activities in one day, Zluri calculates the days' count and assigns a predefined AD score to the calculated number.
  
  

3. Percentage of Users (PU)

Percentage of users who use this app (adoption rate).

• Definition: Adoption rate indicating how many users from the organization are using a specific application.

• Example Scenario: For instance, if there are 100 users in the organization, and 50 use the application, Zluri calculates the percentage and assigns a predefined PU score to the calculated percentage.

Final Application Usage Score

The total Application Usage score is generated by combining AV, AD, and PU, also factoring in the assigned Weight Distribution percentage, which defines the relative importance or contribution of each calculated factor.

Refer to the Weight Distribution section for a detailed understanding.

User Usage Scoring

Zluri considers Monthly Count (MC), Mean of Monthly Count, Distinct Days (DD), and Mean of Distinct Days as the four primary factors to measure usage scoring for users. Also, assigns a Weight Distribution percentage defining the relative importance or contribution of each factor (MC, MeanMC, DD & MeanDD) in the overall calculation of the final user usage score.

Definitions and Examples

1. Monthly Count (MC)

• Definition: Number of activities a user has in a month.

• Example Scenario: For instance, if the number of activities for a user is more than or equal to one, Zluri calculates the activity count and assigns a predefined MC score to the calculated count.

2. Mean of Monthly Count

• Definition: Average monthly count in the past three months.

• Example Scenario: For instance, if the average number of activities for a user in the past three months is more than or equal to one, Zluri calculates the average activity count and assigns a predefined Mean of Monthly Count score to the calculated count.

3. Distinct Days (DD)

• Definition: Number of days of activity received for a user in the past month.

• Example Scenario: For instance, if the number of days of activity received for a user is more than or equal to one, Zluri calculates the days count and assigns a predefined DD score to the calculated count.

4. Mean of Distinct Days

• Definition: Number of average distinct days in the past three months.

• Example Scenario: For instance, if the average number of distinct days in the past three months for a user is more than or equal to one, Zluri calculates the average days count and assigns a predefined Mean of Distinct Days score to the calculated count.

Final User Usage Score 

The total User Usage score is generated by combining MC, Mean of MC, DD and Mean of DD, also factoring the assigned Weight Distribution percentage, which defines the relative importance or contribution of each calculated factor.

Refer to the Weight Distribution section for a detailed understanding.

Weight Distribution 

Weight distribution in the context of Zluri's Application Usage and User Usage scoring system refers to the relative importance or significance of each factor in the overall calculation of the final usage score. The assigned percentage of weight distribution values determines how much influence each factor has on the final score.

Application Usage Weight Distribution

For Application Usage, three factors are considered: AV, AD, and PU. The weights assigned to each factor reflect the perceived importance of each aspect in assessing application usage within an organization.

• AV: The percentage value assigned represents the importance of the frequency of application use. 

• AD: The percentage value assigned reflects the significance of user activity days on an application. 

• PU: The percentage value assigned reflects the contribution organizational adoption rate. 

User Usage Weight Distribution

For User Usage, four factors are considered: MC, Mean of MC, DD, and Mean of DD. The weights assigned to each factor reflect the perceived importance of each aspect in assessing user usage within an organization.

• MC: The percentage value assigned reflects the importance of the user's engagement level within a specific timeframe.

• Mean of MC: The percentage value assigned reflects the significance of assessing the user's historical engagement.

• DD: The percentage value assigned reflects the essence of assessing the consistency of user activity.

• Mean of DD: The percentage value assigned reflects the significance of assessing the historical consistency of user engagement.