By default, processes are fixed in their behavior to match company guidelines. However, you can allow supporter users to modify a process instance before applying it to a ticket. This ticket action does not change the process as defined in the configuration. The following options are available:

• Processes are not modifiable when used in tickets: The default behavior for processes is that they cannot be modified by supporters when starting them on tickets. This option ensures that a process must be followed as defined by, for example, company guidelines.

• Processes can be modified when used in tickets: Processes can be modified by supporters before applying them to a ticket. This option makes sense when using processes as modifiable templates intended to be changed during usage.

By default, tickets can be viewed only by users with the appropriate permissions or memberships in the current resource. However, by setting the sharing options, you can allow access to tickets for all members of the resources involved in a process. This means that users with memberships in resources that could potentially have access to a ticket created by the process or the main ticket in the future are immediately given read or write access to the main ticket and all its parallel tickets. The following options can be used:

• No additional sharing: By default, tickets are not shared with additional resource members, except for those who have access via the current ticket resource or other global settings that allow a user to read or modify all tickets.

• All involved resource members have read access to all tickets of the process: the main ticket and its parallel tickets can be read by all resource members potentially involved in a process. This means that a user whose resource is defined at any point in the process will immediately have read access to any ticket in the process.

• All involved resource members have read and write access to all tickets of the process: the main ticket and its parallel tickets can be read and modified by all resource contributors potentially involved in a process. This means that a user whose resource is defined at any point in the process will have immediate read and write access to any ticket in the process.