Detection profiles, categories, and levels
How profiles, categories, and levels work together per organization and per app.
Detection Profiles
Choose which sensitive data BeeSensible detects per app, and how strictly
| Entity | Level | Enabled |
|---|---|---|
| Email address | Standard | |
| Full name | Standard | |
| Phone number | Standard | |
| Street address | Standard | |
| IBAN | Critical |
A detection profile controls which types of sensitive data BeeSensible detects and how strongly they are highlighted.
Profiles are managed under Detection Profiles in the admin dashboard.
Levels
| Level | Highlight | Meaning |
|---|---|---|
| Standard | Yellow | Regular warning |
| Critical | Red | Higher-sensitivity detection |
| Disabled | None | This entity type is not highlighted |
Categories
BeeSensible detects sensitive data in categories such as identity, contact details, financial data, technical credentials, and other sensitive information. You configure which entity types are active per profile.
Default profile and app profiles
Every organization has a default profile. Apps can also have their own profile. Without an app-specific profile, an app uses the default profile.
Create a profile
- Open Detection Profiles.
- Create a new profile or open an existing one.
- Choose which entity types are enabled.
- Choose Standard or Critical for each enabled type.
- Save the profile.
Assign a profile to an app
Apps are assigned inside the profile, under Where this profile applies:
- Open the profile.
- Under Where this profile applies, tick the apps that should use it.
- Save. Apps you did not tick keep using the default profile.
See Apps and websites for the full flow.
Recommended starting points
| Use case | Starting point |
|---|---|
| External AI tools | Identity, financial data, and credentials on Critical |
| Identity on Standard, financial data and credentials on Critical | |
| Chat | Financial data on Critical, identity on Standard |
| Internal tools | Credentials on Critical, other categories only where needed |
Use these as a baseline and tune them after the first usage period.