BambooHR

Overview

BambooHR is a Human Resources Information System (HRIS) solution that allows you to define organizational membership. Integrate Cortex with BambooHR to automatically sync team memberships, giving you insight into entity ownership.

How to configure BambooHR with Cortex

Prerequisite

Before getting started, create a BambooHR API key.

Configure the integration in Cortex

  1. In Cortex, navigate to the BambooHR settings page:

    1. In Cortex, click your avatar in the lower left corner, then click Settings.

    2. Under "Integrations", click BambooHR.

  2. Click Add configuration.

  3. Configure the BambooHR integration form:

    • Subdomain: Enter your BambooHR subdomain.

      • This can be found in your app URL, e.g., subdomain.bamboohr.com.

    • API token: Enter your BambooHR API token.

    • Report ID: Optionally, enter a Report ID to filter the list of employees.

      • We recommend entering a Report ID if you have a custom BambooHR Report that has the authoritative list of active employees.

      • This value can be found in the app URL, e.g., subdomain.bamboohr.comreports/custom/New+Hires/REPORTID

    • Employee ownership field: Optionally, enter the ownership field name.

      • If left blank, Cortex defaults to finding the list of employees using their division followed by their department.

  4. Click Save.

How to connect Cortex entities to BambooHR

Import entities from BambooHR

See the Create teams documentation for instructions on importing entities.

Editing the entity descriptor

Ownership of each catalog entity through BambooHR is defined through an owner of type group.

x-cortex-owners:
  - type: group
    name: My Bamboo HR Team
    provider: BAMBOO_HR
    description: This is a description for this owner # optional

The name should be exactly equal to the value in the Team field.

Scorecards and CQL

With the BambooHR integration, you can create Scorecard rules and write CQL queries based on BambooHR teams.

See more examples in the CQL Explorer in Cortex.

All ownership details

A special built-in type that supports a null check or a count check, used to enforce ownership of entities.

Definition: ownership: Ownership | Null

Example

An initial level in a security Scorecard might include a rule to ensure an entity has at least one team as an owner:

ownership.teams().length > 0
All owner details

List of owners, including team members and individual users, for each entity

Definition: ownership.allOwners()

Example

The Scorecard might include a rule to ensure that entity owners all have an email set:

ownership.allOwners().all((member) => member.email != null)
Team details

List of teams for each entity

Definition: ownership.teams(): List<Team>

Example

The Scorecard might include a rule to ensure that an entity owners all have a description and are not archived:

ownership.teams().all(team => team.description != null and team.isArchived == false)

Background sync

Cortex conducts an ownership sync for BambooHR teams every day at 6 a.m. UTC.

Still need help?

The following options are available to get assistance from the Cortex Customer Engineering team:

  • Email: [email protected], or open a support ticket in the in app Resource Center

  • Chat: Available in the Resource Center

  • Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a :ticket: reaction to a question in Slack, and the team will respond directly.

Don’t have a Slack channel? Talk with your Customer Success Manager.

Last updated

Was this helpful?