We currently use BarTender Enterprise in a very siloed approach.  Developers have 2022 installed locally and can create labels on their own.  The same is true for our Test (QA) environment which has its own server.  On the QA Test server the files are checked into Librarian there which has its own local database. After labels are tested we physically copy the files to the production server and drag them into Librarian there which stores them in its own separate SQL Server database server.  We end up maintaining 2 sets of files because they are stored in QA's local database, and also  PROD's SQL Server database.

I know you support workflows but I am not quite sold on them yet. My question is can my local install (and QA Test servers) all point to the production database server and have its Librarian database common for all of our instances? So for example, my desktop BarTender would point to the same database as our production server.  Then in Librarian I could then have separate DEV, QA, and PROD folders.  I would develop files stored in the Dev folder, Deploy them to QA which would get used by the QA server for Testing, and eventually Deploy or drag them to the Production folder which would be the released versions used by the production server.  So basically our architecture stays the same but all of our instances would use the same common database server.