Evan Mullins

brownbagmarketing

Plugin to pull a job board from greenhouse.io via their API and display it on your WordPress site. Use a shortcode with your URL Token to pull the data. Find your URL token on <a href="https://app.greenhouse.io/configure/dev_center/config" rel="nofollow ugc">this page</a> when you are logged into your greenhouse account. Place <code>[greenhouse url_token="your_url_token"]</code> in your page or post.
Requirements:
<ul>
<li>Must have a greenhouse account.</li>
<li>Enter your URL Token & API key.</li>
</ul>
Initial Setup:
<ul>
<li>For ease of use, setup your URL Token within Settings->Greenhouse. (NOTE: you can also set this inline with shortcode attributes.)</li>
<li>Add shortcode or use the wizard to add a job board to any page or post.</li>
</ul>
Know the code!
<ul>
<li>To post your job board on a page, simply add the shortcode: [greenhouse]. By default, this will display all of the postings you currently have, along with the forms for applying. These forms are actually hosted at Greenhouse.io.</li>
</ul>
Current Features of the [greenhouse] shortcode:
Filter the jobs displayed. These filters can be combined to create complex filters.
Department Filtering
<ul>
<li>Want to filter results by department? Show only one deparment or a couple? Exclude a whole department?</li>
<li>Add the <code>department_filter</code> attribute: <code>[greenhouse department_filter="Value1|Value2"]</code></li>
<li>supports single or multiple values, pipe-delimited</li>
<li>supports either using the department name OR the department id as the value.</li>
<li>supports negated values – Excludes department(s) and display others. (example: <code>department_filter="-Value3|-Value4"</code>)</li>
</ul>
Job Filtering
<ul>
<li>Want to filter results by job? display only specific jobs? Exclude specific jobs?</li>
<li>Add the <code>job_filter</code> attribute: <code>[greenhouse job_filter="Value1|Value2"]</code></li>
<li>supports single or multiple values, pipe-delimited</li>
<li>supports either using the job title OR the job id as the value.</li>
<li>supports negated values – Excludes this job and show others. (example: <code>job_filter="-Value3|-Value4"</code>)</li>
</ul>
Office Filtering
<ul>
<li>Want to filter results by office? Show only jobs from a specific office or exclude a specific office?</li>
<li>Add the <code>office_filter</code> attribute: <code>[greenhouse office_filter="Value1|Value2"]</code></li>
<li>supports single or multiple values, pipe-delimited</li>
<li>supports either using the office name OR the office id as the value.</li>
<li>supports negated values – Excludes office(s) and only display jobs from elsewhere. (example: <code>office_filter="-Value3"</code>)</li>
</ul>
Location Filtering
<ul>
<li>Want to filter results by location? Show only jobs from a specific location or exclude a specific location?</li>
<li>Add the <code>location_filter</code> attribute: <code>[greenhouse location_filter="Value1|Value2"]</code></li>
<li>supports single or multiple values, pipe-delimited</li>
<li>supports location text value, since there is no id associated to locations in greenhouse.</li>
<li>supports negated values – Excludes location(s) and only display jobs from elsewhere. (example: <code>location_filter="-Value3"</code>)</li>
</ul>
Hiding Forms
<ul>
<li>If you don’t want application forms to display and simply want to display listings, just add the <code>hide_forms</code> attribute</li>
<li>ex. <code>[greenhouse hide_forms="true"]</code></li>
</ul>
Sort Jobs
<ul>
<li>Want to sort the jobs listed in your job board? </li>
<li>Add the orderby attribute to the shortcode.</li>
<li>Values allowed: title, date, id, department, office, location and random.</li>
<li>For example: <code>[greenhouse orderby="title"]</code></li>
<li>Need to customize the order more? </li>
<li>There is an order attribute as well, supported values: DESC (default) and ASC.</li>
<li>There is a sticky option as well, force a single job to the top or bottom of the board.</li>
<li>Sticky attribute format: ‘top’ or ‘bottom’ followed by a pipe ‘|’ and then the id for the job to stick.</li>
<li>For example: <code>[greenhouse orderby="department" order="ASC" sticky="top|18590"]</code></li>
</ul>
Group Jobs
<ul>
<li>Want to group the jobs listed in your job board by department, office or location?</li>
<li>Add the group attribute to the shortcode.</li>
<li>Values accepted: department, office or location.</li>
<li>By default the group name will be used as a headline to seperate each group.</li>
<li>To omit group headlines, include shortcode attribute: group_headline=”false”.</li>
<li>For example: <code>[greenhouse group="department" group_headline="false"</code></li>
</ul>
<h3>Coming Soon</h3>
Roadmap
<ul>
<li>Add filter hooks for customizing output</li>
<li>Cleaner, smarter interface</li>
<li>Widget</li>
<li>Templating for your own layout</li>
</ul>

Greenhouse Job Board

Everything is out of control. I was try to use thhis plugin but getting message for API, Token etc and when go to find token there is no potion to signup.

No full permission

Plugin to pull a job board from greenhouse.io via their API.

ghmeh

This plugin allows to authenticate users against GH Portal API with Authorization Flow. 
Once installed, it can be configured to automatically authenticate users (SSO). After consent has been obtained, an existing user is automatically logged into WordPress, while 
new users are created in WordPress database.
<h3>Plugin flow explained</h3>
When a user of your WordPress application visits one of your public pages, a check is done if a user session is currently set. When <code>GH_Portal_SSO_Option_Settings::enforce_privacy</code> is set to <code>TRUE</code>, the plugin will redirect the user from the public page to the Greenhouse Portal SSO page incase no active session was found. The default WordPress authorization check if performed when accessing any of the <code>wp-admin</code> pages. This also allows to user to sign-in using either the Greenhouse account of their existing WordPress acount.
The following applies to any non wp-admin page request incase no user session is found:
The user will be redirected from the current page to the Greenhouse Portal, which acts a proxy between Auth0’s management system and Greenhouse’s Microsoft Identity (OpenID Connect) accounts, to perform it’s authentication through SSO.
A success SSO using the Greenhouse Portal results in an active access token that’s short lived (8 hours). The access token can be used to retrieve data on behalf of the user to which he/she has given consent.
The request for a redirect to the Greenhouse Portal requires a <code>redirect_uri</code> as one of its query parameter. This is the URL to which the proxy should return the user’s access token. By default, the redirect URL is set to <code>admin-ajax.php</code> in conjuction with <a href="https://developer.wordpress.org/reference/functions/admin_url/" rel="nofollow ugc">admin_url</a> and uses <a href="https://codex.wordpress.org/AJAX_in_Plugins" rel="nofollow ugc">WordPress’ AJAX API</a> to further handle the redirect flow.
<pre><code>`
</code></pre>
Temperary Redirect 
Location: 
 https://authorize.my.greenhousegroup.com/authorize
redirect_uri=<redirect/callback URL> 
 `
The above URL will initiate a SSO request to Auth0. Once the user has signed in, the Greenhouse Portal will redirect the user to the given URL in the <code>redirect_uri</code> query parameter. The access token is passed through as a query parameter to the redirect url (e.g. <code>?GHP_authorization_token=xxxxxxxxxxxx</code>).
On successfull redirect, the access token is fetched from the query parameters. An additional request is made to the Greenhouse API to fetch the Greenhouse user information from the retrieved access token.
<pre><code>`
</code></pre>
POST / HTTP/1.1 
Host: 
 https://api.my.greenhousegroup.com/user
Headers: 
 Authorization= 
 x-api-version= 
 `
The Greenhouse user information is used to find an existing WordPress user. When no WordPress user was found, a new one can be automatically created when <code>GH_Portal_SSO_Option_Settings::create_if_does_not_exist</code> is set to <code>TRUE</code> on successfull sign-in.
After finding/creating the WordPress user, a session of 8 hours is created, the duration can be set by <code>GH_Portal_SSO_Option_Settings::expires_in</code> using a numeric measured in seconds.
When no WordPress user account was found or can not be created, the user is redirected to the wp-admin sign-in page with the approriate error message (if any).

Greenhouse Portal SSO

A client plugin that provides SSO (Single-Sign-on) or opt-in authentication against Greenhouse Portal Auth0 implementation.

Greenhouse Job Board vs Greenhouse Portal SSO