No Children to Pick from
You fix the no children to pick from error by adding read roles to child folders. You must also verify that child nodes exist under the parent group. Platform teams often see this blank list when they set up cloud folders or database trees. To move fast, admins often grant broad parent roles to the whole team. Those wide roles let users read and change every child item without limits. Why the no children to pick from message appears Cloud platforms and database tools store items in a parent a
End-to-End Encryption: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You fix the no children to pick from error by adding read roles to child folders. You must also verify that child nodes exist under the parent group. Platform teams often see this blank list when they set up cloud folders or database trees. To move fast, admins often grant broad parent roles to the whole team. Those wide roles let users read and change every child item without limits.
Why the no children to pick from message appears
Cloud platforms and database tools store items in a parent and child tree. A top account holds sub-accounts, folders, or database groups. When a user clicks a parent item, the app asks the backend for child items. If the backend returns an empty list, the screen shows no children to pick from.
Two main issues cause this empty list in your app. First, the parent item might be an empty shell with no child items inside it. Second, the user role might allow reading the parent name but block listing child items. Many systems split the rule for viewing a parent from the rule for listing its children.
To fix this in your native setup, check the parent item first. Log in with an admin role and verify that child items exist in that group. Next, check the role tied to the user who saw the error. Add the specific list or view permission for child items to that role. Save the role update and ask the user to refresh their screen.
How to scope parent and child permissions
When teams fix this error, they often attach a full admin role at the parent level. Most cloud trees pass parent permissions down to every child item by default. If you grant write rights at the top, the user gets write rights everywhere below it. This quick fix clears the error message right away, but it creates a big security risk.
Instead of broad parent roles, split your rules into two clear parts. Create a basic browse role at the parent level that only lists child names. Then grant read or write roles on the specific child items each person needs. This setup lets the user see the folder tree without opening every single resource to changes.
End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native folder roles solve and what they miss
Native parent and child roles control who can see items in a menu and log in. They help you organize accounts and stop users from seeing teams they do not belong to. Setting up clean list rules fixes the picker menu and keeps your folder tree tidy.
Still, native role trees only check permissions when a user opens a menu or starts a session. Once a user picks a child database or server, the native role steps back. It does not check the specific commands or queries the user runs inside that child resource. If a developer has read rights on a child database, they can pull full tables with emails or card numbers. Static folder roles also stays active all day, even when the user finishes their task. Teams still need a way to inspect live commands and mask sensitive fields in query results.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
What does no children to pick from mean in a folder menu?
It means the parent item has no sub-items or your role lacks list rights. The app cannot find any child items your account is allowed to view.
How do I let users pick child items without giving full admin rights?
Assign a list-only role on the parent folder so the menu loads child names. Then grant read or write roles only on the specific child items the user needs.
Why did my child items vanish after a role update?
The update likely removed the list or browse rule from your parent folder role. Ask an admin to restore the list permission on the parent group and refresh your app.