{
  "schema": "mcsj-recipe-v1",
  "id": "creating-new-mcsj-users",
  "title": "Creating New MCSJ Users",
  "module": "System",
  "source": "C:/Solutions/michel/knowledge/foster/mcsj_assets/tip_sheets/create_new_mcsj_users.json",
  "confidence": "source-compiled",
  "timing_target_seconds": 30,
  "requires_live_mapping": true,
  "short_answer": "The best starting point is usually to copy or duplicate an existing user with the same job duties, then change the new user's name, contact information, and security as needed. This keeps access consistent, but the system administrator should still review each module's security before the user goes live.",
  "steps": [
    {
      "phase": "navigate",
      "action": "Open User Maintenance",
      "path": "System Utilities \u00bb User Maintenance",
      "note": "User setup and security changes should be handled by the customer's system administrator."
    },
    {
      "phase": "operate",
      "action": "Pick a model user first",
      "checks": [
        "Find an existing employee with the same role or department.",
        "Use that user as the security/access model when possible.",
        "Avoid starting from scratch unless the access is truly unique."
      ]
    },
    {
      "phase": "operate",
      "action": "Copy, then personalize",
      "checks": [
        "Copy or duplicate the model user for the new employee.",
        "Change the user ID, name, email, and phone/contact details.",
        "If MFA is used, set the user's email/text authentication option."
      ]
    },
    {
      "phase": "operate",
      "action": "Review module security",
      "checks": [
        "Confirm the copied access matches the new employee's job duties.",
        "Remove modules or levels the employee should not have.",
        "Use the User Listing to review security and inactive users if needed."
      ]
    },
    {
      "phase": "operate",
      "action": "Test before handing off",
      "checks": [
        "Have the user sign in and confirm the expected menus open.",
        "Confirm they cannot access areas outside their role.",
        "Keep a screenshot or User Listing export for setup proof."
      ]
    }
  ],
  "watch_outs": [
    "Do not copy from a power user unless the new employee needs that same high-level access.",
    "Do not leave old or inactive users active; review them separately in User Maintenance.",
    "If a worker ID, department head, tester, or module-specific ID is needed, link it after the MCSJ user exists."
  ],
  "completion_contract": [
    "Use live chestervillagenydb only",
    "Verify record/batch ID before write",
    "Capture visible after-proof",
    "For batches, Save alone is incomplete; verify and Update/Post when applicable"
  ]
}