Platform Configuration

The purpose of the platform is to offer each of its users the right business value, corresponding to their needs. The mechanisms set up around the financial messaging, the management of the different file formats, the enrichment, the validation or the correction of the transactions, the notification mechanisms, the generation of reports, and many other mechanisms, are specific to each customer. This is why our product offers its customers a set of configurations that will allow them to choose how they want to execute these mechanisms.

To configure his financial messaging management, the user must first have specific roles that will allow him to choose the right options for his needs.

The team remains present at each stage of the configuration to support its customers to offer them the best experience and express good business value through the platform.

All of the documentation provided on the platform configuration is intended to help the user configure the platform himself. For any questions and requests for additional information, please contact the IPC Team directly.

Resource Sharing

With the new organizational tree structure, our product has redefined the way that resources will be shared and how to configure access. These are the types of configurations to which you will have access: Unshared Resources, Shared Resources, and Client Resources. Each of these is described in more detail below.

Unshared Resources: These resources cannot be shared with other organizations. Configurations will only belong to one organization which means they cannot be assigned to other levels of organizations. Also, users can only access and manage configurations from that organization. For example, if a user is under Organization A (Level 2) and his configuration is under Organization A, it means the user can only access and manage resources in Organization A.

Organization structure

These resources will not be shared between organizations because it is specific and tailored to each organization: Channels, Flows, Reports, Templates, Input Connectivity, Notifications, and Business Hours.

Shared Resources: These resources would be shared from the parent organization to sub-organizations. It means that a user can only access and not manage the configurations for the organization they belong to. For example, if a cartridge is defined in Level 1 and the user belongs to Level 2, then the user will be able to access the Level 1 cartridge from Level 2 organization but not manage it. These resources can be shared between organizations: Accounts, Rules, Reference Data, Report Types, Date Configuration, Payment Types, Rulesets, Cartridges, External, and Output.

With resource sharing in place, it will be more efficient to onboard an organization. For example, a client organization may have about 50 rules. With this new change, the user will be able to define and share the 50 rules with its sub-organizations (Levels 2-5) without creating 50 rules in each of the organizations.

Client Resources: These resources would be shared from Client organizations to other organizations within the organizational hierarchy: Secrets and UI Settings. It means that:

  • First, a configuration will belong to a client organization or Level 1.

  • Then, a user belonging to any organization under the client organization can access the configurations but not manage them.