Knowledge Base / 👥 My Communities & Shared Ecosystem

👥 My Communities & Shared Ecosystem

đź’ˇ Introduction

The Innoloft Ecosystem, a central feature of our LoftOS product, functions as a “network of networks”. This unique setup allows each platform within the ecosystem to connect and interact with others, facilitating the exchange of business opportunities across different platforms.

👩🏻‍💻 Usage

Functioning of the Shared Ecosystem

All platforms built on LoftOS utilize a unified authentication and login system. This means that once a User creates an account on one platform, they can use the same credentials to log into any other platform built on LoftOS.

Furthermore, certain data types are standardized and shared across all platforms. This shared data includes User profiles, Organization profiles, and individual product entries.

Users can access other platforms on LoftOS by logging into another platform directly with their existing credentials.

Data Sharing between platforms

  • User Profile: Once Users join a platform, their personal profile, including name, title, picture, description, department, interests, and organization affiliation, is visible across all platforms.
  • Organization Profile: Users' organization profiles, descriptions, addresses, logos, founding dates, etc., are displayed across all platforms they are part of.
  • Offers: Any Offers posted by Users are visible on every platform they are part of.
  • Requests: Similarly, any Requests submitted by Users are displayed within every platform they belong to.
  • Matches: Matches for Offers and Requests are calculated based on all Offers and Requests within the LoftOS Ecosystem by default. Platform admins can deactivate matching across the ecosystem through module settings.
  • News: News updates are accessible on every platform where Users are members.
  • Awards & Accelerator Programs: Information about Awards and Accelerator programs is visible within every platform where Users are members.
  • Projects: Users' projects are displayed within every platform they belong to.
  • Messages: Users can access their private messages, chat rooms, and group chats on joined platforms.
  • Pipelines: Users can access their pipelines within every platform they belong to.
  • Forms: Access to Forms is available to Users across all platforms.

    • Data from other Modules are not shared across platforms.

    The visibility of certain data may also depend on additional factors, such as the User’s package or specific module settings configured by the platform.

    Types and Attributes: Ecosystem vs. Individual

    In the Module Settings various components (e.g., Organizations, Offers, Requests), Types, and Attributes are categorized as either Ecosystem Types or Individual Types.

  • Ecosystem Types: Only content categorized under predefined Ecosystem Types is shared across platforms.
  • Individual Types: Content based on Individual Types remains exclusive to the platform where it was created and is not shared with other platforms.

    • Similarly, this categorization extends to Attributes associated with these Types:

  • Ecosystem Attributes: Attributes predefined as Ecosystem Attributes and linked to Ecosystem Types are shared across platforms.
  • Individual Attributes: If Individual Attributes are linked to Ecosystem Types, they will only be visible within the platform where they were initially defined.

    • This structured approach ensures clear distinctions between shared and platform-specific content, enhancing data management across the Ecosystem.

    Control Options (Admin)

    Matching:

  • You can disable the matching feature across the Ecosystem via the Module Settings for Offers/Requests. The default setting is enabled (On).

    • Ecosystem Content:

  • Generally, shared data such as Requests and Offers can be displayed on other platforms without User interaction in two specific cases:
  • Organization Profiles without assigned Users (i.e., Users that exist on other platforms but are not linked to any specific platform).
  • Modifications to this configuration can only be implemented by the Innoloft IT Team.

    • Deleting/Removing Content:

  • You can remove Users from a platform if they are registered under that specific platform; otherwise, they can only disassociate from it (remove platform-specific privileges).
  • The protocols for deleting content vary depending on the type of content and need to be further detailed.

    • Control Options for Users

    Data Sharing Control:

  • Users can manage their data-sharing preferences with other platforms by adjusting their memberships within various applications through the "My Communities" feature.

    • Data Deletion Requests:

  • Requests for data deletion across the Innoloft Ecosystem can either be executed by the Innoloft IT team for comprehensive removal or, to a more limited extent, by the customer.

    • âť“ FAQs

    General

    When does content appear on a different platform?

    If a User is part of multiple platforms, the content is available on each platform. This does not automatically mean the content is also directly visible, as other aspects can influence visibility, like packages and database restrictions.

    How can a User control the content on every platform?

    Currently, a User can only control the content of a platform by being part of it. If content should not be shown on a certain platform, the User has to remove himself from the platform. This can be done on the “My Communities” page.

    Is all content shared in the ecosystem?

    Not all content is automatically shared in the ecosystem. If a platform admin created custom types, e.g., Offers or Projects, the content of these custom types is not shared with any other platform. The same applies to content for Groups, Programs, and Events. The content in these modules is exclusive to the platform where it was created.