Detection profiles
Which data BeeSensible recognises in apps and documents, and how strictly: levels per data type, the default profile, and where a profile applies.
Choose which sensitive data BeeSensible detects per app, and how strictly
A detection profile decides which data BeeSensible treats as sensitive, and how strictly, per data type. There is one kind of profile for apps and for documents: Documents sits in a profile as a target next to the apps, and separate document profiles do not exist. Profiles live under Policy > Detection profiles, tab Profiles.
Detection profiles in the dashboardThe profile list, with each profile's data types, its critical count, and where it applies.The default profile
Every organisation has one default profile, marked Default on the list. It applies to every app and document without a profile of its own; the card says so: "Applies to every app and document without its own profile." Assign an app, or Documents, to another profile and that target follows it from then on, while everything else keeps following the default.
A new organisation starts on BeeSensible default: "The profile BeeSensible provides", the same for everyone. To make it your own, click Customise. You get a copy named BeeSensible default (customised); once saved it applies to everything without its own profile, and the provided profile stays as it is. On the list, Set default makes any other profile the default.
Levels
For each data type you decide under Detect whether it counts, and under Level how strictly. The level sets the highlight people see, in the browser, in the desktop app and in the document review.
| Level | Highlight |
|---|---|
| Standard | yellow highlight |
| Critical | red highlight, high visibility |
| Off | no highlight |
The list holds all 65 data types Bombus knows, in 11 categories; see The detection engine. Group by category splits the list into groups such as Identity, Contact, Address, Financial, Medical and Technical, each with its own switch to turn the whole group on or off. Enable all and Disable all act on what is visible at that moment, so they work on a search result too.
Create a profile
Open the form
Click New profile. To start from an existing profile, open it and click Copy.
Name it
Name and description
| Field | What to enter |
|---|---|
| Profile name | Required; this name shows up in the list and in the AI register |
| Description (optional) | What the profile is for, such as "For EU customer data" |
Choose where it applies
Under Apps and documents, tick what should use this profile. Documents sits in the same list as the apps and picks the profile for everything people anonymise, in the dashboard, the extension and the desktop app. Each target shows where it sits now: On Default, or Moves from another profile. Apps labelled Web + desktop apply in the desktop app as well.
Choose which data to recognise
Under Which data to recognise, pick a starting point at Start from: either Default, which copies the default profile's choices, or Blank, which starts with everything off. Per row, tick Detect on or off and pick Standard or Critical under Level. Search data types finds a type by name or category.
Save it
The bar at the bottom keeps count: the number of data types, how many are critical, and the number of apps. Click Save profile.
Custom terms in a profile
Next to the Sensitive data tab, every profile has a Custom terms tab. There you decide per category (Project, Business relation, Person and the others) whether your organisation's own terms count in this profile, and at which level. The list of terms itself lives on the Custom terms tab next to Profiles; Manage list takes you there. See Custom terms.
Turn detection off for an app
The list also holds the profile No detection: "Apps assigned here are not scanned. BeeSensible detects and highlights nothing." It opens the Turn off detection screen. Remove an app again to protect it; it goes back to the default profile.
What the AI register shows
In the AI register every tool has a Detection profile column, and the tool page names the profile that applies: "Applies to ChatGPT, as set under Detection profiles." For a tool where BeeSensible does not help it reads: "BeeSensible does not help in this tool, so no detection profile applies." A change of profile lands in the tool's history.
The app I want to assign is not in the list
Apps appear once the extension reports activity for them. If an app your people use really is missing, use Request an app at the bottom of the list.
I want to edit the provided profile
BeeSensible default is read-only. Click Customise for your own default, or Copy for a separate profile.
See Apps and websites for how apps work in BeeSensible.
Last updated:
