Customer onboarding

@customers @onboarding
Feature: Customer onboarding
  As an admin
  I want to create a customer and assign an owner and a reviewer
  So that the team can start work against the right owner

  Every piece of work starts from a clean customer record with the right people attached.

  Background:
    Given an admin is signed in
    And the list of active staff members is available for assignment

  Rule: A customer record starts with a distinct owner and reviewer

    Scenario: Create a customer and assign an owner and a reviewer
      Given an admin opens the create-customer form
      When they enter the customer details and choose an owner and a reviewer
      Then the customer is created with that owner and reviewer
      And the team can start work against the record

    Scenario Outline: An invalid assignment is refused on the server
      Given an admin is creating or editing a customer
      When the assignment has "<fault>"
      Then the server refuses the change with the real reason

      Examples:
        | fault                                     |
        | the same person as owner and reviewer     |
        | an owner who is inactive                  |
        | a name that duplicates an existing customer |

  Rule: A new record can be pre-filled from an uploaded document that passes admission

    Scenario: Pre-fill from an uploaded document
      Given an admin uploads a document while creating a customer
      And the document has passed upload admission (type, size and content checks)
      When the in-house document reader reads it
      Then the form is pre-filled from it
      And the admin can correct any field before saving

    Scenario: An unreadable document does not pre-fill
      Given an admin uploads a document that is refused at admission or cannot be read
      When the create form loads
      Then no pre-fill is applied and the admin is told to enter the details by hand

  Rule: Only an admin changes the owner or reviewer

    Scenario: A non-admin cannot change the assignment
      Given a staff member who is not an admin opens a customer record
      When they try to change the owner or reviewer
      Then the change is refused on the server, not only hidden in the screen

  Rule: Staff see only the customers they own

    Scenario: A staff member cannot see another staff member's customers
      Given a staff member who owns some customers
      When they open the register
      Then they see only the customers they own, scoped by tenant and role

  Rule: The register is searchable and an export is scoped like the screen

    Scenario: Search and filter the register
      Given many customers exist
      When an admin searches and filters the register
      Then only the matching customers are listed

    Scenario: An export runs the same authorised query as the screen
      Given a filter is applied to the register
      When an admin exports the list
      Then the export runs the same authorised, tenant-scoped query as the screen
      And it contains the same records as the filtered view

  Rule: Two admins editing one record do not overwrite each other

    Scenario: A concurrent edit is detected
      Given two admins open the same customer record
      When one saves and then the other saves over a stale copy
      Then the second save is refused and the admin is shown the newer version