---
title: "Inspection Template Properties"
slug: "inspection-template-properties"
updated: 2025-04-29T21:56:05Z
published: 2025-04-29T21:56:05Z
canonical: "docs.serenityops.com/inspection-template-properties"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serenityops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Inspection Template Properties

Once an inspection template is created in the Inspections & Audits applications, users with the appropriate roles (such as template editors or template owners) can configure a range of properties to control how the template behaves, what data it collects, and who can use it. These settings are available on the **Details** tab of the template record.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXfBC8LnOYuK3HxcYyXTWGnUOFWirRRuuf2v6vgYmvHaw3Vw2Wy-EW9TjrpXHLGYa2943bMO8HMzTkg26AeqK8qiA9TGiFRY9aESENMz2G85OBlLOg3rLx8_X8YCRVOoJI-WlIHDlA?key=0AljBKwI0wYz67ygMJMFFpE5)

---

## Template Basics

- **Short Description**: The name of the inspection template.
- **Type**: Select whether the template is for an inspection, an audit, or a general checklist.
- **Active**: Toggle to make the template available for use.

---

## Inspection Properties

- **Owner**: The user who owns and manages the template. Only the owner or users with the Template Editor role can edit all templates.
- **Scores Enabled**: When enabled, responses to checklist items can be assigned scores, allowing for an overall inspection score.
- **Allow Issues**: Choose whether inspection responses can generate:
  - Findings
  - Actions
  - Both (default)
  - None
- **Allow Ad Hoc Questions**: Allows inspectors to add new questions dynamically during inspections, which is useful for capturing unanticipated observations.

---

## Default Question Properties

- **Response Type**: The format of expected answers (e.g., Yes/No/NA, Good/Fair/Poor/NA, etc).
- **Require Notes When**: Automatically prompts the inspector for notes based on specific answers.
- **Require Attachments When**: Determines which responses should include supporting files or images.
- **Require Issues When**: Set conditions under which a finding or action must be created.
- **Required Issue Type**: Specify whether the default issue should be logged as a Finding or an Action.
- **Default Issue Priority**: Set a standard priority level for issues generated from checklist responses.

---

## Access Management

Control who can use and view the template and its associated inspection tasks:

- **Available To**: Determines which users can use this template to create inspections. Options include:
  - Only the template owner
  - All inspection users
  - Specific groups and users
- **Tasks Available To**: Controls visibility of inspections created from this template. Options include
  - Only the template owner and assigned groups or users.
  - Specific users or groups (in addition to template owner and assigned groups or users).
  - All inspection users (anyone with the inspection user role)
- **Tasks Available to Entities**: Restricts the entity classes that are available when creating inspections or audits.

For example, a site safety audit may only apply to Establishments or Zones, while an equipment maintenance inspection may only apply to assets and vehicles.

💡 These access controls allow organizations to deploy targeted checklists to the right teams and entities, ensuring efficiency and consistency across locations.