---
title: "How to add a job board to your community"
description: "Add a job board to Circle, Skool, Mighty Networks, Slack, or Discord. Choose a link, widget, or SDK page, with launch copy and posting rules."
image: /site/images/blog/covers/community-job-board-himeji-castle.webp
publishedAt: 2026-11-17
status: "published"
categories:
  - Getting Started
tags:
  - community job board
  - community monetization
  - embedded job board
---

Give jobs a permanent home, put the link where members already look, and keep using your community for questions and referrals. That is enough to launch a useful job board on Circle, Skool, Mighty Networks, Slack, or Discord.

From there, you can embed live job cards or build a custom jobs section with Cavuno’s SDK. The right choice depends on where your members spend time and how much of the website you control.

If your audience mainly follows an email publication, see [how to add a paid job board to your newsletter](/blog/add-job-board-to-newsletter), including setup options and pricing examples.

*Platform details checked against official documentation on 17 November 2026. The SDK example below was tested in a browser against a live Cavuno board.*

## Make the board useful before making it elaborate

A jobs channel is a good place for conversation. A board gives members a searchable place to find roles after the announcement has scrolled away.

Start with a specific promise: remote design roles, local employers, or entry-level opportunities for people in your field. Add current jobs that fit it, check application links, and confirm permission or source terms before republishing. A small relevant selection gives you something concrete to ask members about.

For a **hypothetical design community on Circle**, the first version could be a public board linked from a Jobs resource post, with introductions and employer discussions kept inside Circle. Members can browse or share opportunities; employers can pay for a listing and an optional mention in the community’s roundup.

Create the board at a Cavuno address or [connect your own domain](https://cavuno.com/docs/board-setup/connect-custom-domain), such as `jobs.yourcommunity.com`. Make **Browse jobs**, **Post a job**, and the route back to your community easy to find.

Before announcing it widely, ask a few members to find a relevant role on their phones. Ask an employer to review the posting offer and a moderator to handle a sample submission. Their questions will tell you more than polishing the page alone.

## Choose a link, a widget, or a custom jobs page

**A hosted-board link** is the simplest option. The board handles browsing and employer posting, while your community sends people to it.

**The jobs widget** puts live cards on an existing page that accepts embeds. Generate it in Cavuno under **Jobs → Embed jobs**, choose your filters, and paste the iframe snippet into the page. Job clicks and searches open the full board in a new tab. The [widget guide](https://cavuno.com/docs/board-setup/embed-jobs-widget) covers the settings.

**The SDK** gives you control over the HTML and interactions on your own website. Use it to place jobs alongside member resources, match your site’s design, and filter the list without leaving the page. There is a copyable example below.

Here is where to put each option on the main community platforms.

### Circle: a Jobs post with live cards

Create a Jobs resource post with links to browse and submit roles. To include the widget, an admin on **Professional or above** can paste its iframe snippet into the post’s **Settings → Custom HTML**. Circle’s [custom HTML guide](https://help.circle.so/p/posts/post-spaces/embed-custom-html-code-within-posts) documents the placement.

The cards appear below the published post, rather than in the editor. In Circle’s mobile apps, members open custom HTML through **See attachment**; it does not appear inline or in email notifications. Keep the normal board link in the post so members have a direct route too.

### Skool: put Jobs on the group card

On **Skool Pro**, open **Settings → Plugins → Links**, choose **Edit**, and add the board URL with a Jobs label. Skool’s [Links feature](https://help.skool.com/article/76-how-to-add-links) allows up to three member-visible links.

Use that persistent link alongside a launch post and occasional relevant job highlights. This guide recommends the documented link route for Skool, not an in-app SDK installation.

### Mighty Networks: add Jobs to navigation

Add a custom link under **Admin → Spaces & Navigation → Navigation Links**. Mighty Networks supports [up to four navigation links](https://docs.mightynetworks.com/for-hosts/setting-up-your-network/can-i-customize-the-navigation-in-my-mighty-network), excluding Free and the legacy Creator and Starter plans.

The link opens a new tab on the web and an in-app browser on mobile. During your pilot, follow a job through to its application destination from that mobile browser.

### Slack and Discord: pin the destination, keep the discussion

In Slack, add the board as a [channel resource link](https://slack.com/help/articles/32562841868307-Add-and-manage-tabs-in-channels-and-direct-messages) using **+ → Link**, then pin an introduction with the posting rules. In Discord, [pin the introduction](https://support.discord.com/hc/en-us/articles/221421867-Pin-Messages-FAQ) in the relevant channel. Both actions require the appropriate permissions.

Link announcements to the current job listing and use threads for questions and referrals. Include the board in welcome resources so new members can find it without searching old messages.

## Be clear about who can see the jobs

A public board can work well alongside a private community. Employers and candidates can discover the listings; members use the community to exchange context and introductions.

If you promise member-only jobs, protect access at the board itself. A member-visible link in Circle or Skool does not restrict someone who has the destination URL.

Cavuno offers [whole-board password protection](https://cavuno.com/docs/board-setup/password-protection) for shared-password access. The normal public widget does not show protected listings while that setting is enabled. Checking individual Circle or Skool memberships, including revoking access when someone leaves, requires a separate membership connection.

## Announce the board with something worth opening

Choose a few relevant roles for launch, brief your moderators, and tell members where to browse and how to submit. Adapt this announcement to match your actual access policy:

```text
We've added a job board for [community audience].

Browse current roles: [Board URL]
The board is [public / restricted to your verified access group].

We're focusing on [roles and locations]. Hiring for this audience?
See the posting options: [Employer URL]

Keep using [channel or space] for questions and referrals.
Report a closed or misleading listing to [contact].

Take a look and tell us which opportunities you'd like to see more of.
```

Add the link to onboarding and bring it into relevant events and discussions. In its [account of running the CMX Job Board](https://www.cmxhub.com/blog/how-cmx-uses-its-job-board-to-power-community-engagement-and-how-you-can-too), CMX describes using Goodword and recommends regular job highlights and member hiring stories. The useful lesson is to give the board a place in the community’s routine. This is CMX’s own account, not a Cavuno case study or a measured retention result.

### Give moderators a short posting policy

Decide what fits before accepting submissions. This starter policy is a template to adapt to your process, not legal advice:

```text
We publish [types of roles] for [audience and locations].

Include the employer, role, location and remote eligibility,
employment type, [required compensation information],
and a working application link.

Submit at [URL]. We review listings within [your actual timeframe].
Paid listings follow the same rules; paid promotion is labelled.
Our cancellation and refund terms are available at [URL].

Tell us when a role closes. Report problems to [contact].
Keep applicant personal information out of public discussions.
```

## Sell an offer you can consistently deliver

Start with one clear package. For example, an employer might buy a 30-day listing, with an optional labelled mention in a scheduled community roundup. That is an illustrative offer; choose the price from your audience, comparable opportunities, and employer feedback.

In Cavuno, connect Stripe and create a **Job posting** product under **Settings → Products**. Set its price and duration, then use the [pricing-plan guide](https://cavuno.com/docs/monetization/create-pricing-plans) to verify checkout, including any real-payment implications.

Put promised community mentions on your calendar. Buying a board product does not itself publish a Circle post or Slack message. Confirm the placement date and keep a record of delivery.

If members get a posting benefit, explain how you check eligibility. Cavuno employer membership refers to membership on the board, not automatic recognition of a Circle or Skool account. The [pricing guide](https://cavuno.com/blog/job-board-pricing-models) covers bundles and recurring offers when demand supports them.

## Let members search alongside your resources

A member looking for a role needs more than a few highlights. This panel lets them search by keyword, combine work-arrangement and employment filters, and load more results without leaving your website. Company, location, remote eligibility and available salary details make the shortlist easier to assess.

Place it on a companion website alongside your community resources, or in a website template you control. The example below uses live listings from Robotics Engineer Jobs.

![Searchable community jobs panel](/site/images/blog/newsletter-community/community-panel.png)

For example, a member can search for “perception,” choose Remote and Full-time, and compare the matching roles without leaving the page. Location eligibility and salary details, when supplied, stay visible in the results.

![Community jobs filtered by perception, Remote and Full-time](/site/images/blog/newsletter-community/community-filtered.png)

Copy the complete block into a page that permits custom JavaScript, then replace `key`, `boardUrl` and `employerUrl`. Use it once per page. This is the custom-website route; for Circle’s documented iframe placement use the standard widget, and for Skool use the Jobs link described earlier.

```html
<section id="community-jobs" aria-label="Community opportunities">
  <style>
    #community-jobs { --accent: #186b60; color: #18333d; background: #fff; border: 1px solid #d9e3e4; border-radius: 12px; padding: 24px; font: 14px/1.5 system-ui, sans-serif; }
    #community-jobs * { box-sizing: border-box; }
    #community-jobs [hidden] { display: none !important; }
    #community-jobs h2 { margin: 0 0 6px; font: 28px/1.2 Georgia, serif; }
    #community-jobs p { color: #586c73; margin: 8px 0 16px; }
    #community-jobs form, #community-jobs footer { display: flex; flex-wrap: wrap; align-items: end; gap: 12px; }
    #community-jobs label { display: grid; gap: 5px; flex: 1 1 140px; }
    #community-jobs label:first-child { flex-basis: 100%; }
    #community-jobs input, #community-jobs select, #community-jobs button { font: inherit; border: 1px solid #d9e3e4; border-radius: 6px; padding: 10px 12px; min-height: 44px; min-width: 0; max-width: 100%; background: #f5f8f8; color: #18333d; }
    #community-jobs input { font-size: 16px; width: 100%; }
    #community-jobs button { cursor: pointer; }
    #community-jobs button[type=submit] { background: var(--accent); color: #fff; border-color: var(--accent); }
    #community-jobs button:disabled { opacity: .6; cursor: wait; }
    #community-jobs [data-more], #community-jobs [data-retry] { margin-bottom: 16px; }
    #community-jobs :focus-visible { outline: 3px solid var(--accent); outline-offset: 3px; }
    #community-jobs a { color: var(--accent); text-underline-offset: 3px; }
    #community-jobs a:hover { text-decoration-thickness: 2px; }
    #community-jobs ul { list-style: none; padding: 0; margin: 0 0 16px; }
    #community-jobs li { padding: 16px 0; border-top: 1px solid #d9e3e4; overflow-wrap: anywhere; }
    #community-jobs li a { font-size: 17px; font-weight: 650; display: block; }
    #community-jobs small { display: block; color: #586c73; font-size: 13px; margin-top: 5px; }
    #community-jobs footer { border-top: 1px solid #d9e3e4; padding-top: 16px; gap: 12px 24px; }
  </style>
  <h2>Find your next role</h2>
  <p>Explore opportunities from our community’s job board.</p>
  <form role="search" aria-label="Search community jobs">
    <label>Keyword<input name="q" type="search" maxlength="200" placeholder="Job title, company or skill"></label>
    <label>Work arrangement<select name="work"><option value="">Any setup</option><option value="remote">Remote</option><option value="hybrid">Hybrid</option><option value="on_site">On-site</option></select></label>
    <label>Employment<select name="type"><option value="">All types</option><option value="full_time">Full-time</option><option value="part_time">Part-time</option><option value="contract">Contract</option><option value="internship">Internship</option></select></label>
    <button type="submit">Search jobs</button><button type="button" data-clear>Clear</button>
  </form>
  <p role="status">Loading jobs…</p>
  <ul aria-label="Job results" aria-busy="true"></ul>
  <button type="button" data-more hidden>Load more</button>
  <button type="button" data-retry hidden>Try again</button>
  <footer><a data-browse>Browse full board ↗</a><a data-post>Post a job ↗</a></footer>
  <noscript>Enable JavaScript to search here.</noscript>
</section>
<script src="https://cdn.jsdelivr.net/npm/@cavuno/board@4.73.0/dist/browser/cavuno-board.global.min.js" integrity="sha384-ILNI5QDO/sVoViIePEmeHx79yHhr+9/ICgue77VEhbquCJ6UdoJtzImx2h5B0h0T" crossorigin="anonymous"></script>
<script>
  (() => {
    // Replace these three values. Use a publishable key, never an operator key.
    const key = 'pk_YOUR_BOARD';
    const boardUrl = 'https://jobs.example.com';
    const employerUrl = 'https://jobs.example.com/employers';
    const root = document.getElementById('community-jobs');
    const form = root.querySelector('form'), list = root.querySelector('ul');
    const status = root.querySelector('[role="status"]');
    const more = root.querySelector('[data-more]'), retry = root.querySelector('[data-retry]');
    root.querySelector('[data-browse]').href = boardUrl;
    root.querySelector('[data-post]').href = employerUrl;
    const workNames = { remote: 'Remote', hybrid: 'Hybrid', on_site: 'On-site' };
    const types = { full_time: 'Full-time', part_time: 'Part-time', contract: 'Contract', internship: 'Internship', temporary: 'Temporary', volunteer: 'Volunteer', other: 'Other' };
    const periods = { per_hour: 'hour', per_day: 'day', per_week: 'week', per_month: 'month', per_year: 'year' };
    let filters = {}, cursor, request, failedMore = false;
    const seen = new Set();
    function text(tag, value) {
      const node = document.createElement(tag);
      node.textContent = value;
      return node;
    }
    function card(job) {
      const item = document.createElement('li');
      const title = text('a', job.title);
      title.href = job.links.public || boardUrl;
      const location = job.remoteOption === 'remote'
        ? `Remote · ${job.remoteLocationLabel || 'Check eligible locations'}`
        : job.locationLabel || 'See listing for location';
      item.append(title, text('small', `${job.company?.name || 'Employer'} · ${location}`));
      const terms = [workNames[job.remoteOption], job.customEmploymentType?.label || types[job.employmentType]].filter(Boolean);
      const salary = CavunoBoard.format.formatSalaryRange('en', job.salaryMin, job.salaryMax, job.salaryTimeframe, job.salaryCurrency, 'code');
      if (salary) terms.push(`${salary.bound === 'from' ? 'From ' : salary.bound === 'upTo' ? 'Up to ' : ''}${salary.text}${periods[salary.timeframe] ? ` / ${periods[salary.timeframe]}` : ''}`);
      if (job.isSponsored) terms.push('Sponsored');
      item.append(text('small', terms.join(' · ')));
      return item;
    }
    async function load(append = false) {
      request?.abort();
      const active = request = new AbortController();
      failedMore = append;
      more.disabled = true;
      retry.hidden = true;
      list.setAttribute('aria-busy', 'true');
      status.textContent = append ? 'Loading more jobs…' : 'Searching…';
      if (!append) { list.replaceChildren(); seen.clear(); cursor = undefined; more.hidden = true; }
      try {
        const board = CavunoBoard.createBoardClient({ board: key });
        const page = await board.embed.jobs({ ...filters, limit: 5, ...(append ? { cursor } : {}) }, { signal: active.signal });
        if (active.signal.aborted) return;
        const incoming = page.data.filter(job => !seen.has(job.id));
        const cards = incoming.map(card);
        incoming.forEach(job => seen.add(job.id));
        list.append(...cards);
        cursor = page.nextCursor;
        more.hidden = !(page.hasMore && cursor);
        status.textContent = seen.size ? `${seen.size} jobs shown${Number.isFinite(page.count) ? ` · ${page.count.toLocaleString('en')} matching` : ''}` : 'No matches. Try a broader keyword or clear the filters.';
        if (append) cards[0]?.querySelector('a').focus({ preventScroll: true });
      } catch {
        if (active.signal.aborted) return;
        status.textContent = append ? 'Couldn’t load more. Your results are still here; try again.' : 'Jobs couldn’t load. Try again or browse the full board.';
        retry.hidden = false;
        more.hidden = true;
      } finally {
        if (request === active) { more.disabled = false; list.setAttribute('aria-busy', 'false'); }
      }
    }
    function search() {
      const data = new FormData(form), q = data.get('q').trim();
      filters = { ...(q ? { q } : {}), ...(data.get('work') ? { remoteOption: [data.get('work')] } : {}), ...(data.get('type') ? { employmentType: [data.get('type')] } : {}) };
      load();
    }
    form.addEventListener('submit', event => { event.preventDefault(); search(); });
    form.addEventListener('change', event => { if (event.target.tagName === 'SELECT') search(); });
    root.querySelector('[data-clear]').addEventListener('click', () => { form.reset(); search(); form.elements.q.focus(); });
    more.addEventListener('click', () => load(true));
    retry.addEventListener('click', () => load(failedMore));
    load();
  })();
</script>
```

Change the heading and `--accent` color to fit your community. The CSS is scoped to `#community-jobs`; it leaves your navigation and resource pages alone. Filters apply as members change them, Enter submits a keyword search, and Clear restores the full list. Failed requests keep a route to the hosted board, with a retry button inside the panel.

Use the widget when you want a ready-made block. Use this SDK panel when you want to control the layout and keep searching and pagination on your website. Full job details and employer purchases open on the hosted board.

You need a public board on a [plan with API access](https://cavuno.com/docs/billing/plans-and-pricing); the [CDN guide](https://cavuno.com/docs/sdk/installing/cdn) covers script-security settings. Use only publishable keys in the browser. This panel serves public job cards: it does not check Circle or Skool membership, and the embed API is not gated by the candidate paywall.

## Keep bringing members back to relevant opportunities

Before each roundup, check that the selected roles are current and fulfil any paid placements. Resolve reports, remove closed opportunities, and ask employers whether the interest was useful.

When a member finds a role through the community, ask permission to share the story. Keep measured clicks, applications, and reported hires distinct. Those conversations help you improve the board without treating page views as proof of retention.

Start with a useful selection and a visible destination. [Create the board with Cavuno](https://cavuno.com), make it part of your community’s routine, and use the widget or SDK when it improves how members find their next role.
