You'll want to implement an admin or policy capability pattern. Create a unique capability object within the package that should have exclusive update rights. Then, have all the update functions for the shared object require a reference to this capability object as an argument. This way, only the owner of that specific capability can call those update functions, effectively restricting edits to your package.

Para garantizar que solo un paquete específico pueda actualizar un objeto compartido, puedes usar patrones como el control de remitentes o capacidades. Una forma es implementar un patrón de capacidad, en el que se permiten las actualizaciones en función de la propiedad de un objeto. Como alternativa, puede crear una lista de control de acceso (ACL) para permitir que solo determinadas direcciones interactúen con los métodos del paquete. Estos métodos se detallan en recursos como la documentación sobre los patrones de capacidad y la regla de la lista de denegación, que se pueden consultar aquí y aquí.

To make sure only a specific package can update a shared object in Sui Move, you need to build in access control directly into your smart contract logic. One way to do this is by using a capability pattern, where you create a special object that acts like a permission slip—only the package that holds this object can make changes. You can also check the sender’s address during a transaction and allow updates only if it matches the expected package address. Another option is to include an access control list inside the shared object itself, listing which addresses are allowed to make edits. These methods help you lock down the object so that other modules or packages can’t tamper with it.