Restricting Job Titles by Business Entity Type

What this configuration does

In Glide's Business Account Opening flow, applicants are asked for a job title (sometimes labeled "Occupation") on the business owner details page. By default this is a free-text field, which means applicants can enter anything: "Owner", "CEO", "Big Cheese", typos, or titles that don't legally exist for the entity type they selected.

This configuration replaces the free-text input with a dropdown of job titles filtered by the business's legal entity type (Corporation, LLC, Sole Proprietorship, etc.).

Turn it on when you want to:

• Standardize the data flowing into your core (no typos, no invented roles).

• Make sure every owner's role is legally valid for the entity type they selected.

• Improve accuracy of anything downstream that depends on title: signature pages, beneficial ownership verification, signer permissions, vendor skip rules, etc.

What the applicant sees

When the feature is OFF (default)

1. Business name page: applicant selects the Entity Type alongside Legal Name.

2. Owner details page: applicant types their job title into a free-text input (up to 40 characters). No validation against entity type. Anything is accepted.

3. Dashboard: your back-office team sees a free-text occupation field when viewing or editing an owner.

You can optionally show a subtext above the free-text field to nudge applicants toward specific titles, but it's only a suggestion.

When the feature is ON

1. Owner details page now collects both:

   • Entity Type (only the primary applicant sees this; invited signers inherit it).

   • Job Title, as a dropdown whose options depend on the entity type chosen above.

   • If the applicant changes the entity type, the job title field clears automatically so they can't carry over a stale selection.

2. Business name page no longer asks for Entity Type, since it was already collected. The applicant only sees the question once, earlier in the flow.

3. Dashboard: back-office staff see the same restricted dropdown when editing an owner. Data stays consistent across member-facing and internal views.

What you can customize

1. Job titles per entity type

You define the mapping of Entity Type → Allowed Job Titles for your credit union. Glide loads this into your config.

Example mapping:

You can add, remove, or rename titles per entity type at any time. Every supported entity type must have at least one title defined, otherwise the dropdown will be empty for that structure.

2. Entity type list

The entity types themselves are governed by your FI's business structure list, not by this configuration. Most credit unions adjust the entity type list and the title mapping together so they stay in sync. Common variations across FIs include adding "Association & Clubs", splitting nonprofit vs. for-profit corporations, or simplifying the partnership categories.

Related configuration: ChexSystems skip rules

Your FI can also uses an entity type + title map for a separate purpose: deciding which invited business signers skip ChexSystems checks. It does not affect what applicants see in the dropdown. It only governs which invited owners or signers bypass the ChexSystems report run based on the title they're assigned.

Worth knowing if you're configuring both at the same time, since the two lists usually need to be consistent.

Setup checklist

When you're ready to turn this on, send Glide:

1. Confirmation that you want this configuration on

2. Your final business entity type list, if it differs from the default.

3. Your entity type to job title mapping, with at least one valid title per entity type.

After the config change ships, applicants will go from "type any occupation" to "pick a valid title for the entity type you selected", and your back-office staff will see the same restricted dropdown in the dashboard.