Many companies build their own Revu profiles - tool sets, custom columns, classifications, production rates and formulas that hold years of estimating know-how - and install them on their staff's workstations, or license them to other firms.
Today anyone with access to Revu can take that profile with them: Revu > Profiles > Manage Profiles > Export takes two clicks, and the installed files can also be copied from %AppData%\Bluebeam Software\Revu\21\. Nothing in Manage Profiles, Bluebeam Administrator or the feature flags can prevent it.
Idea: let a profile's author mark a profile as PROTECTED, so that once installed:
(1) Export is disabled for that profile (the Export… button greyed out, including its tool sets and custom columns under Include Dependencies);
(2) a copied profile file will not import on another machine - for example stored encrypted and tied to the licensed Bluebeam ID or organisation;
(3) the organisation's administrator can see and control it (Bluebeam Administrator or Bluebeam Cloud).
This would make Revu safer for every company whose staff work with its profiles, and give profile authors a way to share their work without losing control of it. Happy to help test.