Flare > Setting Up a Flare Workflow > Considerations for Working in a Collaborative Environment >
Setup Permissions

Flare setups are automatically saved with the .flare extension. They receive the .flare extension whether you create them locally or save a setup loaded from Flame. This prevents the overwriting of Flame setups since Flame setups are never saved with the .flare extension. As well, it is not possible to add the .flare extension to a Flame setup name manually. If a Flame user downloads a Flare setup and then attempts to save it, the setup is converted to a Flame setup by the automatic removal of the .flare extension.

Note, however, that nothing prevents you from overwriting a setup created on another Flare system or from deleting setups from another Flare system or from a Flame system.

The first time you save a setup from Flare, the setup is automatically put in a Flare subdirectory, as follows:

~/batch/flare_<hostname>/<my_setup_name>.flare

Setups are saved in this subdirectory whether they were initially created in Flare or downloaded from Flame. Although you can subsequently save setups in other directories, it may be easier to keep track of Flare setups (versus Flame setups) if they are in their own subdirectory.