Teams will be able to take two approaches. Concurrent working or the Lock and Release method. Link to the Concurrent working article as be found at the bottom of the page.
Lock and Release
This means two or more members can't modify the same project at the same moment. SqlDBM handles this as Relational Database does - a resource is locked by a transaction to prevent another transaction from accessing the same resource.
Let's suppose user A decided to start working on the project, so the first thing the user should do is lock the project. A user B wants to modify something, but once it enters the project, a message will be displayed saying that the project is being edited by someone else (user A). Once user A has finished the changes, then he/she releases the lock; thus user B can work on the project. Check below the workflow of the lock/release functionality in SqlDBM.
Figure 1. Before start working, the project needs to be locked.
Figure 2. If you are the editior then you will see the following if the project is locked.
Figure 3. The message show's who is currently editing the project
Figure 4. Once the changes are finished, then they need to be saved.
Figure 5. Releasing the lock, by clicking the unlock button.
Concurrent Working
Concurrent Working on the other hand allows users to work in parallel branches without having to lock a project. This allows users to collaborate together without any downtime.
See also:
Concurrent Working