---
title: "Integrations "
url: "https://terryberry.productfruits.help/en/article/integrations"
language: "en"
last_updated: "2025-11-29T16:21:52.392Z"
---

# Integrations 

Be Rewarded integrates with your existing systems to streamline access and data management. Single Sign-On (SSO) enables automatic login through your organization's authentication system, while other integrations sync employee data and ensure your recognition program stays up to date.

### **SSO Integration**

Single Sign-On (SSO) lets employees log in with their existing Microsoft credentials. This means no extra passwords and easier access for everyone.

**Supported providers include:**

#### **Microsoft (Azure/Entra ID)**

**Step 1: Create a New Application in Azure**

1.  Sign in to the **Azure Active Directory Admin Center**.
2.  Go to **Enterprise Applications**.
3.  Select **\+ New Application**, then choose **+ Create your own application**.
4.  Input your recognition program’s name and choose Integrate any other application not found in the gallery.

**Step 2: Enable Single Sign-On**

1.  Open the application you just created.
2.  Click **Single sign-on**.
3.  Select **SAML** as the method.

**Step 3: Basic SAML Configuration**

-   Use the **ACS URL** and **Entity ID** provided by Terryberry via email.
-   These values are included in the SSO setup email you receive.

**Step 4: Share Metadata with Terryberry**

-   Copy your **App Federation Metadata URL** from Azure.
-   Send it to your Terryberry Recognition Specialist.

**Step 5: Configure SSO in Be Recognized**

1.  Log in to your Be Recognized (360 Recognition) site.
2.  Go to Settings → Integration.
3.  Select **\+ Add SSO Provider**.
4.  Enter your provider name and identifier.
5.  Paste the Metadata URL.
6.  Click Continue, then Save to finish.

If you see an error or the setup doesn’t validate, contact your Terryberry specialist. They’ll help you resolve issues so SSO works smoothly.

#### **Okta**

**Step 1: Create a New Application in Okta**

1.  In Okta, go to **Applications** → **Create App Integration**.
2.  Choose **SAML 2.0**, then click **Next**. 

**Step 2: General Settings**

1.  Enter your program’s name in the **App Name** box.
2.  (Optional) Upload your logo so employees can easily spot the app.
3.  Click **Next**. 

**Step 3: Configure SAML Settings**

-   Use the **Single Sign-On URL** and Audience URI provided by Terryberry.
-   Check **Use this for the Recipient URL and Destination URL**.
-   Choose Email Address as the **Name ID format**.
-   Click Next.

**Step 4: Finish Setup**

-   Complete the screen (optional survey questions may appear).
-   Click **Finish** to complete the Okta setup.

**Step 5: Share Metadata with Terryberry**

1.  In Okta, click **Identity Provider metadata**.
2.  Copy the metadata URL and send it to your Terryberry Recognition Specialist.
3.  They will return an **XML file** containing your certificate and public key.

**Step 6: Configure SSO in Be Recognized**

1.  Log in to your Be Recognized site.
2.  Go to **Settings** → **Integration**.
3.  Select **+ Add SSO Provider**.
4.  Enter your provider name and identifier.
5.  Paste the **Metadata URL**.
6.  Click **Continue**, then **Save** if the configuration validates.

If you see an error, reach out to your Terryberry specialist to confirm the setup.

#### **OneLogin**

**Step 1: Create a New Application in OneLogin**

1.  In OneLogin, go to the **Applications tab**.
2.  Click **Add App**.
3.  In the search bar, type **SAML CUSTOM**.
4.  Select **SAML Custom Connector (Advanced)**.

**Step 2: Name the Application**

1.  Enter your recognition program’s name in the **Display Name** box.
2.  (Optional) Upload your program’s icon to make it easy for employees to spot.
3.  Click **Save**.

**Step 3: Configure the Application**

-   Go to the **Configuration** tab and input the values provided by Terryberry in your SSO setup email:
    -   Audience (Entity ID)
    -   ACS (Consumer) URL Validator (required)
    -   ACS (Consumer) URL (required)

**Step 4: Advanced Settings**

1.  Go to the **SSO tab**.
2.  Change the **SAML Signature Algorithm** to **SHA-256**.
3.  Copy the **Issuer UR**L and send it to your Terryberry Recognition Specialist.

**Step 5: Configure SSO in Be Recognized**

1.  Log in to your Be Recognized site.
2.  Go to **Settings** → **Integration**.
3.  Select **\+ Add SSO Provider**.
4.  Enter your provider name and identifier.
5.  Paste the **Metadata URL** you copied from OneLogin.
6.  Click **Continue**, then **Save** once validated .

If an error appears, reach out to your Terryberry specialist for troubleshooting.

#### **Google**

**Step 1: Create a New Application in Google Admin**

1.  In the **Google Admin Console**, go to **Apps** → **Web and mobile apps**.
2.  Hover over Add app and select **Add custom SAML app**. 

**Step 2: Enter App Details**

1.  Type your program’s name in the **App Name** box.
2.  (Optional) Add a description or upload an icon.
3.  Click **Continue**. 

**Step 3: Download Metadata**

1.  Download the **IdP Metadata** file.
2.  Send the XML file to your Terryberry Recognition Specialist .

**Step 4: Add Service Provider Details**

-   Change the Name ID Format to Email.
-   Enter the ACS and Entity ID values provided by Terryberry (these will be included in your setup email).
-   Click **Continue**. 

**Step 5: Finish Setup**

-   No extra details are needed here.
-   Click **Finish**. 

**Step 6: Activate the App for Your Domain**

By default, the app is turned off. Do these to activate the app:

-   Find the **BlogIn SAML app** you just created.
-   Click the three dots menu and choose **ON for everyone**.

**Step 7: Configure SSO in Be Recognized**

1.  Log in to your Be Recognized site.
2.  Go to **Settings** → **Integration**.
3.  Select **\+ Add SSO Provider**.
4.  Enter the provider name and identifier.
5.  Paste the **Metadata URL** copied earlier.
6.  Click "**Continue**," then **Save** if the configuration validates. 

If you encounter an error, please reach out to your Terryberry specialist for assistance.

#### **AD FS**

**Step 1: Start Setup in Be Recognized**

1.  In your Be Recognized Admin Tools, go to **Integrations** → **SSO**.
2.  Click **\+ Add SSO Provider**.
3.  Choose **Other** from the Provider type dropdown, then click **Create**.
4.  Name the integration (this name will appear on the login screen).
5.  Copy the **.XML metadata** file generated by Be Recognized — you’ll need it later. 

**Step 2: Configure AD FS**

1.  Open AD FS Management on your server.
2.  Right-click **Relying Party Trusts** and choose **Add Relying Party Trust**.
3.  Select **Claims Aware**, then **Start** .
4.  Choose **Enter data** about the relying party manually and click **Next**.
5.  Enter a **display name** for the application and click **Next**.

**Step 3: Add SAML Settings**

1.  Check **Enable support for the SAML 2.0 WebSSO protocol**.
2.  Enter the **metadata XML URL** from Be Recognized.
3.  Add the metadata URL again for the Relying Party Trust Identifier.
4.  Click **Next** to continue .

**Step 4: Apply Access Control**

1.  Choose the **access control policy** you want for sign-ins.
2.  Confirm your settings and click **Next**.
3.  Select **Configure claims** and click **Close** .

**Step 5: Configure Claims**

1.  In the new window, click **Add Rule**.
2.  Select **Send LDAP Attributes** as Claims.
3.  In the claim rule, enter **Name ID**.
4.  Map attributes as directed (typically linking user identity fields).
5.  Click **Finish**. 

At this point, your AD FS configuration is complete. Employees can now log in to Be Recognized with their AD FS credentials.

#### **Ping Identity | PingFederate or PingOne for Enterprise.**

**Step 1: Start Setup in Be Recognized**

1.  In your Be Recognized Admin Tools, go to **Integrations** → **SSO**.
2.  Click **\+ Add SSO Provider**.
3.  Choose **Other** as the provider type.
4.  Enter a name for the integration (this name will appear on the login screen).
5.  Copy the **.XML metadata file** provided in Be Recognized — you’ll need it for Ping Identity setup.

**Step 2: Configure in Ping Identity**

1.  Open your Ping Identity platform (PingFederate or PingOne).
2.  Follow Ping’s standard instructions for creating a SAML application:  
    [Ping Identity SAML Setup Guide](https://docs.pingidentity.com/r/en-us/solution-guides/htg_config_saml_app).
3.  When prompted for metadata, use the **.XML metadata** from Be Recognized.

**Step 3: Complete Setup**

-   After configuration, your employees will be able to log in using Ping Identity credentials.
-   If you run into errors, check the mapping of attributes (NameID, email, etc.) or reach out to your Terryberry specialist for help.

### **Teams Integration**

Connect Be Recognized with Microsoft Teams. Employees can give and view recognition directly inside Teams, extending program visibility.

#### **Teams Integration for Admins & IT**

Connect Be Recognized with Microsoft Teams so employees can recognize one another and receive notifications right inside Teams.

You’ll need two roles for this setup:

-   **Be Recognized Admin** – with access to Integrations and Communications.
-   **IT Administrator** – with access to Microsoft Entra.

**Note:** Make sure employee emails in Be Recognized match the ones used in Teams. Shared emails won’t work.

**Step 1: Add the Be Recognized App in Teams > Admin**

1.  In Microsoft Teams, **sign in with the same email** tied to your Be Recognized profile.
2.  **Install** the Be Recognized app (version 5.0).
3.  Use the **Connect** command in Teams Chat to pair your account.

**Step 2: Enable the App in Be Recognized > Admin**

1.  In Be Recognized, go to sidebar menu or settings and click **Integrations** → **Chat & Collab**.
2.  Toggle the **Teams switch on**.
3.  Copy the **TeamsCodePairing** and paste it into Teams Chat with the Be Recognized bot.
4.  Approve the popup modal to confirm the connection.

**Step 3: Enable Notifications > Admin**

1.  In Be Recognized, click **Settings** icon → **Communications** → **Notification Settings**.
2.  Under both **Recognition Notifications Settings** and **Award Notifications Settings**, verify that Teams notifications are enabled.

**Step 4: Enable Single Sign-On (SSO) > Admin & IT Administrator** 

1.  In the Be Recognized app for Teams, click **Wall, My Wall, or Recognition** tabs.
2.  Submit the admin consent request when prompted.
3.  Your **IT Administrator** must approve the request in **Microsoft Entra** → **Enterprise Applications** → **Admin Consent Requests**.
4.  Once approved, SSO links each employee’s Teams account to their Be Recognized profile.

**Step 5: Update App Properties > IT Administrator**

1.  In Microsoft Entra, go to **Enterprise Applications** → **Be Recognized** → **Properties**.
2.  Set **Assignment Required** to **No**.
3.  This lets all users connect automatically without needing new requests.

#### **Teams Integration for Employees**

The Be Recognized app in Microsoft Teams makes recognition easy and accessible. You can give recognition, see recognition posts, and get notifications without leaving Teams.

***Using Be Recognized in Teams***

-   **Wall**: See recognition, awards, and announcements across your organization. You can react, comment, and if your program allows it, boost recognition directly from Teams.
-   **My Wall**: View recognition posts sent to you or created by you. This keeps your personal recognition activity in one place.
-   **Recognition**: Open your company’s recognition form, select a colleague, choose an award, and write your recognition story. You can send recognition without leaving Teams.
-   **Chat**: Get notifications whenever you’re recognized, awarded, or tagged. These messages come directly from the Be Recognized app bot .

**Rollout Options:**

**Note**: Once your Admin and IT team finish the initial setup, you don’t need to repeat those steps.

-   If you have a Be Recognized account and a Microsoft Teams account with your organization, you can start using the app by simply adding it in Teams.
-   Your IT team may also enable it automatically for everyone using Microsoft’s [Teams App Setup Policies](https://learn.microsoft.com/en-us/microsoftteams/teams-app-setup-policies) .