Job Fields capture details specific to a job that Kula doesn't track by default — things like an internal project code, a hiring initiative tag, or a compliance flag. Some job fields are built in and fixed; anything beyond that is a custom field you define yourself.

Default fields vs. custom fields

The Job Fields settings page shows two sections:

• Default Info — Department, Workplace, Office, Work Type, Skills, Education, and Experience. These are built in and, as of this writing, cannot be edited or reconfigured (for example, you can't currently make Skills optional if it's required, or vice versa) — though the ability to toggle default fields between mandatory and optional is in active development and may become available.

• Custom fields — anything you add yourself, using the field types below.

Creating a custom job field

• Settings → Custom Fields → Job Fields.

• Click Add Custom Job Field.

• Enter a Field Name (mandatory).

• Choose a Field Type (mandatory, and cannot be changed once the field is created): Short Text, Long Text, Single Select, Multi-Select, Date, Number, URL, Yes/No, or Rich Text.

• Add a Description if useful for context.

• Enter a Token — currently required for every field, regardless of whether you plan to use it. Avoid periods (.) or brackets ({ }) in the token value.

• Add Placeholder text — the hint shown in the field before anyone fills it in.

• Optionally restrict where the field appears: "Only Show For Jobs In These Offices" and "Only Show For Jobs In These Departments."

• Check Required Field if the field should block job creation until it's filled in.

• Click Add.

Editing works the same way — open the field from the Job Fields list and update it. Deleting removes the field via a confirmation modal.

About the Token field

• The Token is what lets a custom field's value be pulled into an email template or another document as a placeholder — it's genuinely only necessary if you intend to reference that field's value somewhere else in Kula.

• Despite that, Kula currently requires a token on every custom field regardless of whether you plan to use it that way; there's a standing request to make this optional that hasn't been implemented yet.

Good to know

• Field type can't be changed after creation. If you pick the wrong type, you'll need to delete and recreate the field rather than convert it.

• Office/department scoping is a real feature but has had real bugs historically. If a custom field seems to be showing on jobs outside the offices or departments you scoped it to, this has happened before (since fixed) — worth flagging to support if you see it rather than assuming it's expected behavior.

• Deleting a field isn't guaranteed to be instantly clean everywhere. A past bug allowed soft-deleted custom fields to still be validated during job creation, blocking jobs from saving — since fixed, but if job creation ever fails for no obvious reason, a recently deleted custom field is worth ruling out.

• You currently can't see custom job field values as columns on the Jobs list page. If you need to compare a custom field's value across many jobs at once, that view isn't available today — you'd need to open each job individually.

• The Default Info fields (Department, Office, Work Type, Skills, Education, Experience) can't be made mandatory or optional today, even though that flexibility is in active development. Treat them as fixed for now.

FAQ

• What's the difference between a default field and a custom field? Default fields (Department, Office, Work Type, Skills, Education, Experience) are built into Kula and currently fixed. Custom fields are anything you create yourself to capture something Kula doesn't track out of the box.

• Do I need to fill in a Token if I'm not using this field in a template? Kula requires it today regardless, even though it's really only useful if you plan to reference the field as a placeholder elsewhere. There's an open request to make it optional, but it's not implemented yet.

• Can I change a custom field's type after I've created it? No — the field type is locked in at creation. You'd need to delete and recreate it with the new type.

• I scoped a custom field to a specific office, but it's showing up on jobs in other offices — is that a bug? It's happened before and was fixed, but if you're seeing it, it's worth reporting rather than assuming it's expected — office/department scoping should restrict visibility to only the jobs you selected.

• Can I see a custom field's values across all my jobs in a table or list view? Not currently — job-level custom fields aren't available as columns on the Jobs list page yet.

• Can I make a default field like Department or Skills optional (or required) for my account? Not yet — default fields are fixed today, though the ability to customize their mandatory/optional status is in development.

Need help?

If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.