To address this concern, you can design functions within your smart contract that restrict access to only admin users. By using transfer::share_object, your pool becomes a shared object accessible by everyone. However, you can implement access controls where only certain functions, like withdrawing or changing the balance, can be called by the admin. A shared object will allow you broad access, but with careful design of functions and permissions, you can ensure your pool remains secure.

The inclusion of capability-based permissions can help manage who can perform which actions on your shared object. Refer to resources like the official Move documentation or community guides such as the one found on move-book.com regarding programmability and capability handling.