@AnnLyn wrote:
I know that we should define a ACT but is it possible to secure library and the users still have write and delete access to data below.
Assuming you're talking about SAS metadata:
If you don't have a security model that uses ACT's then it feels this model needs some improvement.
You could definitely secure the library metadata from deletion while still allowing to register/modify table metadata for this library. Easiest would be to store the library metadata object in a different folder.
Having said that: In a prod environment "normal" users should likely not be allowed to modify metadata at all. In a DEV environment: I'm of the opinion that developers need to take some responsibility and that admins shouldn't secure things too much as it can complicate justified developments activities. If there are developers who create "a mess" then this needs eventually to be addressed via training instead of tightened security.