Apart from SSOs & direct integrations, Zluri also collects data through browser extensions & desktop agents. The agent's dashboard displays all the agents & their status.

Clicking on Agents will display the following details:

• The number of people who have at least one agent installed.

• The number of people who have at least one Browser agent installed.

• The number of people who have at least one Desktop Agent installed.

• You can also view the number of people using various Browser Agents like Google Chrome, Mozilla Firefox, and Microsoft Edge.

Clicking on Users, you can see the following details:

• You can view who installed which Browser Agent and their last active date.

• You can also ask them to install the Browser Agent by sending them a prompt.

Overview:

Get actionable insights on your organization's SaaS usage

Zluri is an enterprise SaaS Management Platform(SMP). It helps you discover, manage, and optimize your SaaS stack from a single dashboard. 

What Zluri Does:

• Zluri puts the IT Teams back in control of their new Saas-ified landscape.

• managesZluri helps to bring shadow IT to light, proactively monitors and manage SaaS spend, automates end-to-end SaaS app renewal management. and and 

• Zluri is data-driven and helps IT teams simplify, plan, secure, and get the most out of their SaaS apps portfolio.

• Zluri uses various ways to discover SaaS applications. The browser extension is one of them.

• Zluri browser extension helps IT administrators discover the SaaS applications & used by employees of the organization.

The browser extension runs locally on the client side to read browser activities & reports them to the Zluri server for analysis, where we identify & analyze the SaaS application-related activities & present them on the Zluri dashboard.

Version: 2.3.1

How it works:

1. Identifying as a SaaS app:
When an application is opened in the Browser, We track the basic metadata of the application, like the application name, the server URL from where the data is fetched, etc., and identify the SaaS application from it.

2. Each visit is counted as an activity:
Each time the application is opened, it is counted as an activity.

3. Analyzing the activity data:

Once we have the activities attributed to users, we aggregate that at least at a daily level for the organization & calculate how frequently the user is using an application compared to other users of the same application. This gives us a percentile score for a specific user for an application within that organization.

Data Collected:

We collect only non-sensitive information from your system, which is listed below.

• The URL opened in the tab

• The title of the webpage

• The timestamp of open/closing of the tab

We do not read the cookies saved in the browser, browser history or any content from the websites visited.

How To Install:

Step 1) Download the agent by clicking here
Step 2) Click on Extensions 

Step 3) Click On Settings and the Click On Install Add-On from File

Step 4) Choose the Firefox file that is downloaded, and click on Open.

Step 5)You get a Pop-up on the top right of the window. Click on Add.

Step 6) Enter your work email.

Step 7) We will send you a verification code to your email address. Enter the code, and you will be able to sign in.

Lastly, you can enter the website URLs for which you do not wish to be tracked. (This Step Is Optional)

Overview:

Get actionable insights on your organization's SaaS usage

Zluri is an enterprise SaaS Management Platform(SMP). It helps you discover, manage, and optimize your SaaS stack from a single dashboard. 

What Zluri Does:

• Zluri puts the IT Teams back in control of their new Saas-ified landscape.

• Zluri helps to bring shadow IT to light, proactively monitors and manages SaaS spend, and automates end-to-end SaaS app renewal management.

• Zluri is data-driven and helps IT teams simplify, plan, secure, and get the most out of their SaaS apps portfolio.

• Zluri uses various ways to discover SaaS applications. The browser extension is one of them.

• Zluri browser extension helps IT administrators discover the SaaS applications & used by employees of the organization.

The Zluri desktop agent is a lightweight application that lives in your computer's toolbar. This application reads SaaS usage & activities and sends them to the Zluri server for further analysis, which is then presented on the Zluri dashboard.

Version: 3.2.5

How it works

1. Identifying as a SaaS app:
   When an application is opened on the Desktop, we fetch the application name and identify the SaaS application from it.

2. Each visit is counted as an activity:
   Each time the application is opened, it is counted as an activity.

3. Analyzing the activity data:
   Once we have the activities attributed to users, we aggregate that at least at a daily level for the organization & calculate how frequently the user is using an application compared to other users of the same application. This gives us a percentile score for a specific user for an application within that organization.
   
   

Data Collected:

We collect only non-sensitive information from your system, which is listed below.

• Device Information

• List of Applications running in the background

• All software/applications are installed on the device

• The time for the application has been running

• Launching & closing an application

How to Install:

Step 1) Download the agent by clicking here for the .exe file and here for the .msi file.

Step 2) Install The Agent(double-click on the downloaded file)

Step 3) Authentication 

This can be done in two ways:
Option 1: Using your email address
Step 3.1. a) Enter your email address.

Step 3.1.b)  We will send you a verification code on your email address. Enter the code and you will be able to sign in.

Option 2: Using your Organization Token

The Organization token is sent to you via email.

Step 3.2. a) Enter your organization token, and you will see the "Waiting for authentication Screen." 

Step3.2.b)  The IT Administrator of your company will authenticate you with your user email; after that, you will be able to see the authenticated screen.

Step 4) Now the Agent is all set, it will continue to send data to Zluri servers in the background.

Overview:

Get actionable insights on your organization's SaaS usage

Zluri is an enterprise SaaS Management Platform(SMP). It helps you discover, manage, and optimize your SaaS stack from a single dashboard. 

What Zluri Does:

• Zluri puts the IT Teams back in control of their new Saas-ified landscape.

• Zluri helps to bring shadow IT to light, proactively monitors and manages SaaS spend, and automates end-to-end SaaS apps renewal management.

• Zluri is data-driven and helps IT teams simplify, plan, secure, and get the most out of their SaaS apps portfolio.

• Zluri uses various ways to discover SaaS applications. The browser extension is one of them.

• Zluri browser extension helps IT administrators discover the SaaS applications & used by employees of the organization.

The Zluri desktop agent is a lightweight application that lives in your computer's toolbar. This application reads SaaS usage & activities and sends them to the Zluri server for further analysis, which is then presented on the Zluri dashboard.

Version: 2.1.0

Download this build: https://drive.google.com/file/d/1BOpUnc4fqQ9DImenqIvf-X1H7IqMUI_o/view?usp=share_link

How it works:

1. Identifying as a SaaS app
   When an application is opened on the Desktop, we fetch the application name and identify the SaaS application from it.

2. Each visit is counted as an activity. 
   Each time the application is opened, it is counted as an activity.

3. Analyzing the activity data
   Once we have the activities attributed to users, we aggregate that at least at a daily level for the organization & calculate how frequently the user is using an application compared to other users of the same application. This gives us a percentile score for a specific user for an application within that organization.
   Data Collected:

We collect only non-sensitive information from your system, which is listed below.

• Device Information

• List of Applications running in the background

• All software/applications are installed on the device

• The time for the application has been running

• Launching & closing an application

How to Install:

Step 1) Download the agent by clicking on the download link received through email.

Step 2) Install The Agent

Step 3)Enter your work email (You will get a Validation Code on your email address.)

Step 4) Enter the Validation Code & you will be signed in.

Step 5)Now the Agent is all set, it will continue to send data to Zluri servers in the background.

Overview:

Get actionable insights on your organization's SaaS usage

Zluri is an enterprise SaaS Management Platform(SMP). It helps you discover, manage, and optimize your SaaS stack from a single dashboard. 

What Zluri Does:

• Zluri puts the IT Teams back in control of their new Saas-ified landscape.

• Zluri helps to bring shadow IT to light, proactively monitors and manages SaaS spend, and automates end-to-end SaaS app renewal management.

• Zluri is data-driven and helps IT teams simplify, plan, secure, and get the most out of their SaaS apps portfolio.

• Zluri uses various ways to discover SaaS applications. The browser extension is one of them.

• Zluri browser extension helps IT administrators discover the SaaS applications & used by employees of the organization.

The Zluri desktop agent is a lightweight application that lives in your computer's toolbar. This application reads SaaS usage & activities and sends them to the Zluri server for further analysis, which is then presented on the Zluri dashboard.

Version: 3.3.0

How it works

1. Identifying as a SaaS app
   When an application is opened on the Desktop, we fetch the application name and identify the SaaS application from it.

2. Each visit is counted as an activity.
   Each time the application is opened, it is counted as an activity.

3. Analyzing the activity data
   Once we have the activities attributed to users, we aggregate that at least at a daily level for the organization & calculate how frequently the user is using an application compared to other users of the same application. This gives us a percentile score for a specific user for an application within that organization.
   

Data Collected:

We collect only non-sensitive information from your system, which is listed below.

• Device Information

• List of Applications running in the background

• All software/applications are installed on the device

• The time for the application has been running

• Launching & closing an application

How to Install:

Step 1) Download the agent by clicking here for the .pkg file

Step 2) Install The Agent

Step 3) Authentication 

This can be done in two ways:

Option 1: Using your email address
Step 3.1. a) Enter your email address.

Step 3.1.b)  We will send you a verification code on your email address. Enter the code, and you will be able to sign in

Option 2: Using your Organization Token

The Organization token is sent to you via email 

Step 3.2. a) Enter your organization token and you will see the "Waiting for authentication Screen." 

Step3.2.b)  The IT Administrator of your company will authenticate you with your user email; after that, you will be able to see the authenticated screen

Step 4) Now the Agent is all set, it will continue to send data to Zluri servers in the background.

Step 5) Restart your system.

Permissions Zluri Mac agent requires:

1. Screen Recording Permissions -- - THIS IS A NOT A MANDATORY PERMISSION

For details on why you may consider giving this permission, click here.

Mac Agent Version: 3.2.3

Mac Versions tested on: Ventura[13.4], Big Sur[11.0], Monterey[12.6]

Permissions: Screen Recording Permissions - Optional Permission

Notifications to end users: “Login Item Added- zluri” might come up in some systems; it is a behaviour in control of MacOS

 Creation of Blueprint and adding the scripts

1. Click ‘Blueprints’ from the left navigation menu.

2. Click ‘New Blueprint’

3. Click ‘start from scratch’

4. Enter name & description

5. Click ‘Library’

6. Click ‘Add New’

7. Select ‘Mac’ & Click ‘Custom Apps’

8. Click ‘Add & Configure’

9. Add Title; select the Blueprint created above.

10. In the installation, select ‘Audit & Enforce.’

Audit script:

#!/bin/bash

# version comparison logic

function version_compare { printf "%03d%03d%03d%03d" $(echo "$1" | tr '.' ' '); }

# perform version comparision

function perf_comparison {

installedVersion=$(defaults read /Applications/zluri.app/Contents/Info.plist CFBundleShortVersionString) # ask installed version of the app from system

echo "installed zluri app version: $installedVersion"

expectedVersion="3.2.3" # admin should update the expectedVersion value to the latest version available

[ $(version_compare $installedVersion) -lt $(version_compare $expectedVersion) ] && echo "1"

[[ $(version_compare $installedVersion) -gt $(version_compare $expectedVersion) || $(version_compare $installedVersion) -eq $(version_compare $expectedVersion) ]] && echo "0"

}

shouldUpdate="0"

finalResult="0"

ZLURI_APP="/Applications/zluri.app"

if [ -e $ZLURI_APP ]

  then

     echo "zluri app found in /Applications/ dir"

    finalResult="0"

    perf_comparison

    shouldUpdate=$?

    echo "shouldUpdate again $shouldUpdate"

  else

    echo "zluri app NOT found in /Applications/ dir"

    finalResult="1"

fi

if [[ $shouldUpdate -eq "1" ]] || [[ $finalResult -eq "1" ]]

  then

  echo "it should update or exit with code 1"

  # first kill the app if running

  # needed for auto-update

  ZLURI_PROCESS=$(ps aux | grep -v grep | grep -ci zluri)

  OSQUERY_PROCESS=$(ps aux | grep -v grep | grep -ci osquery)

  if [[ $ZLURI_PROCESS -gt 0 ]] && [[ $OSQUERY_PROCESS -gt 0 ]]

    then

    echo "trying to kill the process"

      pkill -x "zluri"

      pkill -x "osquery"

  fi

  exit 1

fi

if [[ $finalResult -eq 0 ]] || [[ $shouldUpdate -eq 0 ]]

    then

    echo "all ok"

    exit 0

fi

11. Add the pre-install script and upload the package and post-install script.

Pre-install:

#!/bin/bash

CURRENT_USER=$( echo "show State:/Users/ConsoleUser" | scutil | awk '/Name :/ && ! /loginwindow/ { print $3 }' )

HOMEDIR=$(/usr/bin/dscl . -read /Users/"$CURRENT_USER" NFSHomeDirectory | /usr/bin/cut -d' ' -f2)

ORG_TOKEN=<orgToken>

INTERVAL= 3600000

SCREEN_RECORD=off

echo "$ORG_TOKEN"

echo "$CURRENT_USER"

echo "$HOMEDIR"

# Deleting App components from Application folder

echo "Deleting zluri Logs"

logsPath=$HOMEDIR/Library/Logs/zluri

if [ -d "$logsPath" ]

then

rm -rf $HOMEDIR/Library/Logs/zluri

echo "***Deleted Zluri Logs Successfully***"

fi

echo "Deleting Zluri Application Support"

applicationSupportPath=$HOMEDIR/Library/Application\ Support/zluri

if [ -d "$applicationSupportPath" ]

then

rm -rf $HOMEDIR/Library/Application\ Support/zluri

echo "***Deleted Zluri Application Support Successfully***"

fi

echo "Finished:preflight"

echo "writing zluri generic-MDM config file"

if [ ! -d /tmp/zluritemp ]; then

    mkdir -p /tmp/zluritemp

else

    echo "zluritemp dir exists"

fi

echo "{\"org_token\": \"$ORG_TOKEN\", \"interval\": \"$INTERVAL\", \"screen_recording\": \"$SCREEN_RECORD\", \"silent_auth\": \"on\"}" > /tmp/zluritemp/client-config.json

echo "====written the client config json file required configurations in temp directory===="

# Handle the rosetta-related issues in preinstall script

# Determine the processor brand

processor_brand=$(/usr/sbin/sysctl -n machdep.cpu.brand_string)

# Determine the processor brand

if [[ "$processor_brand" == *"Apple"* ]]; then

    /bin/echo "Apple Processor is present..."

    # Check if the Rosetta service is running

    check_rosetta_status=$(/usr/bin/pgrep oahd)

    # Rosetta Folder location

    # Condition to check to see if the Rosetta folder exists. This check was added

    # because the Rosetta2 service is already running in macOS versions 11.5 and

    # greater without Rosseta2 actually being installed.

    rosetta_folder="/Library/Apple/usr/share/rosetta"

    if [[ -n $check_rosetta_status ]] && [[ -e $rosetta_folder ]]; then

        /bin/echo "Rosetta2 is installed... no action needed"

    else

        # Installs Rosetta

        /bin/echo "Rosetta is not installed... installing now"

        /usr/sbin/softwareupdate --install-rosetta --agree-to-license

    fi

elsex

    /bin/echo "Apple Processor is not present...Rosetta2 is not needed"

fi

sudo mkdir -p $HOMEDIR/Library/Application\ Support/zluri

echo "{\"org_token\": \"$ORG_TOKEN\", \"interval\": \"$INTERVAL\", \"screen_recording\": \"$SCREEN_RECORD\", \"silent_auth\": \"on\"}" > $HOMEDIR/Library/Application\ Support/zluri/client-config.json

echo "====written the client config json file required configurations in temp directory===="

exit 0

Post Install:

#!/bin/bash

# writing config json file to appData directory

# CURRENT_USER=$(/bin/ls -l /dev/console | awk '{print $3}')

CURRENT_USER=$( echo "show State:/Users/ConsoleUser" | scutil | awk '/Name :/ && ! /loginwindow/ { print $3 }' )

HOMEDIR=$(/usr/bin/dscl . -read /Users/"$CURRENT_USER" NFSHomeDirectory | /usr/bin/cut -d' ' -f2)

ORG_TOKEN=<orgToken>

INTERVAL= 3600000

SCREEN_RECORD=off

echo "ORG TOKEN: $ORG_TOKEN"

echo "API INTERVAL: $INTERVAL"

echo "SCREEN RECORD: $SCREEN_RECORD"

echo "CURRENT USER: $CURRENT_USER"

echo "HOMEDIR: $HOMEDIR"

sleep 300

ZLURIDIR="$HOMEDIR/Library/Application Support/zluri"

echo "ZLURIDIR: $ZLURIDIR"

# cd $ZLURIDIR

if [ -d "$ZLURIDIR" ]; then

    echo "{\"org_token\": \"$ORG_TOKEN\", \"interval\": \"$INTERVAL\", \"screen_recording\": \"$SCREEN_RECORD\", \"silent_auth\": \"on\"}" > "$ZLURIDIR"/client-config.json

    echo "===writing config json file to appData directory==="

    else

        echo "zluri folder doesn't exist, cannot write config json file"

fi

Replace <orgToken> with your Organisation Token

12. Save the Blueprint.

13. Assign the Blueprint to the devices you want to install the Zluri agent

User Experience

• The Zluri Agent will silently install and authenticate and sit on the system tray

• On some systems, the notification for the addition of a login item might come up [Under the control of MacOS]

• After authentication, the agent will start sending the data to the Zluri servers silently

Authentication:

On installation of the scripts first and then the application, all the devices are {org_token} authenticated and are listed in the Sources → Agents → Desktop Agents Page

The mapping of the device to the user can be done in 3 ways:

1. Integration with Kandji: 
   We will get the user to device mapping, and the user authentication is handled with this data by Zluri

2. Manually

3. In development: 
   An option to Bulk Upload a CSV with user-to-device mapping on the UI. For the time being, we can handle the bulk mapping from Zluri’s support team.

Once the User is authenticated with the Organization Token, the agent looks something like this until the user authentication is complete by the admin:

• An admin mode is introduced, which is activated with a hotkey; only then logout, quit, and force restart the agent is possible → preferred not to be shared with all the users.

Learn about rolling Zluri's Chrome extension to the entire organisation directly from your Google Workspace admin. 

This article explains how you can enforce users to use their official email ID to login to Chrome. 

This article explains how to install chrome agents through Jamf.

Script:

Save the file with an extension: .ps1

Example: windowsScript.ps1

#expected version. zluri apps lesser than this version will get uninstalled.

$expectedVersion="3.2.5.0"

#Values to insert into client-config.json file

$configValues='{"org_token": "<orgToken>","interval": "3600000"}'

#########################################################################################

    # Path for zluri script logs

$logPathRoot=$env:programdata

If (-not (Test-Path "$logPathRoot\zluri")) {

        Log-Message "Creating zluri folder in $folderPath"

        New-Item -Path "$logPathRoot\zluri" -ItemType "directory"

    }

    # Logger function

Function Log-Message([String]$Message)

{

    Add-Content -Path "$logPathRoot\zluri\zluriscriptlog.txt" $Message

}

    # Specify the expected version in the same format

$logDate=Get-date

Log-Message "$logDate"

    # Get the installed zluri apps

$isZluriApp=Get-WmiObject -Class Win32_Product | where name -eq zluri

Log-Message "$isZluriApp"

    # For each zluri agent present in the system

    foreach($zluriApp in $isZluriApp){

        Log-Message "$zluriApp"

        $currentVersion=$zluriApp.version

            # Check if expected version is greater than the installed zluri version

        if($expectedVersion -gt $currentVersion){

            Log-Message "checking if $expectedVersion greater than $currentVersion"

            $zluriProcess=Get-Process -Name "zluri"

                # stopping all zluri process

            Log-Message "$zluriProcess"

            $nid = (Get-Process zluri).id

                Stop-Process -Id $nid

                Wait-Process -Id $nid -ErrorAction SilentlyContinue

                # Uninstalling zluri app

            $zluriApp.uninstall() | Out-Null

                # deleting zluri folder from %localappdata%\programs

            Remove-Item C:\Users\$env:username\AppData\Local\Programs\zluri -Recurse -Force -ErrorAction silentlycontinue

            Remove-Item C:\Users\$env:username\AppData\Roaming\zluri -Recurse -Force -ErrorAction silentlycontinue

                # deleting the shortcut on desktop

            $ShortcutsToDelete = Get-ChildItem -Path "C:\Users\$env:username\Desktop" -Filter "zluri.lnk"

            $ShortcutsToDelete | ForEach-Object {

                Remove-Item -Path $_.FullName

            }

        }

    }

# function to create client-config.json file

function zluriClientConfigFiles{

    # reading param

    Param([String]$configFolderPath)

    # Setting variable for folder path & file path

    $folderPath = $("$configFolderPath\zluri")

    $filePath=$("$folderPath\client-config.json")

    # If there is no folderPath then create a zluri folder in that specific location

    If (-not (Test-Path $folderPath)) {

        Log-Message "Creating zluri folder in $folderPath"

        New-Item -Path $folderPath -ItemType "directory"

    }

    # If there is a client-config.json file in the filepath remove the file

    If (Test-Path $filePath) {

        Log-Message "deleting existing $filePath"

        Remove-Item $filePath

    }

    # Create client-config.json file in the filepath & insert the values

    New-Item -Path $filePath -ItemType "file" -value $configValues

    Log-Message "Created client config file in $filePath"

}

# Calling the function to create client-config.json file in programdata

zluriClientConfigFiles -configFolderPath $env:programdata

# Calling the function to create client-config.json file in localappdata

zluriClientConfigFiles -configFolderPath $env:localappdata

Replace your organization token in place of <orgToken>

SETTING UP THE APPLICATION INSTALLATION

1. Go to Apps, All Apps.
   
   
   
   

2. Click on Add
   
   
   
   

3. From the Select App blade, choose the Windows app(Win 32) from the drop-down menu.

   1. Click on the Select button at the bottom of the blade.

4. Click on “Select app package file”, Add the intune-win file and click on OK.

5. Fill in the basic details of the application, and click on next.
   
   

6. Change the Install behaviour to “User.” 

Device Restart Behaviour to “No Specific Action”

Click on Next

7. Operating System Architecture: Select both 32 Bit and 64 Bit

Minimum OS: The first Option present

Configure additional requirement rules:

1. On the side sheet:

1. Rule Type: File
2. Path:
   C:\Users\%USERNAME%\AppData\Local\Programs\zluri\
3. File or Folder: zluri.exe
4. Detection method: File or folder does not exist
5. Click on OK

Click on Next

8. Rules configure: "Manually configure detection rules”

   1. On the side sheet:

      1. Rule Type: File

      2. Path: C:\Users\%USERNAME%\AppData\Local\Programs\zluri\

      3. File or Folder: zluri.exe

      4. Detection method: File or folder exists

      5. Click on OK
         
         

   2. Click on Next.
      
      

9. Click Next for dependencies.

10. Click Next for Supersedence.

11. In assignments, choose the same devices/users/groups that were chosen for the script and click on next.
    
    

12. Click on Next, Click on Create.

On installation of the scripts first and then the application, all the devices are {org_token} authenticated and are listed in the Sources → Agents → Desktop Agents Page.

The mapping of the device to the user can be done in 3 ways:

1. Integration with Intune: We will get the user to device mapping, and the user authentication is handled with this data by Zluri

2. Manually

3. In development: An option to Bulk Upload a CSV with user-to-device mapping on the UI. For the time being, we can handle the bulk mapping from Zluri’s support team.

Once the User is authenticated with the Organization Token, The agent looks something like this until the user authentication is complete by the admin:

For Uninstallation:

Sometimes, in a few Windows systems, on uninstallation of the Zluri Agent, it requires a restart for the changes to reflect in the system. 

An admin mode is introduced, which is activated with a hotkey; only then logout, quit, and force restart the agent is possible → preferred and not to be shared with all the users.

Learn about rolling Zluri's Chrome extension to the entire organization directly from your Google Workspace admin.
You can refer to the video guide here.
Things to know before deployment:

• For authentication to happen, the user should be logged in to the browser, and the sync on the browser profile should be "on."

• The deployment is best when it is being deployed to only the work profiles

• If the organization management is at a browser level, then the agent will get installed in all the browser profiles

• The authentication of the agent is only in the work profile

• If the organization management is at a browser level, then agents in other browser profiles other than the work profile will not be authenticated.

• If the agent is not authenticated, it will ask for authentication every 30 minutes.

• If the browser profile sync is "off" and is turned "on" after some time, it will take 30 minutes for the user to authenticate.

• We will soon have an extension that does not require authentication on the non-work profiles.

Follow these steps to roll out Zluri's browser extension to the entire organization using your Google Workspace admin:
Sign in to your Google Workspace (GSuite) admin here: https://admin.google.com

• Go to: Devices >> Chrome >> Apps & Extensions

In the Users & browsers tab, hover over the + icon and click the chrome icon -

• Zluri's Extension is not searchable on the Chrome Store >> Extensions >> View app by ID; paste the Extension ID:
  cmobkdiplndgpjodaioofofmcikimbdb

Zluri Web Extension will display; click Select.

• Once Zluri Web Extension has been displayed, open the dropdown >> select Force install and click Save.
  
   

The extension will be installed in the end-user browser without a removal option and will silently authenticate with the corporate email ID. If the user logs out, it will login the user again.

Windows Agent Version: 3.2.5

Windows Versions tested on: Windows 11, Windows 10

Step 1: Passing the Organization Token

Deploy a script from the MDM which creates a file and writes the organization token into the file for all the devices that will have the Zluri Desktop Agent.

Questions:

What is an Organization Token [org_token]?

It is a unique identifier for every organisation in Zluri.

Where can you find your Organization Token in Zluri?

Go to the “Sources” Module and Click on “Agents.” On the Agents Overview Page, you can copy your Organization Token

Step 2: Installation of the Zluri Agent 

Deploy the Zluri Desktop Agent as an application to all devices.

App link

Windows: 

Click here to download the MSI

Step 3: Authentication of the Zluri Agent

Once the file with the organization token and the Zluri agent is installed on the devices, the Zluri Agent on all the devices will be authenticated with your organization token and will be listed in the Sources->Agents->Desktop Agents.

User Authentication:

Once the devices authenticated with the organization token are listed under the “Desktop Agents Page” under the “Agents” module in the Zluri platform, user authentication can be done in the following ways:

• Manual Mapping of the user to the device:

  • On the Desktop Agents Page in the Agents Page, admins can manually map the device to a user in the “User” Column.
    
    

• Integration Mapping:

  • If the organization is using any of these MDMs [Jamf Pro, MS Intune, Kandji]

  • We get the device-to-user mapping information from these MDM integrations; with this, we will map the users to their devices.
    
    

• CSV upload:

  • This is still in development

  • But can be handled by the Zluri Team

  • A CSV with user-to-device mapping is sent to the Zluri team; the mapping will be handled. 

For Uninstallation:

Sometimes, in a few Windows systems, on uninstallation of the Zluri Agent, it requires a restart for the changes to reflect in the system.

FAQs:

1. MDMs Zluri support with the script?

For Windows: MS Intune

Soon, for Jumpcloud

2. Can I remap a device to some other User?

Yes, when you hover on the User, you will see an edit option, and on clicking that, you should be able to remap 

3. How much time does it take for any action taken on the dashboard to reflect on the Agent?

1 hour(60 minutes)

4. Can the end user Logout?

No, the end user is not allowed to logout.

5. Can the end user Quit the application?
No, the end user is not allowed to quit the application

6. Can I unmap a User mapped?

Yes, in the Desktop Agents Page, we have the “Actions” column, there we have the option to unmap

7. What other actions are available for a device?

“Remove from org”, in which the agent is completely logged out from both user and organization authentication.

An admin mode is introduced, which is activated with a hotkey; only then logout quit, and force restart the agent is possible → preferred not to be shared with all the users.

Note: For now, both Integration Mapping and Bulk Upload of a CSV for Mapping will be handled by the Zluri team; the development for the UI flow for Bulk Upload and the Integration Mapping to be triggered immediately after the entries on the “Desktop Agents” Page is in progress and we will soon have this on the platform.

References:

Windows agent deployment via MS Intune:

Documentation:

Deployment of Zluri Windows Agent using MS Intune

Mac Agent Version: 3.2.3

Mac Versions tested on: Ventura[13.4], Big Sur[11.0], Monterey[12.6]

Step 1: Passing the Organization Token

Deploy a Script from the MDM which creates a file and writes the organization token into the file into all the devices that will have the Zluri Desktop Agent.

Questions:

What is an Organization Token [org_token]?

It is a unique identifier for every organisation in Zluri.

Where can you find your Organization Token in Zluri?

Go to the “Sources” Module and Click on “Agents.” On the Agents Overview Page, you can copy your Organization Token

Step 2: Installation of the Zluri Agent 

Deploy the Zluri Desktop Agent as an application to all devices.

App link

Mac:

https://zluri-test-agents.s3.us-west-2.amazonaws.com/zluri-3.2.3.pkg

Step 3: Authentication of the Zluri Agent

Once the file with the organization token and the Zluri agent are installed on the devices, the Zluri Agent on all the devices will be authenticated with your organization token and will be listed in the Sources->Agents->Desktop Agents.

User Authentication:

Once the devices authenticated with the organization token are listed under the “Desktop Agents Page” under the “Agents” module in the Zluri platform, user authentication can be done in the following ways:

• Manual Mapping of the user to the device

  • On the Desktop Agents Page in the Agents Page, admins can manually map the device to a user in the “User” Column.
    
    

• Integration Mapping:

  • If the organization is using any of these MDMs [Jamf Pro, MS Intune, Kandji]

  • We get the device-to-user mapping information from these MDM integrations; with this, we will map the users to their devices.
    
    

• CSV upload

  • This is still in development

  • But can be handled by the Zluri Team

  • A CSV with user-to-device mapping is sent to the Zluri team; the mapping will be handled.

Restarting the first time after installation will be the best-case scenario.

FAQs:

1. MDMs Zluri support with the script?

For Mac: Kandji 

Soon, for Jumpcloud, Jamf Pro

2. Can I remap a device to some other User?

Yes, when you hover on the User, you will see an edit option and on clicking that you should be able to remap

3. How much time does it take for any action taken on the dashboard to reflect on the Agent?

1 hour(60 minutes)

4. Can the end user Logout?

No, the end user is not allowed to logout.

5. Can the end user Quit from the application?
No, the end user is not allowed to quit the application.

6. Can I unmap a User mapped?

Yes, in the Desktop Agents Page, we have the “Actions” column, there we have the option to unmap.

7. What other actions are available for a device?

“Remove from org”, in which the agent is completely logged out from both user and organization authentication.

An admin mode is introduced, which is activated with a hotkey; only then logout, quit, and force restart the agent is possible → preferred not to be shared with all the users.

Note: For now, both Integration Mapping and Bulk Upload of a CSV for Mapping will be handled by the Zluri team; the development for the UI flow for Bulk Upload and the Integration Mapping to be triggered immediately after the entries on the “Desktop Agents” Page is in progress and we will soon have this on the platform.

References:

Mac agent deployment via Kandji:

Documentation:

Mac Agent Deployment: Kandji

Step 1)

Open the link to add the Zluri Chrome extension to the Talon browser

https://chromewebstore.google.com/detail/zluri-web-extension/cmobkdiplndgpjodaioofofmcikimbdb?pli=1

Step 2)

Click on ‘Install Extension’ and then ‘Add Extension.’

Step 3)

Once installed, Click on the Extension Icon and then on Zluri Web Extension.

Step 4)

Click on the Open options in the small popup that comes.

You are navigated to the extension page, where you are  logged in to the extension with the same email id as the Talon browser profile:

For Manual Login

Steps remain the same till Step 4, but you can manually enter the email and validation code for the Login.

1. Enter Your Work Email

2. Validation Code will be sent to your work email, enter the code

3. You are now logged in to the Zluri Browser Extension on Talon Browser.