Hi Anupama,



The problem here is that when you try to upload the new file on your "file" Field in the "Vault Technology Asset"  content type. The new file is going to be saved as a default "File Asset" and not as your "Vault File Asset"  content type that the limited user has permissions. That's why you get the permissions error message in the log.



In this case, you can:



1) Instead of using a "File" Field on your "Vault Technology asset" use a "Binary" Field. that will help you to avoid to have another content type just to save the file.





2) If you still need the "Vault File Asset" content type for the files then: the limited user should add the file ("Vault File Asset") first using the upload file option on the site browser or on the content search as you did or using WebDAV setting in the folder with default file asset set to your "Vault File Asset") and then create the "Vault Technology asset" content and select one of the files listed in your /technology/ folder.



or



3) Give access to the "Technology "role to publish on the default "File Asset" content type. The only thing, in this case, is that the file is going to be created with another content type that is not the "Vault File Asset" and the user will see other files assets that maybe you don't want to.



Regards,

  Oswaldo