File type restrictions within Beekeeper app

Beekeeper provides users with the capability to upload, share or attach files in various features within the product, such as:

• Streams
• Chats
• Campaigns
• Document Library
• Workflows
• Tasks
• Shortcuts
• Forms
• Surveys
• Shifts
• User Uploads

To enhance the security and reliability of the Beekeeper platform, we have introduced a new feature limiting the file types that can be uploaded in the app. This feature was enabled by default on 29th July 2025.

What Has Changed?

With this update, Beekeeper blocked the upload of files with certain high-risk or executable extensions across all modules that support file importing.

This new file extension disallow featuret aims to prevent the upload of potentially harmful or unsupported file types and ensures a safer experience for all users across the platform.

Blocked File Extensions

The following file types are no longer accepted once the feature is enabled:

.ade, .adp, .app, .appcontent-ms, .application, .appref-ms, .asp, .aspx, .asx, .bas, .bat, .bgi, .cab, .cdxml, .cer, .chm, .cmd, .cnt, .com, .cpl, .crt, .csh, .der, .diagcab, .exe, .fxp, .gadget, .grp, .hlp, .hpj, .hta, .htc, .img, .inf, .ins, .iso, .isp, .its, .jar, .jnlp, .js, .jse, .ksh, .lnk, .mad, .maf, .mag, .mam, .maq, .mar, .mas, .mat, .mau, .mav, .maw, .mcf, .mda, .mdb, .mde, .mdt, .mdw, .mdz, .mht, .mhtml, .msc, .msh, .msh1, .msh1xml, .msh2, .msh2xml, .mshxml, .msi, .msp, .mst, .msu, .ops, .osd, .pcd, .pif, .pl, .plg, .prf, .prg, .printerexport, .ps1, .ps1xml, .ps2, .ps2xml, .psc1, .psc2, .psd1, .psdm1, .pssc, .pst, .py, .pyc, .pyo, .pyw, .pyz, .pyzw, .reg, .scf, .scr, .sct, .settingcontent-ms, .shb, .shs, .theme, .tmp, .url, .vb, .vbe, .vbp, .vbs, .vhd, .vhdx, .vsmacros, .vsw, .webpnp, .website, .ws, .wsb, .wsc, .wsf, .wsh, .xbap, .xll, .xnk

Why This Matters

Security is a top priority at Beekeeper. By disallowing executable and potentially unsafe file types, we help prevent malicious uploads and reduce the risk of operational issues caused by unsupported formats. This change aligns with industry best practices for enterprise-grade platforms and strengthens overall compliance and trust across our ecosystem.

We want you to stay safe and secured.