Desktop Agent Deployment: Anonymous Users

This guide outlines how partners can deploy Produce8 to automatically create anonymous user profiles and begin collecting activity data—without requiring users to sign in.

Who This Is For

This deployment flow is intended for:

  • Partner accounts setting up Produce8 for the first time

  • Teams that want to collect data without requiring users to sign in

  • Scenarios where users may never engage directly with Produce8

1. Set Up Account Settings for App & User Discovery

Before deploying to users, configure the account settings to enable automatic app and user discovery.

If you’re deploying to a customer, start by creating their customer account in the Partner Centre. Then log into that account and configure the following:

Enable App Discovery

To automatically detect desktop and browser apps:

  1. Select your user icon in the bottom-left corner of the Produce8 Web App.
  2. Choose Account Settings from the menu.
  3. On on the General page, scroll down to App Discovery Settings.
  4. Toggle the settings to On.
Screenshot 2025-05-12 at 2.37.51 PM

 

Once enabled:

  • Apps in use will appear in a pending state on the App Administration page

  • Admins must approve apps before data collection begins

  • Ignored apps are excluded from insights and reports

Screenshot 2025-05-12 at 2.52.11 PM

📘 Learn more in Automatic App Discovery

Enable Automatic User Discovery

To create anonymous profiles automatically for users on deployed systems:

  1. In the same Account Settings → General section, scroll to Automatic User Discovery

  2. Toggle the setting to On

image (3)

Once enabled:

  • An anonymous user profile will be created for each active system user on any deployed device

  • This allows for early data collection without requiring immediate user sign-in

  • Anonymous Data Collection is enabled by default when this is on

⚠️ Note: Anonymous users will not be created if the account has already reached its user limit.

📘 Learn more in Automatic App Discovery 

2. Deploy the Desktop Agent and Browser Extensions via RMM

Once your settings are configured, deploy the Produce8 Desktop Agent and Browser Extensions using your preferred RMM tool.

OS Architecture Package Type URL Sample Script
Windows ARM64 MSI https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/msi/arm64/Produce8-Agent-latest.msi https://github.com/Produce8/scripts/blob/main/PC/Agent/Install-Produce8-Agent.ps1
Update url for the agent and account id.
Windows ARM64 EXE https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/exe/arm64/Produce8-Agent-latest.exe https://github.com/Produce8/scripts/blob/main/PC/Agent/Install-Produce8-Agent.ps1
Update URL for the agent and account id.
Windows x64 MSI https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/msi/x64/Produce8-Agent-latest.msi https://github.com/Produce8/scripts/blob/main/PC/Agent/Install-Produce8-Agent.ps1
Update url for the agent and account id.
Windows x64 EXE https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/exe/x64/Produce8-Agent-latest.exe https://github.com/Produce8/scripts/blob/main/PC/Agent/Install-Produce8-Agent.ps1
Update url for the agent and account id.
MacOS ARM64 DMG https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/dmg/arm64/Produce8-Agent-latest.dmg https://github.com/Produce8/scripts/blob/main/Mac/Agent/install.sh
Update url for the agent as needed
MacOS ARM64 PKG https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/pkg/arm64/Produce8-Agent-latest.pkg Mac/Agent/install.shProduce8/scripts Update url for the agent as needed
MacOS x64 DMG https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/dmg/x64/Produce8-Agent-latest.dmg https://github.com/Produce8/scripts/blob/main/Mac/Agent/install.sh
Update url for the agent as needed
MacOS x64 PKG https://desktop-agent-assets-main.s3.us-west-2.amazonaws.com/main/pkg/x64/Produce8-Agent-latest.pkg https://github.com/Produce8/scripts/blob/main/Mac/Agent/install.sh
Update url for the agent as needed

 

Once deployed:

  • The agent will auto-launch in the background

  • An anonymous user profile will be created for the active user

  • These users will appear under Account Settings → User Management

Screenshot 2025-05-13 at 3.08.16 PM

Mac OS Deployment Note

Before deploying the agent on Mac:

  • Add the account.properties file to:

    /user/Library/Application Support/Produce8-agent

  • Include your account ID (from Account Settings → General) in the file:

account.accountId=your-account-id-here

Screenshot 2025-05-02 at 3.22.45 PM

Browser Extension Deployment

Browser extensions are required to capture activity in tools like Google Docs, Outlook Web, or Slack.

Browser Plugin Link Plugin ID Sample Script - Windows Sample Script - Mac
Chrome https://chromewebstore.google.com/detail/produce8-agent/kjdhkfobigjnlanlfjakbbibdbakdcnc kjdhkfobigjnlanlfjakbbibdbakdcnc Use Intune or the following script: PC/BrowserPlugin/Chrome/Install-Chrome-Plugin.ps1Produce8/scripts  
Firefox https://addons.mozilla.org/en-CA/firefox/addon/produce8-agent/ support@produce8.com (id) {2170649e-9ff0-4923-b6a5-60077ca1675d} (syncGUID) Use Intune or the following script:  
Edge https://microsoftedge.microsoft.com/addons/detail/produce8-agent/clfmhpehigjmbgobgdebalogdgohbafk clfmhpehigjmbgobgdebalogdgohbafk Use Intune or the following script: PC/BrowserPlugin/Edge/Install-Edge-Plugin.ps1Produce8/scripts  

 

Deployment Notes:

  1. Extensions can be pushed using Intune or similar tools
  2. If Intune isn't available, PowerShell scripts can also be used
  3. Extensions must be installed in the browser(s) your users actively use

Where to Find Deployment Scripts

Deployment scripts for the Desktop Agent, Browser Extensions, and Desktop App are available within the Produce8 Web App.

📘 Learn more How to Find Scripts in Produce8

3. (Optional) Deploy the Produce8 Desktop App

The Desktop App is not required for anonymous data collection. However, if users may sign in later, you can deploy it during the initial rollout.

OS Architecture Package Type URL Sample Script
Windows x64 MSI https://p8desktopapp-v2-main.s3.us-west-2.amazonaws.com/%40cyclops/desktopapp/main/win32/x64/Produce8.msi https://github.com/Produce8/scripts/blob/main/PC/DesktopApp/Install-Produce8-App.ps1
Windows ARM64 MSI https://p8desktopapp-v2-main.s3.us-west-2.amazonaws.com/%40cyclops/desktopapp/main/win32/arm64/Produce8.msi https://github.com/Produce8/scripts/blob/main/PC/DesktopApp/Install-Produce8-App.ps1
MacOS x64 DMG https://p8desktopapp-v2-main.s3.us-west-2.amazonaws.com/%40cyclops/desktopapp/main/darwin/x64/Produce8.dmg  
MacOS ARM64 DMG https://p8desktopapp-v2-main.s3.us-west-2.amazonaws.com/%40cyclops/desktopapp/main/darwin/arm64/Produce8.dmg  

 

If deployed:

  • Users can log in via Google/O365 SSO or email and password

  • Once signed in, their anonymous profile will automatically convert to a signed-in user

This allows you to start with passive observation and optionally transition users to an interactive experience later.

4. Review and Approve Discovered Apps 

Once users begin working with the Desktop Agent and browser extensions installed, apps will begin appearing in the App Administration section in a “pending” state.

As an admin or owner, you’ll need to:

  • Approve apps to begin collecting activity

  • Ignore apps to exclude them from reports

  • You can update these choices at any time

Screenshot 2025-05-12 at 2.52.11 PM

📘 Learn more in Automatic App Discovery 

What to Expect After Deployment

  • Anonymous users will be created automatically for each device

  • These users will appear in Account Settings → User Management

  • Devices will begin reporting activity via heartbeat to Account Settings → Account Health → Devices

  • No data will be collected until at least one app is approved

image (2)-png

Technical Notes & Best Practices

  • Add a step in your RMM script to quit and restart the agent after installation

  • If you use endpoint protection (e.g. SentinelOne), be sure to whitelist the agent and app

  • Track deployment success by checking:

    • User Management for new users
    • Account Health → Device for heartbeat data

Example RMM Scripts