> ## Documentation Index > Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Creating a Scan Job > Choose a module, set targets and credentials, and set a schedule – the wizard for every scan module without a guide of its own. A scan job is the stored configuration of a scan module: which gateway runs it, which targets and credentials it uses, and on what schedule. The wizard captures all of that in a fixed sequence; this path applies to every module without a guide of its own under *Scan Modules*. ## Entry points The *Scan Job* button sits on *Scan › Dashboard* and *Scan › Scan Modules*; clicking a module tile there opens the wizard directly and skips the module choice. If a gateway is still missing, Docusnap365 walks you through its setup first and on to the module choice afterwards. ## How the wizard is laid out Four parts, in this order: | Step | Content | | - | - | | *Basics* | gateway and job name – the same for every module | | middle part | the module-specific entries, usually targets – see below | | *Schedule* | when and how often the job runs | | *Summary* | an overview with *Change* back to every step | In *Basics* you choose the *Gateway*; every one is offered with its state badge, but only an already connected one is preselected. The *Job Name* is suggested from the module and the gateway and can be overwritten; without a connected gateway the field stays empty. Below that you can optionally assign the job to an *Organization*, *Location* and *Platform*. If you jump back to an earlier step in the step header, **every step after it counts as unprocessed again** – your entries are kept, but you pass every check once more. For a small correction, *Change* in the summary is the shorter route. ## Entering Targets For most modules the middle part is a target list: one row per scan target, with module-dependent columns. What the target column accepts – IP, hostname, range or a module-specific format – is in the [Scan Reference](/docs/en/scan/reference#what-may-go-into-the-target-column). The *Credentials for all targets* picker above the list sets the credential entry for every row at once. A row that deviates carries an entry of its own; *Use default* sets it back to the default. A row with an empty cell runs with the default. Set the shared entry first, then the exceptions. The summary later counts how many targets deviate from the default – that way you notice a forgotten row. Number fields such as *Port* or *Timeout (ms)* are silently pulled to their permitted range when you leave them, with no message – an accidentally typed 70000 becomes 65535. The exact limits are in the [Scan Reference](/docs/en/scan/reference#bounds-of-the-number-fields); check unusual values once more after entering them. For many targets at once, *Import CSV* opens a menu with *Select File* and *Download template*. Columns are matched by the names in the header row, not by position; files are read as UTF-8, falling back to the code page Excel writes with on German Windows. A report above the table then summarizes how many targets were taken over and how many were skipped as a duplicate, without a target or with an invalid value. Four modules – *Windows DNS*, *Windows DHCP*, *DFS* and [*Nutanix*](/docs/en/scan/nutanix) – can have their targets searched for in the directory instead: the dialog takes the domain or Prism Central plus credentials and takes over the servers found as rows. ## Credentials Credentials do not have to be prepared beforehand: the picker carries two creation rows above the existing entries – one for a permanent entry, one that applies only here. All permanent entries are managed under *Scan › Credentials*. Which types exist and which fields they require is in the [Scan Reference](/docs/en/scan/reference#credential-types). Name entries after their role, not the account – "Windows domain scan" is found again in the wizard faster than an account name. A job with **one-time credentials** cannot be run again: the access data was not saved and has to be entered afresh through *Edit* for every further run. For recurring jobs, choose the permanent entry. ## Module Settings Some modules bring their own settings, reachable through *Customize* in the middle part; if values are set, *active* stands next to it. *Active Directory* lets you exclude personal data and extended attributes from capture here. *Windows (AD)* and *Windows (IP)* bring a preselected subset of the Windows components, which can be adjusted before creating the job. The complete list of modules with their own settings is in the [Scan Reference](/docs/en/scan/reference#module-settings). ## Setting the Schedule Under *Frequency* there are four patterns – *Once*, *Daily*, *Weekly* and *Monthly*; what each means is in the [Scan Reference](/docs/en/scan/reference#schedule). With *Once*, the choice between *Run Immediately* and *Choose Time* also determines the label of the closing button. *Daily* runs on all seven days; there is no weekday picker. For a working-days-only scan choose *Weekly* and clear Saturday and Sunday. If any step carries **one-time credentials**, *Daily*, *Weekly* and *Monthly* are locked – only *Once* with *Run Immediately* is available. To set a schedule, store the credentials in the *Vault*. *Time* accepts only the quarter-hour grid. A value stored earlier is rounded down to this grid when opened – when editing an older job, check whether the rounded time still fits your maintenance window. Dates in the past can no longer be chosen, neither with *Choose Time* nor with *Start*, and *End* accepts nothing before the chosen start. This also hits **editing** an existing job: if its *Start* now lies in the past, the date field reports an error you must fix first. With recurring execution, the period up to the end date also needs at least one occurrence – an *End* before the first possible execution day is reported as an error as well. ## Summarizing and creating The *Summary* condenses every entry, each section with *Change* back to the matching step. The closing button is called *Run Now* if the job starts immediately, otherwise *Schedule Job*. You find exactly this view again later on the finished job, under *Show Configuration*. The gateway used last is preselected for the next job, provided it is connected – with several jobs for the same gateway that saves a click every time. ## Related The new job appears under *Scan › Active*; how you watch, halt or correct it is in [Managing Jobs](/docs/en/scan/manage-jobs). Modules with a different middle part have a guide of their own under *Scan Modules* – which ones is in [Scan Modules – Overview](/docs/en/scan/scan-modules). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.