​
Overview

In advanced scenarios, client platforms may need to extend and store user profile data internally. Opigno 4 offers a structured approach to separate learning and private content, allowing for flexible customization while ensuring security and organization.

​
Extending User Profiles

​
How It Works:

  1. Enable and Configure the Opigno Connect Module:
    • Activate the opigno_connect module.
    • Configure the client_key and client_secret to authorize API communication with the server.
  2. Generate Unique Identifiers for Users:
    • Assign a universally unique identifier (UUID) to each user.
    • Define and configure any custom fields required for user profiles.
  3. Use UUID for Seamless Integration:
    • Reference the UUID wherever user-specific data is needed.
    • Ensures consistency and simplifies integration.
  4. Backend Entity Creation:
    • Create a new entity type on your backend to manage extended user profile data.
    • Customize fields based on specific business or application needs.

​
Requests and Flexibility:

  • Single or Combined Requests:
    • Choose between making two distinct requests or combining them, depending on your backend structure.
    • For example, a second request may fetch training-related data, such as course progress and score points.

​
Extending Training Entities​

The same approach applies when customizing training data.

​
How It Works:

  1. Enable and Configure the Opigno Connect Module:
    • Activate the opigno_connect module.
    • Set up the client_key and client_secret for API access.
  2. Create and Customize Training Entities:
    • Define a new entity type on your backend to represent extended training data.
    • Add custom fields to capture additional training-related details.
  3. Link Training Data to Custom Entities:
    • Use the opigno_connect module or an autocomplete field to associate training data with your custom entity.

​
Requests and Flexibility:

  • Single or Combined Requests:
    • Make separate requests for user and training data or combine them, depending on your backend implementation.

​
Internal Notes

  • The creation and management of new entities must be handled on your backend system.
  • A flexible backend implementation enables decoupled integration, allowing you to structure API requests and entity relationships to match your specific requirements.
By following these guidelines, you can extend Opigno’s functionality to support custom user profiles and training entities effectively.