For other purchased/vendor sourced parts, what lifecycles are more intuitive and less prone to break in vault? We use the default object based security but I cannot fully understand the feature as there are inconsistencies within our projects.
My team is trying to source all purchased parts in a dedicated purchased parts folder. I have found when files with the purchased part category are outside of this folder, it is not recognized by our projects. However, if a part is in the folder but the folder is not locked, the part, while released, can still be checked out. Our admins have intentionally set folder driven rules such that a locked folder will lock parts and files downstream. This has been cumbersome as several files are downloaded and checked into the vault weekly, and having to request admins to unlock and resort files in the vault.
Is it best to use a flexible design cycle or is there a more sensible process for vendor sourced parts which a more seasoned user can recommend?
