There are two distinct processes involved in synchronizing resources - catch up and release.
When you make changes in the workbench, resources are saved locally. Eventually you will want to release your changes to the stream so others can have access to them. Meanwhile, others may have released changes to the steam. You will want to catch up these resources in the workbench.
It is preferable to catch up before releasing changes, in case there is a conflict with the resources in your workbench and the resources currently in the stream.
Conflicts arise when you have locally modified a resource for which a more recent version is available in the stream. In this situation you can choose to do one of three things: catch up the resource from the stream, release your version of the resource to the stream , or merge your work and the stream resource. Typically you will want to merge, as the other two options will result in loss of work.
There are several filters (display modes) you can use to simplify the process of synchronizing resources.
Incoming changes are changes that come from the stream. Such changes, if accepted, will update the workbench resource to the latest version currently released into the stream.
Outgoing changes are changes that come from the workbench. Such changes, if released, will update the stream resources to the version currently present in the workbench.
No matter which filters you use, conflicts will always appear