Message-ID: <1864518997.10454.1711618346059.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10453_336062547.1711618346059" ------=_Part_10453_336062547.1711618346059 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Synchronization and Permissions

Synchronization and Permissions

Dark Feature - Synchronizers are hidden by defa= ult

We recommend using Automation = instead of Synchronizers. Automation is safer, provides ad= ditional functionality and flexibility, and uses fewer system resources.

To enable synchronizers, see Advanced Configuration and Dark Features<= /a>.

When sync runs, the updates will be made on behalf of the u= ser who installed the synchronizer! Any change that a synchronizer makes when reconciling data between Str= ucture and Jira is performed on behalf of the user who created the synchron= izer, not the user who ran the synchronizer.

This is really important to understand. Consider the following settings:=

Now anyone can edit the structure - add issues, remove issues and rearra= nge the issues in the structure. Every change to the structure will= lead to adding and removing links between the affected issues on your beha= lf - even if the user who changes the structure does not have Link Issues p= ermission!

For all existing synchronizers, the c= reator's username can be found in the Run as User column on the synchroniza= tion settings page. Before executing the transaction, Jira validates the us= er's permissions and then records the result together with the username in = the log.

------=_Part_10453_336062547.1711618346059--