You can build a curated job board with Airtable and a miniExtensions Interface by publishing only employer listings that a coordinator has reviewed. Keep submissions separate from the public listing table so a new employer submission is a proposal, not an immediately visible job advertisement.
This example is for an association sharing roles relevant to its members. It focuses on listing review, public browsing, and removal of closed roles. It does not collect candidate applications, screen applicants, recommend hiring decisions, or replace an applicant-tracking system.
Separate the employer intake from the public board
At fictional Northbridge Network, an employer submits a role title, location, work arrangement, description, closing date, and application URL. A coordinator checks the copy and destination, asks for corrections if necessary, and publishes an approved version. Job seekers browse the approved board and follow the employer’s own application instructions.
That separation is important because an intake record may contain an unpublished draft, an internal contact address, or review notes. A filtered view is useful, but a dedicated public-copy table makes the intended publication boundary easier to audit. Only copy fields that should be visible to anyone using the board.
Create intake and publication tables
- Listing Submissions: Role title as primary single line text; Employer name as single line text; Submitter email as email; Location as single line text; Work arrangement as single select; Role description as long text; Application URL as URL; Requested closing date as date; Review status as single select; Internal review notes as long text.
- Published Roles: Role title as primary single line text; Employer display name as single line text; Location as single line text; Work arrangement as single select; Approved description as long text; Application URL as URL; Closing date as date; Publication status as single select with Draft, Live, and Closed; Last reviewed as date.
Use fictional examples such as “Operations coordinator” at Cedar Workshop and “Member services assistant” at Harbor Association. Avoid adding real applicants or private employer material during setup. You can maintain a staff-only reference between a submission and its published copy, but do not expose a linked child form that opens the private submission.
Collect a proposal without granting publication access
Create a miniExtensions Form on Listing Submissions. Include employer-supplied details but leave staff review notes and review decisions out of the intake. Make the required fields match your actual review policy: a description and an application destination may be mandatory, while a closing date might be optional for ongoing recruitment.
A coordinator reviews each submission in Airtable and creates or updates its public copy. This is a manual editorial handoff in the proposed workflow, not an automatic moderation feature. Decide what you will accept, how employers request corrections, and who checks whether a role remains open. Submission alone should not imply endorsement, guaranteed publication, or a verified employer.
Configure a public, read-only browsing experience
Use a miniExtensions Interface rather than a login Portal for the public board. The Interface documentation explains that Interfaces do not require login and everyone using one sees the same data. That is appropriate only for the deliberately public Published Roles table, not the intake table.
Create an Airtable view called Live roles, filtered to Publication status = Live. In the Interface table’s Views settings, select that view through Filter and Sort using the Airtable-view source option. Use the normal default List or Gallery layout to present the role title, employer, location, work arrangement, and closing date.
Expose only the approved description and application URL in any expanded form. Set displayed fields read-only and disable visitor record creation and unlinking where available. Review every view and expanded form, not only the list cards. A public display should not become an editable directory merely because the underlying Interface can support edits.
Give readers useful browsing choices
For a small board, start with all live roles. Add predefined views for meaningful groups such as Remote or On-site only if those options match your data. Each view should retain the Live publication condition as well as its category filter. A Remote view that forgets the publication condition could surface a closed or draft role.
Write an informative description instead of relying on a title alone. “Operations coordinator” should explain the team, responsibilities, work arrangement, and how to apply. Ask the employer to supply any location-specific disclosures it is responsible for; do not infer compliance from a completed form.
Treat expiry as an operational responsibility
A closing date field does not itself remove a listing. In the simple baseline, the coordinator reviews due dates and moves expired or withdrawn roles to Closed. If a role is still open, confirm the new date with the employer and update the approved copy. Record Last reviewed so staff can distinguish recently checked listings from stale ones.
If you later use a date formula or an automation to manage expiry, verify its date, timezone, and empty-value behavior separately. Do not tell employers that listings will close automatically until that behavior has actually been configured and tested.
Check publication boundaries with sample records
- Create one Draft, one Live, and one Closed sample role. Browse the public link without signing in and confirm that only the Live record appears.
- Check every category view and direct expansion path for the same boundary.
- Try editing, creating, and unlinking from the public view. Confirm that the available controls match your read-only intent.
- Check the application URL and description on desktop and mobile; do not publish a destination you have not reviewed.
- Close the live sample role, reload the board, and confirm it disappears while the staff record remains in Airtable.
The result is a small, maintainable publication workflow: employers propose, a coordinator reviews, and readers browse approved roles. For general service listings rather than employment opportunities, the service-provider directory guide covers a different audience and browsing purpose.


