Bitwarden elastic integration


The official bitwarden elastic integration seems to require an organization API key in order to function. This seems a little excessive for Policy, Group, Collection, and Event logs. Is there any way to use a less privileged API key or to reduce the permissions of the organization key used within elastic or are organization keys unable to have granular permissions associated with them?

Hi @gurjie and welcome to the Bitwarden community! Thanks for sharing this input. Currently this functionality is connected to Teams and Enterprise plans, including a single user. That could change although there are no plans or timetable at the moment.