admin management

[ltan10]

As there is no admin portal on the UI for shellhub community edition.

Is there any way to list available users, and or namespaces?
./bin/cli does not offer any of those features.

[gustavosbarreto]

@ltan10 You're right, there's currently no admin portal or CLI command to list users and namespaces in the Community Edition. The CLI is limited to create/delete operations at the moment.

Could you share more about your use case? Are you looking for a quick way to inspect your instance (in which case querying MongoDB could work as a workaround), or do you think this should be implemented as a proper CLI feature?

We're open to feedback on this and would like to understand what would be most useful before pointing you in a direction.

[ltan10]

Thanks for confirming.

Our prospective use case is we will have multiple namespaces with small number of devices in each namespace.
So potentially users will scale with namespaces.

Ideally would like to be able to have a central point to view all users, namespaces and devices. Which based off the screenshot from.
https://shellhub-io.github.io/admin-manual/admin-console/ it does appear to have ability to show all users and devices.

I am unsure if the admin console shows which namespaces each user belongs to as i don't have the feature to test.

I understand the idea to gate access to the admin console.
Just thinking out loud, if it may be more efficient in the long run to make basic access of the admin-console available in the community edition. i.e bring the CLI features into UI and leave the current CLI as a second last resort before delving into databases.

It would present a more unified experience for users and would reduce the development of parallel tools.

[otavio]

Thanks for sharing the details about your use case — managing multiple namespaces with smaller device counts per namespace is a common pattern we see as deployments grow.

You raise a fair point about the admin experience in the Community Edition. Today, the admin console is only available in Cloud and Enterprise editions, which means Community users are left querying MongoDB directly for basic visibility into users and namespaces. That's not a great experience, and we agree the CLI should be a more capable tool before anyone needs to reach for the database.

It's also worth noting that we're in the process of migrating our storage backend from MongoDB to PostgreSQL, so relying on direct database queries as a workaround today would become a moving target. That's another reason we want to provide proper tooling for this.

We're planning to improve the admin experience. The approach we're considering is to add basic admin CLI commands (listing users, namespaces, and devices) to the Community Edition. This gives self-hosted users the operational visibility they need without requiring direct database access. The full admin console UI with advanced management capabilities would continue to be part of the Cloud and Enterprise editions.

We don't have a timeline to share yet, but this is on our radar. If you have specific admin operations you find yourself needing most often, feel free to list them here — that helps us prioritize what to build first.

Also, given your scenario — multiple namespaces, growing user base, and the need for centralized management — have you considered the Enterprise edition? It supports self-hosted deployments as well, so you'd keep full control of your infrastructure while getting access to the admin console and advanced management features out of the box. Happy to share more details if that's something worth exploring for your setup — you can reach us at https://www.shellhub.io/contact.