A360 Collaboration Conflict
Yes, this is the way that worksets work. If a workset is checked out by a user, then no one else can edit that workset until it's "relinquished" back. If all elements in a file are on "Workset 1" and someone checks out "workset 1", they now have control over every element in the model.
What needs to happen here, is that elements either need to be placed on different worksets to separate them into workable "groups", or to not check out a workset at all, and just borrow individual elements.
I highly suggest starting here: (main topic and lots of sub-topics on worksets)
https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2019/EN...
and then check this out for element borrowing:
https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2019/EN...
@scott_d_davis wrote:not check out a workset at all
And by checkout he means take ownership of or make editable. Whatever term your group of people use. When multiple people need to work on elements that are on the same workset, this is the way to do it. In fact, taking ownership of a workset is not necessary unless you plan on working on the model without having a connection to the central model or when you need to prevent other people from working on those elements. During normal day to day editing it's just not necessary and creates snags in the workflow like you are experiencing.
Worksets are meant to be "collections" of objects in Revit. By default, Revit will create "Workset 1" and "Shared Levels and Grids"
If you need to work in such a way where these "collections" of objects need to be all checked out at once, so that a single user has sole control over editing them, then the objects need to be placed on their own worksets. For instance, you could put all plumbing fixtures and toilet partitions on a workset called "Restrooms". A user then could "check out" Restrooms, because it's their task to work on the design of of those Restrooms that day. As Restrooms workset is checked out, no one else can edit it, until that workset is "relinquished" back into the system.
The best analogy is a library: (Element Borrowing) You go in, and take a book off the shelf and go to a cubicle to read it. No one else can read that book, because you have it "checked out", until you go put it back on the shelf.
Worksets on the other hand, are a library shelf full of books, and you check out the entire shelf. No one else can read any of those books until you check them back in.
The way you are currently working is that you have ALL objects on one workset...and you are "checking out the entire library". Separate those objects onto their own worksets so that others can work.
OR, to your question, you simply don't check out ANY worksets. The entire library is yours. Go to an object and edit it in some way, and you have just "checked it out" (made it editable). It's now your until you put it back on the shelf.
Revit worksharing is designed to work in either capacity, and even both at the same time.
Hope that helps!
