Copy flow paths provide automation related to creating and sending content, tasks or events. The differences in sending content, tasks or events are minimal, thus all three copy flow types are explained in this chapter.

Copy-flows are defined as separate 'send-on' and 'send-back' steps and possibility to use the creation folder of an object as a source or destination for any copy-flow step. Copy-flows are defined by group or user

Important: a user has the combined copy-flows definition of all his groups plus his own.

Copy flow paths and "creation" containers (folders, calendars)

You can specify in which folder an user can create a content, or in which calendar an user can create a task or an event. See Add a copy flow path / To add a new 'start' path. See also Where to review and edit copy flow paths? and Copy flow transitions.

Sending items

Although you can move an item in any container you are granted appropriate access permissions, the  copy flow provides predefined path and simplifies the copy flow steps.

For every position, you can define an onwards and a backwards path.

Copy flow paths and users/groups

Normally, define the tasks copy flow on the GN4 group level, and leave as undefined the tasks copy flow on the users level. If all the users follow the same tasks copy flow, then define it for the Everyone group. If specific users need slight differences, define only the path that are different on the user level.

Copy flow history

See State history.