User base integration types
  1. Knowledge Base
  2. Integrations
  3. User base integration types

User Integration - Pingboard

ℹ️ This article is intended to assist with the specific settings to Pingboard, if you haven't read the native integration setup article, start with it by clicking here.

Required data: 

  • client_id

  • client_secret (Key).

These are generated by creating a Service Account in the Pingboard in the Manage Service Accounts section, you can check them out by clicking on this article.

 

You can check below the Pingboard fields that Qulture.Rocks platform can integrate:

Team Sync (only available for this provider)


There is an option to enable team sync. When enabled, it causes users to be assigned to teams based on the Pingboard groups they belong to.

Note that this will cause users to be removed from teams that are not in the Pingboard group list.

Examples:

i. John belongs to the Engineering and Backend Chapter groups on the Pingboard;

ii. Maria belongs to the Backend Chapter group in Pingboard and the Product Team in Qulture (the only one in our system);

iii. When the integration runs, the system will:

Create the teams: Engineering and Backend Chapter

Add John to the Engineering and Backend Chapter teams

Add Maria to the Backend Chapter team

Remove Maria from the Product team

The integration has the possibility of synchronizing team leaders. To do this, you must create a field in SOURCE with the names of the teams of which the employee is the leader, separated by semicolons (";"), for example "Product; Marketing".

Translated with DeepL.com (free version)

Questions? #ChatWithUs 😁