> ## Documentation Index > Fetch the complete documentation index at: https://docs.assuric.com/llms.txt > Use this file to discover all available pages before exploring further. # Creating custom tasks > Add a task Assuric's defaults don't cover, give it a category, and map it to a framework requirement if one applies. **Quick summary** * Use **New Task** to add your own task alongside Assuric's defaults. * Choosing the *Product* category means picking a product too, and you can't change that choice later. * Mapping a task to a requirement is optional, but only a mapped task counts as evidence for that framework. Click **New Task** in the Tasks toolbar. Or start from a framework's **Tasks** tab. Its **Add** menu has: * **Create new task**, for a custom task on that framework. * **Map existing tasks**, to link tasks from other frameworks. Give the task a *Task Title* and a *Category*, both required, and an assignee if you know the owner. Pick one of the [task categories](/tasks/categories-and-states), or *Other* if none fits. The Add New Task dialog with the Task Title field, Category selector, and Assignees control highlighted **Picking Product as the category is a one-way choice.** A required *Mapped Products* field appears next to *Category*, with the hint *This cannot be changed later*. *Mapped Frameworks*, under *Compliance Mapping*, also becomes required for a product-specific task. Pick the product in *Mapped Products*. The New Task dialog with Product selected as the category, showing the new required Mapped Products field and the Mapped Frameworks field now marked required *Task Type*, *Status* and *Priority* start with defaults (*Document*, *Not Started*, *Medium*), and *Due Date* and *Recurrence* are optional. Under *Compliance Mapping*, pick a framework in *Mapped Frameworks* first. *Mapped Requirements* stays disabled until you do, then lists that framework's clauses. **What happens if you don't map a task to a requirement?** It still tracks like any other task, but proves nothing against a framework. *Associated Documents* and *Associated Evidence* are optional. Click **Add Task** once you're done. ## Related articles The categories a custom task can belong to. Assign, schedule and comment on any task, custom or default. What a task satisfies, and how the two are mapped. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.