> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/event-templates/editor/details.md).

# Details

The **Details** tab contains the reusable name and team organization for a template. It keeps the template's name, tags, assignees, event roles, and internal notes together with the settings explained in the other [Event Template editor](/reference/event-templates/editor.md) articles.

The Details view below shows the parts that can travel with a template. The **Contact Info**, **Timeline**, and **Files** sections that you may know from an ordinary Event Page are intentionally absent.

<div data-with-frame="true"><figure><img src="https://2616748322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtdSEPutB4SrRwwUMOIx%2Fuploads%2Fgit-blob-3f31f9a8026a05a48000122d19d6c67e91ef7df6%2Fevent-template-editor-details.png?alt=media" alt="FlowerBuddy Event Template Details tab showing Key Event Data with the template name, timezone, tags, assignees, and Event Roles; Notes; and Event Flowers, without client, timeline, or file sections." width="550"><figcaption></figcaption></figure></div>

## Name, tags, assignees, and roles

Use **Name** to change the template's library name. Use **Tags** to organize the template and **Assignees** when the same workspace members should be associated with events created from it. **Event Roles** show the roles that can organize work on a future event, such as a delivery lead or lead designer.

The **Date** section shows the workspace timezone, but a template does not keep a specific event date. When a real event is created, review its date and any task dates that depend on the event.

## Notes

Use **Notes** for internal context that should help the team use the setup. Keep client names, venue instructions, and other event-specific details out of a reusable template unless they are deliberately generic. For ordinary event notes and formatting controls, see [Write event notes](/reference/event-page/details/write-event-notes.md).

## Client View

The **Hide cost and profit** switch controls FlowerBuddy's workspace presentation mode. When enabled, FlowerBuddy hides cost and profit information in the current event view and hides workflow status. It does not change Client Portal access or publish anything, so use it when presenting the event screen to a client and turn it off when you need the florist view again.

Tags, assignees, event roles, and notes are merged or carried into an event according to the template action being used. [Apply an event template](/reference/event-page/details/apply-event-template.md) explains the choices for updating an event that already exists.

## In this section

* [Set event flowers for a template](/reference/event-templates/editor/details/event-flowers.md)
* [Configure payments and contract content in a template](/reference/event-templates/editor/details/payments-and-contract.md)
* [Set template markups and event settings](/reference/event-templates/editor/details/markups-and-settings.md)