diff --git a/containers/backupchecks/src/templates/documentation/customers-jobs/approved-jobs.html b/containers/backupchecks/src/templates/documentation/customers-jobs/approved-jobs.html index 93fffd7..cb78a4c 100644 --- a/containers/backupchecks/src/templates/documentation/customers-jobs/approved-jobs.html +++ b/containers/backupchecks/src/templates/documentation/customers-jobs/approved-jobs.html @@ -4,16 +4,327 @@

Approved Jobs

- View and manage approved backup jobs. + View and manage all approved backup jobs across all customers.

+

Overview

+ +

The Jobs page provides a comprehensive view of all approved backup jobs in BackupChecks. Once a job has been approved from the Inbox, it appears here and begins receiving backup reports automatically.

+ +

This page allows you to:

+ + + +

Accessing the Jobs Page

+ +

To view approved jobs:

+ +
    +
  1. Navigate to Jobs in the main navigation menu
    2. +
  2. This page is available to Admin, Operator, and Viewer roles
    3. +
  3. Reporters do not have access to operational features like the Jobs page
    4. +
+ +

Jobs List

+ +

The Jobs page displays a table with the following columns:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ColumnDescription
CustomerCustomer name (jobs are grouped by customer)
Job NameBackup job name (clickable to view details)
Backup SoftwareDetected backup software (e.g., Veeam, Acronis, Windows Server Backup)
Backup TypeType of backup (e.g., Full, Incremental, Differential)
Last RunDate and time of the most recent backup run
StatusStatus of the most recent run (Success, Failed, Warning)
ScheduleLearned schedule (e.g., "Daily", "Weekly: Mon, Wed, Fri", "Monthly: 1st")
ActionsEdit, Archive, Delete buttons
+
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Filtering:
+ By default, only active jobs for active customers are shown. Archived jobs and jobs belonging to inactive customers are hidden. Use the "Show archived jobs" toggle to view archived jobs.
-

Content

+

Viewing Job Details

-

Detailed content will be added here in a future update.

+

To view detailed information about a specific job:

+ +
    +
  1. Navigate to the Jobs page
    2. +
  2. Find the job in the list
    3. +
  3. Click on the job name
    4. +
+ +

The job detail page shows:

+ + + +

Editing Job Information

+ +

While you cannot manually change parser-determined fields (sender pattern, subject pattern, backup software), you can edit certain job properties:

+ +
    +
  1. Navigate to the Jobs page
    2. +
  2. Find the job you want to edit
    3. +
  3. Click the Edit button
    4. +
  4. Modify editable fields: + +
    5. +
  5. Click Save to apply changes
    6. +
+ +
+ ⚠️ Parser Fields Are Read-Only:
+ Fields determined by Mail Parsers (backup software, backup type, sender pattern, subject pattern) cannot be manually edited. If these are incorrect, the Mail Parser configuration must be updated by an administrator. +
+ +

Job Status Indicators

+ +

Jobs display different status indicators based on their most recent backup run:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
StatusColorMeaning
SuccessGreenMost recent backup completed successfully
FailedRedMost recent backup failed
WarningYellow/OrangeBackup completed with warnings
No RunsGrayJob approved but no backup runs received yet
+ +

Archiving Jobs

+ +

When a backup job is no longer active (e.g., server decommissioned, backup solution changed), you can archive it to declutter operational views.

+ +

How to Archive a Job

+ +
    +
  1. Navigate to the Jobs page
    2. +
  2. Find the job you want to archive
    3. +
  3. Click the Archive button
    4. +
  4. Confirm the archival
    5. +
+ +

Effects of Archiving

+ +

When a job is archived:

+ + + +
+ 💡 When to Archive:
+ Archive jobs when: + +
+ +

Viewing Archived Jobs

+ +

To view archived jobs:

+ +
    +
  1. Navigate to the Jobs page
    2. +
  2. Enable the Show archived jobs toggle at the top of the page
    3. +
  3. Archived jobs will appear in the list with an "Archived" label
    4. +
+ +

Unarchiving a Job

+ +

To unarchive a job:

+ +
    +
  1. Enable Show archived jobs
    2. +
  2. Find the archived job
    3. +
  3. Click the Unarchive button
    4. +
+ +

The job will immediately reappear in operational views (Daily Jobs, Run Checks).

+ +

Deleting Jobs

+ +

If you need to permanently remove a job and all its data:

+ +
    +
  1. Navigate to the Jobs page
    2. +
  2. Find the job you want to delete
    3. +
  3. Click the Delete button
    4. +
  4. Confirm the deletion in the dialog
    5. +
+ +
+ ⚠️ Warning - Permanent Deletion:
+ Deleting a job is permanent and will delete: + + This action cannot be undone. Consider archiving the job instead if you might need the data later. +
+ +

Exporting Job Data

+ +

You can export all job data to a JSON file for backup, reporting, or migration purposes.

+ +
    +
  1. Navigate to Settings → Maintenance
    2. +
  2. In the "Export/Import" section, click Export Jobs
    3. +
  3. A JSON file will be downloaded containing: + +
    4. +
+ +
+ 💡 Export Format:
+ The export uses JSON format (schema version: approved_jobs_export_v1). This format is designed for system migration and backup purposes. +
+ +

Importing Job Data

+ +

You can import job data from a previously exported JSON file.

+ +
    +
  1. Navigate to Settings → Maintenance
    2. +
  2. In the "Export/Import" section, click Import Jobs
    3. +
  3. Select your JSON file (must match the export format)
    4. +
  4. Click Upload
    5. +
  5. The system will: + +
    6. +
  6. Review the import summary showing created and updated counts
    7. +
+ +
+ ⚠️ Import Behavior:
+ The import process will: + + Ensure your JSON data is correct before importing. +
+ +

Next Steps

+ + {% endblock %} diff --git a/containers/backupchecks/src/templates/documentation/customers-jobs/configuring-jobs.html b/containers/backupchecks/src/templates/documentation/customers-jobs/configuring-jobs.html index b58f72c..a0498ea 100644 --- a/containers/backupchecks/src/templates/documentation/customers-jobs/configuring-jobs.html +++ b/containers/backupchecks/src/templates/documentation/customers-jobs/configuring-jobs.html @@ -4,16 +4,297 @@

Configuring Jobs

- Learn how to configure backup jobs. + Understand how backup jobs are created and configured in BackupChecks through the Inbox approval workflow.

+

Overview

+ +

Unlike traditional systems where you manually configure backup jobs, BackupChecks uses an Inbox-based approval workflow. Jobs are created by approving backup report emails, and all job configuration is automatically determined by Mail Parsers.

+
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Key Concept:
+ You cannot manually create or configure backup jobs in BackupChecks. Instead, jobs are created by approving emails from the Inbox. This ensures consistency and prevents configuration errors.
-

Content

+

How Jobs Are Created

-

Detailed content will be added here in a future update.

+

The job creation process follows these steps:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
StepWhat HappensWhere
1Backup report email arrives in monitored mailboxEmail system
2Mail import fetches the email via Microsoft Graph APIBackground process
3Email appears in Inbox (no matching job exists yet)Inbox page
4Operator selects customer and clicks "Approve job"Inbox page
5Mail Parser extracts job configuration from emailBackground process
6Job is created with parser-determined configurationJobs page
7Email is linked to job and removed from InboxRun Checks page
+ +

Approving a Job from the Inbox

+ +

To create a new backup job:

+ +
    +
  1. Navigate to Inbox in the main menu
    2. +
  2. Find a backup report email in the inbox list
    3. +
  3. Click on the email to view its details
    4. +
  4. In the Customer field, select or enter the customer name + +
    5. +
  5. Click the Approve job button (enabled once a customer is selected)
    6. +
+ +

The system will:

+ + +
+ 💡 Customer Selection:
+ The Approve job button is only enabled when a customer is selected. If you type a new customer name, it will be created automatically when you approve the job. +
+ +

What Mail Parsers Configure

+ +

When you approve a job, the Mail Parser automatically determines the following job configuration:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConfigurationHow It's Determined
Backup SoftwareDetected from email subject, sender, or body patterns (e.g., Veeam, Acronis, Windows Server Backup)
Backup TypeExtracted from email content (e.g., Full, Incremental, Differential)
Job NameParsed from email subject or body
Sender Email PatternEmail sender address (used to match future emails)
Subject PatternEmail subject pattern (used to match future emails)
Success/Failure DetectionParser rules for identifying successful vs. failed backups
+ +
+ ⚠️ No Manual Configuration:
+ You cannot manually edit these job settings. All configuration is determined by the Mail Parser to ensure consistency. If a parser incorrectly identifies a field, the parser itself must be updated (Admin only). +
+ +

Processing Similar Emails (Reparse All)

+ +

After approving your first job for a customer, you can automatically process other emails that match the same pattern:

+ +
    +
  1. At the top of the Inbox page, click Reparse all
    2. +
  2. The system will scan all inbox emails and: + +
    3. +
+ +
+ 💡 Workflow Tip:
+ After approving a few jobs from the Inbox, click Reparse all to automatically process any historical emails that match those jobs. This saves time when onboarding a new customer with many existing backup reports. +
+ +

Viewing Job Configuration

+ +

To view a job's configuration after it has been created:

+ +
    +
  1. Navigate to Jobs in the main menu
    2. +
  2. Find the job in the list (organized by customer)
    3. +
  3. Click on the job name to view details
    4. +
+ +

The job detail page shows:

+ + +

Archiving Jobs

+ +

If a backup job is no longer active, you can archive it:

+ +
    +
  1. Navigate to Jobs
    2. +
  2. Find the job you want to archive
    3. +
  3. Click the Archive button
    4. +
+ +

Archived jobs:

+ + +
+ 💡 Archive vs. Delete:
+ Archiving a job hides it from operational views but preserves all historical data. This is useful for jobs that are no longer running but whose history you want to retain. Deleting a job is permanent and removes all associated data. +
+ +

Deleting Jobs

+ +

To permanently delete a backup job:

+ +
    +
  1. Navigate to Jobs
    2. +
  2. Find the job you want to delete
    3. +
  3. Click the Delete button
    4. +
  4. Confirm the deletion
    5. +
+ +
+ ⚠️ Warning - Permanent Deletion:
+ Deleting a job is permanent and will delete all associated backup runs, tickets, remarks, and historical data. This action cannot be undone. Consider archiving the job instead if you might need the data later. +
+ +

Job Lifecycle

+ +

A typical backup job goes through the following lifecycle:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
StageDescriptionVisibility
1. Email in InboxBackup report arrives, no job exists yetInbox page
2. Job ApprovedOperator approves job from InboxJobs page, Run Checks
3. Active JobJob receives regular backup reportsDaily Jobs, Run Checks, Jobs page
4. Schedule LearnedSystem learns backup schedule after several runsDaily Jobs (appears on expected days)
5. Job ArchivedBackup no longer runs, job archived for historyHidden from operational views
6. Job DeletedJob and all data permanently removedCompletely removed
+ +

Common Questions

+ +

Can I manually create a job without an email?

+ +

No. Jobs can only be created by approving emails from the Inbox. This ensures that every job has a valid Mail Parser configuration and prevents misconfiguration.

+ +

Can I edit a job's sender or subject pattern?

+ +

No. Job configuration is determined by Mail Parsers and cannot be manually edited. If a parser is incorrectly identifying fields, contact an administrator to review the parser configuration.

+ +

What if multiple jobs match the same email?

+ +

BackupChecks uses sender and subject patterns to uniquely identify jobs. If multiple jobs could match the same email pattern, the system will match to the first job created. Ensure each backup job sends reports with unique sender or subject patterns.

+ +

Can I change the customer a job is linked to?

+ +

Yes, you can edit a job to change its linked customer. Navigate to the job detail page and use the "Edit" function to select a different customer.

+ +

Next Steps

+ + {% endblock %} diff --git a/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html b/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html index aeeff19..a700bf5 100644 --- a/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html +++ b/containers/backupchecks/src/templates/documentation/customers-jobs/job-schedules.html @@ -4,16 +4,283 @@

Job Schedules

- Understand how job schedules work. + Understand how BackupChecks automatically learns backup job schedules and uses them to predict expected runs.

+

Overview

+ +

BackupChecks does not require you to manually configure backup schedules. Instead, the system automatically learns when backups are expected to run by analyzing historical backup run patterns.

+ +

This learned schedule information is used to:

+ + +
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Key Concept:
+ Schedules are learned automatically by analyzing backup run history. You do not configure schedules manually. After a few backup runs, BackupChecks will infer the schedule pattern.
-

Content

+

How Schedule Learning Works

-

Detailed content will be added here in a future update.

+

BackupChecks uses historical backup run data to infer schedules through the following process:

+ +
    +
  1. Data Collection: As backup reports arrive and create runs, the system records the date and time of each backup
    2. +
  2. Pattern Analysis: After several runs, the system analyzes the dates to identify patterns (e.g., daily, specific weekdays, monthly)
    3. +
  3. Schedule Inference: Once a pattern is detected, a schedule is assigned to the job
    4. +
  4. Continuous Learning: The schedule is updated as more runs are received to maintain accuracy
    5. +
+ +

Minimum Data Required

+ +

To learn a schedule, BackupChecks needs:

+ + + +
+ 💡 Learning Time:
+ For a daily backup, the system can learn the schedule after 3-5 days of successful runs. For weekly backups, it may take 2-3 weeks to establish a reliable pattern. +
+ +

Schedule Types

+ +

BackupChecks can learn and display the following schedule types:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Schedule TypePatternDisplay Example
DailyRuns every day"Daily"
WeeklyRuns on specific days of the week"Weekly: Mon, Wed, Fri"
MonthlyRuns on specific day(s) of the month"Monthly: 1st, 15th"
IrregularNo consistent pattern detected"Irregular" or no schedule shown
+ +

Viewing Job Schedules

+ +

You can view a job's learned schedule in several places:

+ +

1. Jobs Page

+ +

The Jobs page displays the learned schedule in the "Schedule" column for each job.

+ +
    +
  1. Navigate to Jobs
    2. +
  2. Locate the job in the list
    3. +
  3. The "Schedule" column shows the learned pattern (e.g., "Daily", "Weekly: Mon, Wed, Fri")
    4. +
+ +

2. Job Detail Page

+ +

The job detail page shows more detailed schedule information:

+ +
    +
  1. Navigate to Jobs
    2. +
  2. Click on a job name to open the detail page
    3. +
  3. The "Schedule Information" section shows: + +
    4. +
+ +

3. Daily Jobs Page

+ +

Jobs with learned schedules appear on the Daily Jobs page on days they are expected to run.

+ +
    +
  1. Navigate to Daily Jobs
    2. +
  2. Jobs expected to run today are listed here
    3. +
  3. The schedule determines which jobs appear on this page
    4. +
+ +
+ 💡 Daily Jobs Behavior:
+ A job will only appear on the Daily Jobs page if: + + New jobs without learned schedules will not appear on Daily Jobs until a pattern is established. +
+ +

Schedule Accuracy

+ +

Schedule learning is based on pattern recognition and may not be 100% accurate in all cases:

+ +

High Accuracy Scenarios

+ + + +

Lower Accuracy Scenarios

+ + + +
+ ⚠️ Schedule Changes:
+ If a backup schedule changes (e.g., from daily to weekly), the learned schedule will gradually update as new runs are received. During this transition period, the displayed schedule may be inaccurate. Allow a few weeks for the system to relearn the new pattern. +
+ +

No Schedule Displayed

+ +

If a job shows no schedule or "No schedule learned", it means:

+ + + +

In these cases:

+ + +

Schedule Override and Customization

+ +

BackupChecks does not currently support manual schedule configuration or overrides. All schedules are automatically learned from historical data.

+ +
+ 📝 Future Feature:
+ Manual schedule configuration and schedule overrides may be added in a future version. For now, rely on the automatic learning system. +
+ +

Using Schedules in Daily Jobs

+ +

The Daily Jobs page uses learned schedules to show which jobs are expected to run today:

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Job StatusMeaningAction Needed
Ran successfully (green)Job ran today and completed successfullyNo action needed
Ran with failure (red)Job ran today but failedInvestigate failure, create ticket if needed
Expected but not run (yellow/gray)Job is expected to run today based on schedule, but hasn't run yetWait if still early in the day, investigate if overdue
+ +
+ 💡 Workflow Tip:
+ Use the Daily Jobs page as your primary monitoring dashboard. Check it daily to ensure all expected backups have run successfully. Any job showing as "expected but not run" late in the day should be investigated. +
+ +

Schedule Learning Best Practices

+ +

To help BackupChecks learn accurate schedules:

+ + + +

Troubleshooting Schedule Issues

+ +

Schedule Not Appearing

+ +

Possible causes:

+ + +

Solution: Wait for more backup runs to accumulate. Ensure the backup software is running on a consistent schedule.

+ +

Schedule Is Inaccurate

+ +

Possible causes:

+ + +

Solution: Allow time for the system to relearn the pattern based on recent runs. Ensure backups run consistently going forward.

+ +

Job Not Appearing on Daily Jobs

+ +

Possible causes:

+ + +

Solution: Check the Jobs page to see if a schedule is learned. If not, wait for more runs to establish a pattern.

+ +

Next Steps

+ + {% endblock %} diff --git a/containers/backupchecks/src/templates/documentation/customers-jobs/managing-customers.html b/containers/backupchecks/src/templates/documentation/customers-jobs/managing-customers.html index 80f3943..b32477c 100644 --- a/containers/backupchecks/src/templates/documentation/customers-jobs/managing-customers.html +++ b/containers/backupchecks/src/templates/documentation/customers-jobs/managing-customers.html @@ -4,16 +4,283 @@

Managing Customers

- Learn how to manage customer accounts. + Learn how to create, edit, and manage customer accounts in BackupChecks.

+

Overview

+ +

Customers are the organizations or clients whose backup jobs you monitor in BackupChecks. Each customer can have multiple backup jobs associated with them.

+ +

The Customers page provides a central location to:

+ + + +

Accessing the Customers Page

+ +

To access customer management:

+ +
    +
  1. Navigate to Customers in the main navigation menu
    2. +
  2. This page is available to Admin and Operator roles
    3. +
  3. Viewers can see customers but cannot make changes
    4. +
+ +

Customer List

+ +

The Customers page displays a table with the following columns:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ColumnDescription
NameCustomer name (clickable to view/edit details)
JobsNumber of backup jobs configured for this customer. Displays in red and bold if zero jobs are configured.
Autotask CompanyLinked Autotask company name (if Autotask integration is enabled and mapping exists)
ActiveCheckbox indicating whether the customer account is active
ActionsEdit, Delete, and Autotask mapping buttons
+
- 📝 Coming Soon: - This page is under construction. Full content will be added in a future update. + 💡 Job Count Indicator:
+ If a customer shows 0 jobs in red and bold, it means no backup jobs have been approved for this customer yet. Jobs are created by approving emails from the Inbox.
-

Content

+

Creating a New Customer

-

Detailed content will be added here in a future update.

+

To create a new customer account:

+ +
    +
  1. Navigate to the Customers page
    2. +
  2. Scroll down to the New Customer section
    3. +
  3. Fill in the following fields: + +
    4. +
  4. Click Create Customer
    5. +
+ +

The customer will be created and appear in the customer list immediately.

+ +
+ 💡 Best Practice:
+ Create customer accounts before approving backup jobs from the Inbox. This allows you to immediately assign incoming backup reports to the correct customer. +
+ +

Editing Customer Information

+ +

To edit an existing customer:

+ +
    +
  1. Navigate to the Customers page
    2. +
  2. Find the customer in the list
    3. +
  3. Click the Edit button (pencil icon) in the Actions column
    4. +
  4. Modify the customer details in the edit form
    5. +
  5. Click Save to apply changes
    6. +
+ +

All customer fields (name, contact person, email, phone, notes) can be updated at any time.

+ +

Activating and Deactivating Customers

+ +

Customers can be marked as active or inactive using the checkbox in the Active column.

+ +

Active Customers

+ +

Active customers:

+ + +

Inactive Customers

+ +

Inactive customers:

+ + +
+ ⚠️ Impact of Deactivating:
+ When you deactivate a customer, all their backup jobs immediately disappear from operational views (Daily Jobs, Run Checks, Jobs list). This is useful for decluttering the interface when a customer is no longer active. Jobs are not deleted and can be reactivated by marking the customer as active again. +
+ +

Deleting Customers

+ +

To delete a customer:

+ +
    +
  1. Navigate to the Customers page
    2. +
  2. Find the customer you want to delete
    3. +
  3. Click the Delete button (trash icon)
    4. +
  4. Confirm the deletion in the dialog
    5. +
+ +
+ ⚠️ Warning - Permanent Deletion:
+ Deleting a customer is permanent and will also delete all associated backup jobs, runs, tickets, and remarks. This action cannot be undone. Consider deactivating the customer instead if you might need the data later. +
+ +

Autotask Company Mapping

+ +

If Autotask integration is enabled, you can map customers to Autotask companies. This allows BackupChecks to create tickets in the correct Autotask company.

+ +

Mapping a Customer to Autotask

+ +
    +
  1. Navigate to the Customers page
    2. +
  2. Find the customer you want to map
    3. +
  3. Click the Link Autotask Company button
    4. +
  4. A modal dialog will open with a search box pre-filled with the customer name
    5. +
  5. Review the search results and select the matching Autotask company
    6. +
  6. Click Save Mapping
    7. +
+ +

Once mapped, the Autotask company name will appear in the "Autotask Company" column, and any tickets created for this customer's backup jobs will be created in the linked Autotask company.

+ +
+ 💡 Auto-Search Feature:
+ When you open the Autotask mapping dialog, BackupChecks automatically searches for companies matching the customer name. This speeds up the mapping process for most customers. +
+ +

Unmapping a Customer from Autotask

+ +

To remove an Autotask company mapping:

+ +
    +
  1. Click the Unlink button next to the Autotask company name
    2. +
  2. Confirm the unmapping
    3. +
+ +

Existing tickets remain linked to the Autotask company, but new tickets will not be created until the customer is mapped again.

+ +

Exporting Customer Data

+ +

You can export all customer data to a CSV file for backup, reporting, or migration purposes.

+ +
    +
  1. Navigate to the Customers page
    2. +
  2. Click the Export Customers button at the top of the page
    3. +
  3. A CSV file will be downloaded containing: + +
    4. +
+ +
+ 💡 Use Case:
+ Export customer data regularly as a backup, or before performing system maintenance. The exported CSV can be imported later to restore customer data. +
+ +

Importing Customer Data

+ +

You can import customer data from a CSV file.

+ +
    +
  1. Navigate to the Customers page
    2. +
  2. Click the Import Customers button
    3. +
  3. Select your CSV file (must match the export format)
    4. +
  4. Click Upload
    5. +
  5. The system will: + +
    6. +
  6. Review the import summary showing created, updated, and skipped customers
    7. +
+ +
+ ⚠️ Import Behavior:
+ The import process matches customers by name. If a customer with the same name already exists, their information will be updated with the CSV data. Ensure your CSV data is correct before importing. +
+ +

Customer Workflow Summary

+ +

Here's the typical workflow for managing customers in BackupChecks:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
StepActionResult
1Create customer accountCustomer appears in list with 0 jobs
2Approve backup job from InboxJob is linked to customer, job count increases
3(Optional) Map to Autotask companyTickets can be created in Autotask for failed backups
4Monitor backup jobsJobs appear in Daily Jobs and Run Checks
5(If needed) Deactivate customerJobs hidden from operational views
+ +

Next Steps

+ + {% endblock %} diff --git a/docs/changelog-claude.md b/docs/changelog-claude.md index bb27986..a0486eb 100644 --- a/docs/changelog-claude.md +++ b/docs/changelog-claude.md @@ -28,8 +28,8 @@ This file documents all changes made to this project via Claude Code. - Code blocks, tables, and image support - Responsive design for mobile and desktop - **Access Control**: Login required (@login_required) - accessible to all user roles - - **Current Status**: Core infrastructure complete, getting-started section (3 pages) and users section (3 pages) completed with comprehensive content - - **Placeholder Pages**: Remaining 27 pages created with basic structure for future content + - **Current Status**: Core infrastructure complete, getting-started (3 pages), users (3 pages), and customers-jobs (4 pages) sections completed with comprehensive content + - **Placeholder Pages**: Remaining 23 pages created with basic structure for future content - Full content for remaining sections will be added incrementally in future updates ### Changed @@ -45,6 +45,15 @@ This file documents all changes made to this project via Claude Code. - Session Information section (not displayed in User Settings) - Redundant theme/role configuration sections (these are in navbar, not settings page) +### Added +- Completed Customers & Jobs documentation section (4 pages): + - **Managing Customers**: Customer creation, editing, activation/deactivation, Autotask company mapping, CSV export/import, delete operations + - **Configuring Jobs**: Inbox-based job approval workflow, Mail Parser automatic configuration, Reparse All functionality, job archiving and deletion + - **Approved Jobs**: Jobs list overview, job details, status indicators, archive/unarchive workflow, JSON export/import for migration + - **Job Schedules**: Automatic schedule learning, schedule types (daily/weekly/monthly), Daily Jobs integration, schedule accuracy and troubleshooting +- Added user-settings.png screenshot showing password change form +- Enhanced documentation CSS: centered all images horizontally (display: block, margin: 20px auto) + ## [2026-02-07] ### Changed