@spokane-folio/security-incident 1.0.28

package/.eslintrc

@@ -0,0 +1,32 @@
+{
+  "extends": [
+    "@folio/eslint-config-stripes",
+    "airbnb",
+    "plugin:import/recommended",
+    "plugin:jsx-a11y/recommended",
+    "plugin:prettier/recommended",
+    "prettier"
+  ],
+  "parser": "@babel/eslint-parser",
+  "plugins": [
+    "no-only-tests"
+  ],
+  "rules": {
+    "react/jsx-props-no-spreading": "off",
+    "no-only-tests/no-only-tests": "error",
+    "react/prop-types": "off",
+    "import/prefer-default-export": "off"
+  },
+  "overrides": [
+    {
+      "files": [ "src/**/tests/*", "**/*.test.js", "test/**/*" ],
+      "rules": {
+        "react/prop-types": "off",
+        "import/prefer-default-export": "off"
+      }
+    }
+  ],
+  "env": {
+    "jest": true
+  }
+}

package/.github/workflows/CODEOWNERS

@@ -0,0 +1,8 @@
+
+# default ownership for this repo
+* @CB-SPL-Dev
+
+# workflow and release sensitive paths
+.github/workflows/** @CB-SPL-Dev
+package.json @CB-SPL-Dev
+yarn.lock @CB-SPL-Dev

package/.github/workflows/pr-validation.yml

@@ -0,0 +1,44 @@
+
+
+name: PR Validation
+
+on:
+  pull_request:
+    branches: [dev]
+
+permissions:
+  contents: read
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out
+        uses: actions/checkout@v4
+
+      - name: Set up Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: yarn
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+
+      - name: Lint
+        run: yarn lint
+
+      - name: Test
+        run: yarn test --ci
+        continue-on-error: false
+
+      - name: Build
+        run: yarn build
+
+      - name: Validate module descriptor generation
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y jq
+          yarn run build-mod-descriptor
+          test -f module-descriptor.json

package/.github/workflows/release.yml

@@ -0,0 +1,64 @@
+
+
+name: Release
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    environment: production-release
+
+    steps:
+      - name: Check out
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Node for npm
+        uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          registry-url: 'https://registry.npmjs.org'
+          scope: '@spokane-folio'
+          cache: yarn
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+
+      - name: Install jq
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y jq
+
+      - name: Generate module descriptor
+        run: yarn run build-mod-descriptor
+
+      - name: Publish to npm
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npm publish --access public
+
+      - name: Pack tarball
+        run: yarn pack
+
+      - name: Read package version
+        id: pkg
+        run: echo "version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
+
+      - name: Create GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: v${{ steps.pkg.outputs.version }}
+          name: security-incident v${{ steps.pkg.outputs.version }}
+          files: |
+            module-descriptor.json
+            *.tgz
+
+
+

package/.prettierrc

@@ -0,0 +1,6 @@
+{
+  "singleQuote": true,
+  "trailingComma": "es5",
+  "tabWidth": 2,
+  "printWidth": 80
+}

package/.stripesclirc

@@ -0,0 +1,4 @@
+{
+  "configFile": "stripes.config.js",
+  "port": 3000
+}

package/CHANGELOG.md

@@ -0,0 +1,8 @@
+# Change history for ui-security-incident
+
+## 1.1.0 (IN PROGRESS)
+
+
+## 1.0.0
+
+* New app created with stripes-cli

package/CONTRIBUTING.md

@@ -0,0 +1,4 @@
+# Contribution guidelines
+
+Guidelines for Contributing Code:
+[dev.folio.org/guidelines/contributing](https://dev.folio.org/guidelines/contributing)

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,16 @@
+# ui-security-incident
+
+This software is distributed under the terms of the Apache License, Version 2.0. See the source [LICENSE](https://www.apache.org/licenses/LICENSE-2.0.txt) for more information.
+
+## Introduction
+The Security Incident UI Module, or `ui-security-incident`, is a Stripes UI Module designed to help libraries manage and track security incidents efficiently. It provides functionality for creating, editing, viewing, searching, sorting, and filtering incident reports. 
+
+## Installation 
+
+## Build and serve
+
+## Tests
+
+## Additional information 
+
+Other [modules](https://dev.folio.org/source-code/#client-side).

package/administrator-documentation/roles-and-permissions.md

@@ -0,0 +1,65 @@
+# Track Roles and Permissions Guide
+
+## Overview
+Track uses **roles and permissions** to control what each staff member can do in the application.  
+This system is called **RBAC (Role-Based Access Control)**.
+
+---
+
+## What Are Roles and Permissions?
+
+- **Roles** are assigned to staff (for example: *Front-line Staff*, *Supervisor*, or *Admin*).  
+- **Permissions** decide what each role can see and do in Track.
+
+Together, roles and permissions ensure that each user only has access to the actions and information appropriate to their job responsibilities.
+
+---
+
+## What You Experience in the UI
+
+Depending on your assigned role, the interface and available features in Track will change.
+
+### View Incidents
+Most staff can see the list of incidents and view their details.
+
+### Create or Edit Incidents
+Only staff with the proper permissions can create new reports or edit existing ones.
+
+### Access Settings
+Supervisors and admins can see the **Settings** section to manage:
+- Categories  
+- Types  
+- Locations  
+- Trespass templates  
+- Trespass reasons  
+
+### Edit Settings
+Only admins (or staff with special permissions) can **add, change, or delete** items in Settings.
+
+If you don’t have permission for a feature, you simply won’t see its button or page — the option will be hidden automatically.
+
+---
+
+## Typical Roles Example
+
+| **Role**           | **View Incidents** | **Create/Edit Incidents** | **View Settings** | **Edit Settings** |
+|--------------------|--------------------|----------------------------|-------------------|-------------------|
+| Front-line Staff   | ✓                  | ✓                          |                   |                   |
+| Supervisor         | ✓                  | ✓                          | ✓                 |                   |
+| Admin              | ✓                  | ✓                          | ✓                 | ✓                 |
+
+---
+
+## How Roles Are Set
+
+- Roles are assigned by your library’s **system administrator** (outside of Track).  
+- Track automatically shows or hides features based on your assigned role.  
+- Permissions are managed centrally to maintain consistency across your organization.
+
+---
+
+## Summary
+
+- **Admins** can do everything, including changing settings.  
+- **Supervisors** can view and manage incidents, and view settings.  
+- **Front-line staff** can create and view incidents.  

package/administrator-documentation/track-settings-admin-guide-sketch.md

@@ -0,0 +1,192 @@
+# Track Settings: Admin Guide
+
+## What is Track Settings?
+
+**Track Settings** is the control center for managing how security incidents are tracked and documented in your library.  
+It lets you customize categories, types, locations, trespass templates, and reasons—so **Track** fits your organization’s needs.
+
+---
+
+## What Can You Do in Track Settings?
+
+### Incident Categories and Incident Types
+In Track Settings, Incident Categories and Incident Types work together to help you organize and report security incidents in your library.
+
+### Incident Categories
+Incident Categories are broad groups, like “Theft” or “Disturbance.” They help you sort incidents into meaningful sections for easier tracking and analysis.
+
+### Incident Types
+Incident Types are the specific kinds of incidents that happen, such as “Verbal Abuse” or “Property Damage.” Every Incident Type belongs to one Incident Category. For example, “Verbal Abuse” might be part of the “Disturbance” category.
+
+### How This Works in the UI
+When you **add or edit an Incident Type**, you’ll be asked to choose which **Category** it belongs to.  
+Categories help you keep your Incident Types organized, so reports and searches are clearer. The 'description' field is required. The information for the description will help admin and staff users to have more specificity for reference when choosing an incident type when creating or editing a report.
+You can **filter Incident Types by Category** when viewing or selecting them, making it easier to find what you need. The description of the incident type is also rendered for better reference. 
+
+### Summary
+**Incident Categories** are the big groups; **Incident Types** are the specific incidents within those groups.  
+This setup makes it simple to organize, find, and report incidents in a way that fits your library’s needs.
+
+
+## Locations, Zones, and Custom Locations
+Set up all library locations and sub-locations (like **“Main Branch”** or **“Children’s Area”**) to accurately record where incidents happen.
+
+### Service locations
+Service locations for Track are derived from the official institutional level FOLIO locations, populating the 'select location' dropdown selector in Track Locations Settings. You can select a location and save it to Track locations. The 'location' value of a service location derived from the institution cannot be edited.  
+
+### Custom locations
+Custom locations are available for configuration in Track to allow libraries to record incidents in areas that aren't part of their official FOLIO location setup - such as outdoor spaces, shared facilities, or temporary event areas. This makes reporting and analysis more accurate for all parts of the library's environment. 
+
+Custom locations for Track are user inputted with the 'name' value as required. The name of a custom location cannot be the same as the name of an existing Track service location. The 'name' value of a custom location may be edited.
+
+### Zones
+Zones are configurable for any Track service location, whether it was derived from institutional FOLIO locations or a custom location. Each location can have many zones, with the requirement that each zone has a 'name' field, 'description' is optional. Individual zones are not editable, although they can be removed for replacement. 
+
+### How It Works in the UI - Managing Locations and Zones
+- Go to **Settings** and choose **Locations**.
+- You’ll see a list of your library’s official locations. You can add new locations (custom ones) if needed.
+- For each location, you can add zones to break it down into smaller areas. For example, add "Reading Nook" as a zone under "Main Branch."
+- Zones help you record exactly where something happened, making reports more detailed and useful.
+
+### Using Locations and Zones When Reporting Incidents
+- When you create or edit an incident, you’ll select a location from a dropdown menu.
+- If zones are set up for that location, you’ll also be able to pick the specific zone.
+- Custom locations appear in the same list, so you can always record incidents in any area you need.
+
+### Editing and Removing
+- You can edit the name of a custom location if needed, but official locations cannot be changed.
+- Zones can be removed and replaced, but their names and descriptions cannot be edited once created.
+
+### Summary
+- **Locations** help you track where incidents happen at a high level.
+- **Zones** let you be more specific within each location.
+- **Custom Locations** allow you to add new areas for tracking, so nothing is missed.
+- The UI makes it easy to select, add, and organize these places, so your incident records are always clear and complete.
+
+
+## Trespass Document Templates
+### What Are Trespass Document Templates?
+A **Trespass Document Template** is a pre-made notice that you can use when someone needs to be officially notified about a trespass.  
+Instead of writing a new notice every time, you set up templates in advance. These templates can include special placeholders (like a person’s name or the date) that get filled in automatically when you use them.
+
+### How Do You Manage Templates in Track?
+### Go to Settings
+In the Track app, open the **Settings** section and choose **“Trespass Templates.”**
+
+### View Existing Templates
+You’ll see a list of all your current trespass templates.  
+Each template shows its **name**, **description**, and whether it’s **active** or **set as the default**.
+
+### Add a New Template
+Click the **“Add”** or **“New”** button.  
+Fill in the template’s name and description, and write the notice text.  
+You can insert placeholders for things like names or dates, so each notice is personalized. 
+
+### Inserting tokens
+Use the 'insert' button in the editor's menu to open the tokens modal. Choose the token(s) you want and click 'Insert selected tokens' button. This will write your selected tokens to the last place your cursor was in the editor's text area. It is not advised to copy and paste tokens from one space to another in the editor because if there is a typo (ex: missing bracket, nudged spacing inside the token text) that token will not be read by the program and data will not be dynamically written onto the final trespass document. 
+
+### Edit a Template
+Click on a template to view its details. Choose **“Edit”** to update the wording or change which placeholders are used.  
+You can also preview how the notice will look before saving.
+
+### Set a Default Template
+You can mark one template as the **default**.  
+This means it will be used automatically when creating a new trespass notice, unless you choose a different one. If one template is already default and you update a different template to default, that most recently updated template will then override to become the new default. A template cannot be both 'default' and not active - if a template is saved as 'default' but not active, the update will revert to 'active'. If no template is chosen as the default the program will not automate trespass documents. 
+
+### Delete a Template
+If you no longer need a template, you can delete it.  
+You’ll be asked to confirm before it’s removed.
+
+### How Are Templates Used When Reporting Incidents?
+- When you create or edit an incident that involves a trespass, **Track** will use your default template to generate the notice.  
+- The system fills in the placeholders with the correct information (like the person’s name and the date).  
+- You can preview the notice before saving or sending it.  
+- The final document is attached to the incident record for future reference.
+
+### Tips for Admins
+- **Keep Templates Clear and Professional:** Use simple, direct language in your notices.  
+- **Use Placeholders Wisely:** They help personalize each notice without extra work.  
+- **Preview Before Saving:** Always check how the notice will look to make sure it’s correct.  
+- **Set a Default Template:** This ensures the programmatic trespass document generation is in effect.
+
+Trespass Document Templates make it easy to create, manage, and send official notices.  
+With Track, you can be sure every trespass notice is **accurate**, **consistent**, and **ready when you need it**.
+
+
+## Trespass Reasons
+Manage the list of reasons for issuing trespass notices, and choose which are active or default. Trespass Reasons are the explanations you give when someone is being issued a trespass notice at your library. They help you keep a clear record of **why** a person is being asked to leave or stay away.
+
+### How Do Trespass Reasons Work in the UI?
+### Where to Find Them
+Go to the **Settings** section and select **Trespass Reasons**.
+
+### What You See
+You’ll see a list of all the trespass reasons your library uses.  
+Each reason is a short description, such as:
+
+- “Repeated disruptive behavior”  
+- “Violation of library policy”  
+
+These help staff choose consistent explanations for each trespass action.
+
+### Adding a New Reason
+Click the **Add** button to create a new reason.  
+Type in your explanation and save it.  
+This new reason will now be available whenever staff need to issue a trespass notice.
+
+### Default Reason
+You can mark one reason as the **default**.  
+This means it will be automatically selected when staff are filling out a trespass notice — but they can always choose a different reason if needed.
+
+### Suppressing a Reason
+If you no longer want a reason to appear for staff to select, you can **suppress** it.  
+Suppressed reasons are hidden from the selection list but not deleted, so your historical records remain accurate.
+
+### Editing or Removing
+You can edit the text of a reason if you need to update its wording.  
+If a reason is no longer needed, suppress it instead of deleting it to keep your data and reports consistent.
+
+### When Are Trespass Reasons Used?
+
+Whenever staff issue a trespass notice to a customer (for example, during an **incident report**), they will select a reason from your list.  
+This reason is included in both the **official trespass notice** and your **incident records**, making it clear why the action was taken.
+
+### Summary
+Trespass Reasons help your team stay **consistent**, **clear**, and **accurate** when documenting why someone is being trespassed.  
+You control the list in **Settings**, making it easy to update as your library’s needs change.
+
+---
+
+## Getting Started
+
+### 1. Open Track Settings
+Go to the **Settings** section in Track.  
+You’ll see a menu with options for:
+- Categories  
+- Types  
+- Locations  
+- Trespass Templates  
+- Trespass Reasons
+
+### 2. Choose What to Manage
+Click on the area you want to update (for example, **“Incident Categories”**).
+
+### 3. View, Add, Edit, or Delete
+- **View:** See the current list of items.  
+- **Add:** Click the **New** or **Add** button to create a new item. Fill in the details and save.  
+- **Edit:** Click on an item to view details, then choose **Edit** to make changes.  
+- **Delete:** Use the delete button to remove items you no longer need. You’ll be asked to confirm before anything is deleted.
+
+### 4. Save Your Changes
+After adding or editing, always click **Save** or **Save and Close** to keep your updates.
+
+### 5. Use Modals and Previews
+For trespass templates, you can preview documents before saving.  
+You can also insert tokens (like names or dates) to personalize notices.
+
+
+## Tips for Admins
+- **Keep Categories and Types Organized:** Clear names make reporting easier.  
+- **Double-Check Before Deleting:** Deleted items can’t be recovered.  
+- **Use Templates for Consistency:** Trespass templates help ensure notices are professional and complete.  
+- **Set Defaults Carefully:** Default reasons and templates are used most often, so choose what fits your policies.