Recruiting
Your careers page, from your open roles.
Where your website runs on our platform, an open role becomes a live job page and a careers index without leaving here, and applications come straight back into the pipeline.
What connects
A publishing connection that renders your open roles as pages on your own domain and routes the application form back here.
What crosses the boundary
- Sent: the vacancy content, and a takedown instruction when it closes.
- Received: form submissions as candidate records with the CV attached.
- Received: page view counts per role, so you can see what is being read.
- Never sent: anything about current employees.
What this lets you do
- Publish and unpublish a careers page without touching the website.
- Collect applications on your own domain rather than a third-party form.
- Keep the careers index current automatically as roles open and close.
- See which roles are being viewed and not applied for.
Setting it up
- 1Link the two workspaces.
- 2Choose the path — usually /careers — and the page style.
- 3Configure the application form fields and what is mandatory.
- 4Publish one role and submit a test application.
Permissions
Scoped to the careers section of your site. Orglume cannot edit the rest of your website and is not granted publishing rights beyond the pages it creates.
What you can ask once this is connected
- “Publish the open roles to our careers page.”
- “How many people viewed the operations role?”
- “Take down the filled vacancy.”
Where it stops
Only for sites on that platform. If your website is elsewhere you get a hosted application link and the same pipeline behind it, which works perfectly well — this is a convenience, not a requirement.
Recruiting
Others in this category.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]