push sync job users - how many?

[binary_jam]

Hey everybody,

I can't quite wrap my head around how many users are necessary for sync jobs in push-direction in this setup:
PBS1 has 5 datastores with snapshots from different sources in them.
PBS2 also has 5 datastores which contain mirrors of all snapshots from their equivalent datastores on PBS1.
Right now, this is set up with sync jobs in pull direction on PBS2. Those sync jobs use a single user on PBS1 and a single remote config on PBS2.

Now that sync jobs in push direction are supported, this setup is to be converted to pushing from PBS1 to PBS2.
Again, all snapshots of datastore X on PBS1 should be push-synced to datastore X on PBS2.
For testing purposes, one sync job was already switched to push-direction. It works fine.

What I don't quite fully understand is this block in the documentation:

It is strongly advised to create a dedicated remote configuration for each individual sync job in
push direction, using a dedicated user on the remote. Otherwise, sync jobs pushing to the same
target might remove each others snapshots and/or groups, if the remove vanished flag is set or
skip snapshots if the backup time is not incremental. This is because the backup groups on the
target are owned by the user given in the remote configuration.

What exactly is "the same target"? Same remote PBS? Same datastore? Same namespace?
In this setup it would be five sync jobs - one for each datastore.
The docs are speaking of skipped snapshots in syncs and unwanted deletions of previous snapshots on the target side.
Isn't this only the case if multiple sync jobs push to the same datastore (and even the same namespace)?

Is it safe in this setup (one sync job per datastore) to only have one remote config and one remote user?
The setup should be as complex as necessary and as simple as possible.

Thanks in advance for your input!