Queue ownership - super Admin

Regarding “Non-Owner Permission” on a queue.

We would like to have a super admin that can read and consume any queue in the broker.

Is there any way to have a super admin that can read or consume any queue even the non-owner permissions is set to no-access?

Another way would be to have multiple owners for a queue, but it seems it is, for the moment, not supported.
(Queue Authorizations)

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Looking at the documentation, I can explain how queue permissions and ownership work:

The queue owner has full unlimited permissions for the queue - they can consume, delete, and modify topics in the queue. Queue ownership is established in the following ways:

  1. For client-provisioned queues: The client username associated with the client that creates the queue automatically gets ownership
  2. For CLI/admin-provisioned queues: No client username automatically gets ownership (defaults to “management”)
  3. CLI users with read-write or admin access to the Message VPN have full permissions on the queue (management ownership)

For non-owner access, you can configure one of these permission levels:

  • no-access: Disallows access to the queue
  • read-only: Read-only access to messages
  • consume: Can read and delete messages
  • modify-topic: Can consume messages and modify topic subscriptions
  • delete: Can consume messages, modify topics, and delete the queue

So to answer your specific question - there is no concept of multiple owners or a “super admin” that can override the non-owner permissions. The queue owner and Message VPN administrators have full access, while all other users are restricted by the configured non-owner permission level.

Relevant documentation: