Lack of read-only roles causes scaling issues with InfluxDB adoption in large organizations

Currently, InfluxDB Cloud has only one permission level for users: Owner . With Owner permissions, a user can delete resources and other users from your organization. Take care when inviting a user.

That’s not helpful. This prevents InfluxDB from safely being used in teams larger than a handful of people. When will we get read-only roles?

Will version 3 (Core? Enterprise? Cloud?) feature true, differential roles? The documentation for v3 Influx offerings doesn’t appear to even have pages about users, compared to documentation for v2.

@Pete_InfluxData do you have any insight if this is for the roadmap for v3?
Thanks!