About Partners

About Partners¶

Partners represent the organizations that participate in your data integration ecosystem. In FeedXChange, partners serve as the foundational organizing principle. Every connection, template, and integration is associated with a specific partner.

Figure 1. Partners list view

Partner Fundamentals¶

A partner in FeedXChange represents:

An external organization participating in your loyalty program
Your own company (for single-organization implementations)
Different departments or business units within your organization

Examples of partners:

Co-branded credit card companies
Car rental agencies
Retail chains in a coalition program
Hotel partners
Your own organization's internal divisions

Partner Types and Program Models¶

Coalition Programs¶

If you operate a coalition program with multiple participating organizations:

Create separate partners for each participating organization
Designate your organization as the "hosting" partner
Each partner manages their own connections, templates, and integrations
Partners can only see and manage their own resources (unless they're hosting partners)

Single Organization¶

If you're not managing a coalition program:

Create one partner representing your own company
All integrations and connections are associated with this single partner
Simpler administration with centralized management

Hosting Partners¶

A hosting partner is the organization that owns and manages the loyalty program.

Hosting Partner Characteristics:¶

Program ownership - Controls the overall loyalty program
Cross-partner visibility - Can see integrations from all partners
Administrative privileges - Manages program-wide settings and participants
Multiple hosting partners - Programs can have multiple hosting partners (such as different departments within the same company)

Important

Limit hosting partners to those you want to have visibility into all integrations for the program. Hosting partner status grants visibility across the entire ecosystem.

Partner Information Requirements¶

Each partner includes:

Basic details - Name, type, and unique partner code
Contact information - Support phone and email for operational issues
Configuration - Timezone, program association, and status
Administrative users - Partner admins who can manage the partner's resources

Partner Admins¶

Partner admins are users authorized to perform FeedXChange operations on behalf of their partner.

Partner Admin Features:¶

Role-based permissions - Assigned roles that control access levels (create, read, update, delete)
Partner-scoped access - Can only manage resources for their associated partner
Invitation workflow - Receive time-sensitive email invitations to set up accounts
ReactorCX integration - Roles and permissions are managed through the ReactorCX system

Admin Invitation Process:¶

System administrator creates the partner admin account
FeedXChange sends an automated email invitation
Time-sensitive - Admin must create a password within two hours
If the invitation expires, your program administrator can send a password reset email

Partner Dependencies and Relationships¶

Partners are foundational to FeedXChange operations:

Prerequisites - Must create partners before connections, templates, or integrations
Resource association - All FeedXChange resources are partner-scoped
Access control - Partner boundaries enforce data isolation and security
Operational structure - Partners define the organizational structure of your integration ecosystem

Partner Lifecycle Management¶

Plan - Identify participating organizations and access requirements
Create - Set up partner records with appropriate details and settings
Configure - Add partner admin users and assign appropriate roles
Operate - Partners create and manage their connections, templates, and integrations
Maintain - Update partner information and manage admin users as needed