Comment 9 for bug 1569582

FYI, we decided on IRC that we would add a single reserved policy group for now, named 'bluetooth'. This will allow full access to bluez. This will be reserved in the first iteration because there are information leaks and the device can be placed into discovery mode. Other accesses were not investigated but are presumably present.

In the future, bluez will gain trust-store integration (with corresponding system settings updates) so that access to bluez can be safely granted to apps. We might leave 'bluetooth' as reserved and create new policy groups like bluetooth-file-transfer, bluetooth-input, etc.