Skip to main content
Skip table of contents

Custom fields

Every organization tracks different information about employees. Custom fields let you define exactly what data you capture without being limited to a fixed schema. Employee records are Jira issues with custom fields, so you use Jira's standard field configuration.

Configuring fields

Go to Frank settings and find "Customize employee profiles" under the Jira section. Click "Configure template" to open the Jira screen configuration. Here you can add, remove, and reorder the fields that appear on employee records.

The standard template covers basics like name, role, department, and manager. You can add fields for anything else your organization needs to track: contract details, emergency contacts, certifications, equipment assigned, or visa status.

Common fields to consider

Personal information
Full name, preferred name, pronouns, date of birth, personal email address, phone number, home address.

Work information
Job title, department, team, manager, start date, employment type (full-time, part-time, contractor), work location, remote/office status.

Compensation (mark as sensitive)
Salary, bonus structure, equity grants, pay grade, currency.

Documents and compliance
Contract type, visa status, work permit expiration, certifications held, certification expiration dates.

Emergency contact
Contact name, relationship, phone number.

Sensitive fields

When configuring custom fields, you can mark individual fields as sensitive. Sensitive fields only appear for users in the sensitive data access group — typically HR and managers. Use this for:

  • Compensation and salary information

  • Personal identification numbers

  • Health-related information

  • Performance ratings

  • Disciplinary records

  • Any other data that should have restricted visibility

Regular employees see their own sensitive fields but not those of colleagues.

Best practices

Start with essential fields and add more as your needs evolve. It's easier to add fields later than to clean up unused ones.

Use consistent naming conventions so fields are easy to understand. "Start Date" is clearer than "SD" or "Date1."

Group related fields logically on the screen. Put all contact information together, all compensation fields together, and so on.

Review your sensitive field classifications regularly. As your organization grows, you may need to restrict additional fields or adjust who has access.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.