--- title: Divisions and seasons description: What divisions and seasons are, how they organize tasks and inventory, and what the active and archived flags do. --- [Skip to content](https://help.trak.io/knowledge-base/divisions-and-seasons#main-content) [![resized by Cameron Trak Logo Variations - 2025-01-1](https://help.trak.io/hs-fs/hubfs/resized%20by%20Cameron%20Trak%20Logo%20Variations%20-%202025-01-1.png?width=120&height=75&name=resized%20by%20Cameron%20Trak%20Logo%20Variations%20-%202025-01-1.png)](https://help.trak.io/knowledge-base?hsLang=en) Open main navigation Close main navigation - How can we help you? - There are no suggestions because the search field is empty. 1. [Trak Software Help Center](https://help.trak.io/knowledge-base?hsLang=en) 2. [Using Trak](https://help.trak.io/knowledge-base/using-trak?hsLang=en) 3. [Settings and Admin](https://help.trak.io/knowledge-base/using-trak?hsLang=en#settings-and-admin) # Divisions and seasons Divisions and seasons are the two top-level ways Trak organizes your work. A **division** is a distinct part of your organization; a **season** is a period of activity within a division. Every task and every piece of inventory belongs to a season, and every season belongs to a division. Most workspaces run a **single division**. Larger organizations that manage several properties or teams run **multiple divisions** (you may hear this called multi-division or multi-property). When there's only one division, Trak selects it for you automatically; when there are several, you choose which one you're working in. ### Who can manage divisions and seasons? Divisions and seasons are managed by **Site Admins**, under **Settings**. Managers, Team Members, and Collaborators can see them but cannot change them. One difference between the two: a Site Admin can create and edit divisions but **cannot delete** them — division deletion is restricted, and a workspace must always keep at least one division. Site Admins can fully manage seasons, including deleting them. ### Divisions A division groups its own seasons and its own products. Open **Settings** from the left sidebar, then choose **Divisions**. - **Active.** Whether the division is live. The setting reads: *"When checked, associated seasons and products will appear."* Collaborators only see active divisions; your internal users see all of them. - **External ID.** If the division came from another system during an import, it keeps that system's identifier here. - **Order.** Drag a division's row up or down on the list to reorder it; the new order saves as soon as you drop it. Divisions do not have an archived state — that flag exists on seasons only. ### Seasons A season belongs to one division and represents a period of activity within it — often a competition year or campaign. On a partnership, **seasons organize the tasks** you track: the partnership's task list is grouped by season. Open **Settings** from the left sidebar, then choose **Seasons**. When you have more than one division, pick the division first, then manage its seasons. A season carries two independent flags, plus the shared settings: - **Active.** The setting reads: *"Active seasons are included in partnership completion percentages, and are selected by default."* An inactive season still exists and is visible in the app; it just isn't counted toward completion or selected automatically. - **Archived.** The setting reads: *"Archived seasons are not displayed in the application, but the data is retained for historical record."* Archiving is a stronger "put away for history" state — the season drops out of the app entirely, and collaborators can no longer see it, while the data is kept. - **External ID** and drag-to-reorder work the same as on divisions. A season shows as **Active**, **Inactive**, or **Archived** in the list, and you can filter by those three states. Active and archived are separate settings: an inactive season is still on display, whereas an archived one is hidden. ### How products and seasons create inventory Every **product** belongs to a division. Trak turns products into sellable **inventory** automatically, one inventory item per season: - **When you create a product,** Trak generates inventory for it on each active season of its division. - **When you add a new season to a division,** Trak generates inventory for that season from the division's existing products. This is why products live at the division level but the inventory you actually sell is tied to a specific season. ### What happens if I delete a season? You can't delete an **active** season — Trak stops you with *"You can not delete an active season."* Make the season inactive (or archive it) first. Deleting an inactive or archived season is destructive. As the confirmation warns: *"Deleting a season will delete all tasks associated with this season."* Because inventory is held on the season too, deleting the season also removes the inventory generated for that season's products. This can't be undone, so archive a season instead of deleting it if you only want it out of the way. ### What happens if I delete a division? A workspace must always keep at least one division, so Trak blocks deleting the last one with *"There must be at least one division."* Deleting a division removes **all of its seasons and all of its products**, and — because deleting a season deletes that season's tasks — the tasks across every one of those seasons are deleted as well. This is a large, permanent change; use the division's **Active** flag to hide it instead if you don't intend to erase its history. - [The Basics](https://help.trak.io/knowledge-base/the-basics?hsLang=en) - [Using Trak](https://help.trak.io/knowledge-base/using-trak?hsLang=en#main-content) - [Partnerships](https://help.trak.io/knowledge-base/using-trak?hsLang=en#partnerships) - [Social Media](https://help.trak.io/knowledge-base/using-trak?hsLang=en#social-media) - [Integrations](https://help.trak.io/knowledge-base/using-trak?hsLang=en#integrations) - [Settings and Admin](https://help.trak.io/knowledge-base/using-trak?hsLang=en#settings-and-admin) - [Module by Module](https://help.trak.io/knowledge-base/module-by-module?hsLang=en) - [Advanced Features](https://help.trak.io/knowledge-base/advanced-features?hsLang=en) - [How To Guides](https://help.trak.io/knowledge-base/how-to-guides?hsLang=en) - [Mobile App](https://help.trak.io/knowledge-base/mobile-app?hsLang=en) - [New Features](https://help.trak.io/knowledge-base/new-features?hsLang=en#main-content) - [2026](https://help.trak.io/knowledge-base/new-features?hsLang=en#2026) - [2025](https://help.trak.io/knowledge-base/new-features?hsLang=en#2025) - [2024](https://help.trak.io/knowledge-base/new-features?hsLang=en#2024) - [2023](https://help.trak.io/knowledge-base/new-features?hsLang=en#2023) [![resized by Cameron Trak Logo Variations - 2025-01](https://help.trak.io/hs-fs/hubfs/resized%20by%20Cameron%20Trak%20Logo%20Variations%20-%202025-01.png?width=120&height=75&name=resized%20by%20Cameron%20Trak%20Logo%20Variations%20-%202025-01.png "resized by Cameron Trak Logo Variations - 2025-01")](https://www.trak.io/) P.O. Box 2560, Boise, ID 83701 [mailto:erika.schutte@trak.io](mailto:erika.schutte@trak.io) Copyright © 2026, Trak Software