👥 HR & onboarding
Onboarding, on a single page they can bookmark.
New hires fill forms. HR fills forms. Managers fill forms. Gravity Tables turns those forms into the dashboard everyone keeps asking for.
The before
What this replaces, specifically.
Onboarding status is a Slack thread
"Did Alex sign the contract yet?", three people asking, two looking, nobody finding.
Application pipeline lives in Notion + email + spreadsheet
No single source. Candidates fall through.
Employee directory is always out of date
Title changes, team moves, manager changes, never reflected.
The after
What Gravity Tables does instead.
Self-serve employee profiles
Staff edit their own row. HR audits via the activity log.
Onboarding checklist per row
Each new hire row shows their progress on a multi-step checklist with inline edit.
Filter by team, department, or status
HR sees the full pipeline. Managers see their team. New hires see only themselves.
The shortcode
Copy. Paste. Customize the IDs.
This is the actual shortcode pattern this use case uses. Drop it on a page, change the form ID, you're shipping.
[gravity_table id="onboarding" filters="team,status" filter_by_user="true" allow_edit="checklist_progress"]Real scenario
A 200-person agency
Before
- Onboarding tracked in a Notion doc
- Manual updates by HR every Friday
- New hires don't know their own status
After
- /onboarding page filtered per user
- New hires see their checklist; HR sees the full pipeline
- Status updates flow from the form back to the table
"Three weeks of building an "onboarding portal" replaced with one shortcode and a Friday afternoon."
Build it
Step-by-step guides for hr & onboarding.
Long-form walkthroughs for the patterns this use case is built on. Copy-ready shortcodes, custom-bulk-action PHP, hook examples.
Guide
How to build a customer portal with Gravity Forms and Gravity Tables
A complete walkthrough for building a self-serve customer portal on WordPress. Per-user filtering, inline editing, role-aware exports, audit trail, all from one shortcode.
Read the guide
Guide
How to set up role-based permissions for Gravity Tables
Restrict who can view, edit, and export a Gravity Tables view based on WordPress roles and capabilities. Server-side enforced, with edge-case handling and recipes.
Read the guide
Guide
How to show users only their own Gravity Forms entries
A complete walkthrough for filtering a Gravity Tables view so each logged-in user sees only the entries they submitted, with role permissions and edge-case handling.
Read the guide
Or browse all guides.
Compare to alternatives
Evaluating other tools for hr & onboarding?
Honest side-by-side comparisons with the alternatives most relevant to this use case.
vs
GravityView
GravityView is the better display tool. Gravity Tables is the better editing-and-operations tool.
See the matrix
vs
wpDataTables
Pick wpDataTables for arbitrary external data. Pick Gravity Tables when the data lives in Gravity Forms.
See the matrix
vs
Tablesome
Tablesome is broader (multiple form plugins). Gravity Tables is deeper (Gravity Forms only, but with editing, charts, maps, and a 3-layer permission model).
See the matrix
Or see the full alternatives matrix with all 6 competitors side by side.
Ready when you are
Stop exporting CSVs. Start shipping dashboards.
10 days of full Pro access. If it doesn't pay for itself in the first week, you don't have to keep it.