This is by design and is very important to maintaining data integrity. You would never want to have two users editing the same record.
The best way to "get around" FM's handling of this is to build a data entry process where a user lands on a page of globals. fills in the data and clicks a submit button to transfer the data to the storage table and commit the change. You will still have to script the handling of another user having record lock while your trying to do the update.
If you go down that road this should be required reading...
Other topics of interest:
You're leaving out a lot of important information.
Working together how?
The file is hosted on Filemaker Server?
Conflict occurs exactly when?
They are trying to edit the same record?
Ok, as mentioned above, this correct and useful behavior.
They are doing what seems like quite different tasks?