Overview

General Codes are configurable lookup tables that drive various system behaviors. Instead of hardcoding values like payment reasons, decline categories, or status labels, the system reads them from General Codes, making them admin-configurable without engineering involvement.

πŸ—’οΈ Lookup Tables

Configurable lists of values used throughout the platform (payment reasons, decline reasons, status transitions, etc.).

πŸ€– AI Configuration

Agent prompt configurations are stored as general codes of type agent β€” see the Agents page for the dedicated UI.

βš™οΈ System Behavior

Many system behaviors are driven by code values β€” changing a code changes the behavior without a code deployment.

Types of General Codes

General codes are organized by type. Each type is a named category of related codes.

Common code types:

  • SMEPaymentShidduch β€” reasons for SME payments, with optional extra.amount for pre-filled payment amounts
  • DeclineReason β€” the reasons users can select when declining a suggestion
  • UnmatchReason β€” reasons available when unmatching an active introduction
  • ProfileStatus β€” configuration for each user profile status (label, color, allowed transitions)
  • agent β€” AI agent configurations (prompt, model, temperature, API key) β€” use the Agents page for a dedicated editing UI
  • AutoUpdateProfile β€” rules for the daily automatic profile update lambda
  • matchCheck β€” yes/no questions Jev asks about a member and candidate before staff suggest the pair; each row’s name is the question text, and the Extra JSON sets threshold, labels, and scope. Ops guide: Match check questions (reference)

Filter the General Codes list by type using the Type dropdown at the top of the screen to focus on a specific category.

Creating & Editing Codes

1
Find the code type
Go to Settings β†’ General Codes and filter by the type you want to edit.
2
Add or edit a code
Click Add Code to create a new entry, or click an existing code to open the edit dialog. Fill in the key, display label, optional description, and the extra JSON field if needed.
3
Save
Click Save. The new or updated code is immediately available throughout the system wherever that code type is used.

⚠️ Deleting Codes

Deleting a code that is referenced by existing records (e.g., a payment reason already used on a payment) can break those records' display. Prefer deactivating a code (setting it inactive) over deleting it. Inactive codes are no longer available for new selections but don't break existing references.

The Extra Field

Many general codes have an extra JSON field that allows storing additional structured data alongside the basic key/label pair.

Examples of extra usage:

  • SMEPaymentShidduch codes: extra.amount pre-fills the payment amount when this reason is selected
  • Agent codes: extra stores the model name, temperature, max tokens, and encrypted API key for the AI agent
  • ProfileStatus codes: extra may store the hex color code for the status badge
  • matchCheck codes: extra.threshold (0–1 hold cutoff), extra.bothWays, extra.humanTopic (short Admin label), extra.scope (pair or member) β€” see match check questions β†’ Extra JSON fields

The extra field is a freeform JSON object. The valid keys and their meanings depend on the code type. Consult your platform documentation or engineering team for the expected structure for each type.

πŸ”’ API Key Encryption

For agent type codes, the apiKey value in extra is encrypted at rest and shown masked in the UI and API responses. You can update it by entering a new value β€” it will be re-encrypted on save.