Deny Read Permission to Buckets for Org Members

InfluxDB 2
1

I would like to allow read and write permissions to buckets in an organization on a user-by-user basis, using either InfluxDB OSS or InfluxDB Cloud.

Here’s what I’ve noticed:

  1. If I use PostBucketsIDOwners, this indeed grants write access to buckets for individual users in the org.
  2. If I use PostOrgsIDMembers, this grants default read permission to all buckets in the org for members added in this way.
  3. If I do step (1) and not (2) for a user, that bucket is created but the user cannot see it in the InfluxDB UI.
  4. I have experimented with the Authorizations API but this doesn’t appear to have any effect.

Is there any way for me to allow or deny read access to individual buckets within an org on a member-by-member basis?

2

Hello @balsa,
So just to clarify, you’d like to do step 3 but for the bucket to exist in the UI?
Or you want this:

Is there any way for me to allow or deny read access to individual buckets within an org on a member-by-member basis?

But for the UI?

3

Specifically, I’d like to be able to set up an org where users are granted read permissions to buckets on a user-by-user basis, and for that to be reflected in the UI. What I’ve noticed is that membership in an org gives a user read permissions to all buckets in the org regardless of anything else I do.