> ## Documentation Index > Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt > Use this file to discover all available pages before exploring further. # Sign-off task definitions > CSV file format reference for bulk uploading sign-off task definitions in Atoti Sign-Off, with column names, required fields, and format details for scope values and workflow variables. Download sample file: [sign-off-task-definitions.csv](./csv/sign-off-task-definitions.csv) This file is used to create task definitions in bulk. For information on how to upload adjustments using this file, see [Upload tasks](../configure-tasks/create-task/create-task-upload). | Column Name | Description | Required | Value Example | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | name | The name of the definition. Must be unique across all task definitions. | Y | `Pnl` | | description | The description of the definition. | Y | `Description for the Pnl definition` | | category | The category of the definition. | Y | `Pnl category` | | workflowType | The workflow type used by the subsequent tasks. | Y | `simple`, `4-eyes` or `4-eyes-kpi` | | workflowVariables | Any variables required by the workflow. | N | `approvers=MANAGERS;reviewers=USERS` | | startDate | The start date of the task definition with YYYY-MM-DD date format. | Y | `2018-09-20` | | endDate | The end date of the task definition with YYYY-MM-DD date format. | N | `2018-09-30` | | cube | The cube on which the definition applies. | Y | `VaR ES Cube` | | server | The server on which the definition applies. | Y | `MR` | | scopeValues | The scope of the definition. If empty, the definition will be considered top of house. | N | `[Booking].[Desks].[Desk]=[AllMember].[Commodity]\|[AllMember].[Equities];[Organization].[BookHierarchy].[Level 4]=[AllMember].[Global Markets].[Equities].[Cash Equities].[Developed Markets]` | | kpis | The thresholds at which the task is automatically approved and exported without any review. Only applicable for `4-eyes-kpi` workflow type. | N | `Desk All PV;Cash Equities` | | linkedDashboardId | The ID of an existing dashboard to link to the definition. This is the unique reference to a dashboard that you may find in the URL when accessing the dashboard. | N | `ecxRnV` | ## Scope values In the notation for scope values, a semi-colon (`;`) is used to separate level members and a pipe (`|`) is used to separate levels. So the following example: ``` [Booking].[Desks].[Desk]=[AllMember].[Commodity]|[AllMember].[Equities];[Organization].[BookHierarchy].[Level 4]=[AllMember].[Global Markets].[Equities].[Cash Equities].[Developed Markets] ``` Breaks down into: * `[Booking].[Desks].[Desk]` = * `[AllMember].[Commodity]` * `[AllMember].[Equities]` * `[Organization].[BookHierarchy].[Level 4]` = * `[AllMember].[Global Markets].[Equities].[Cash Equities].[Developed Markets]` This means that your definition scope will include at the desk level `Commodity` and `Equities` and at `level 4` of `BookHierarchy` the `Developed Markets`. ## Workflow variables In the notation for workflow variables, a semi-colon (`;`) is used to separate workflow variable names and a pipe (`|`) is used to separate values. So the following example: ``` approvers=MANAGERS;reviewers=USERS;emails=abc@company.com|def@company.com|ghi@company.com ``` Breaks down into: * `approvers` = * `MANAGERS` * `reviewers` = * `USERS` * `emails` = * `abc@company.com` * `def@company.com` * `ghi@company.com` `emails` is not a valid variable in the provided workflows (`simple`, `4-eyes`, `4-eyes-kpi`). You may have such a variable if you define a *custom workflow* sending an update via emails.