iPaaS.com Roles and Permissions
As an Integrator, you have access to specific features within the platform. You can also switch between Subscriber and MiSP roles to access additional functionality as needed.
Feature Access by Role
Feature | MiSP | Subscriber | Integrator |
User/Role Management | • | • | • |
Data Management |
| • |
|
Integration Management |
|
| • |
Branding and Content | • |
|
|
Resources | • |
|
|
Knowledgebase | • |
|
|
Training | • | • | • |
Register a Deal | • |
|
|
Subscription Management | • | • |
|
Integration Monitoring and Diagnostics | • | • |
|
Settings | • | • |
|
Integrator Experience
The Integrator experience is configured at the company level and provides specialized permissions for developers who create and deploy subscriptions. This role-based experience includes specific tools and features designed for integration development. You can switch to a Subscriber view to test your implementations.
Core Concepts
Data Accountability
iPaaS.com serves as the central source for all API calls made to integrated systems, giving users complete visibility into data flows across their entire ecosystem.
Hub and Spoke Model
iPaaS.com operates using a hub-and-spoke architecture. New data is pulled into a standardized data model, stored in the iPaaS.com database, and then distributed to connected systems that are configured to receive updates.
Data Direction
Data transfer direction in iPaaS.com is defined as:
Data TO iPaaS.com: Information flowing from external sources into the platform.
Data FROM iPaaS.com: Information flowing from the platform to external sources.
Queue-Based Data Transfer
iPaaS.com uses a queue-based system that holds data awaiting updates and processes events using first-in, first-out (FIFO) methodology. This approach prevents system overload and ensures stable performance for both iPaaS.com and connected systems.
Webhooks
iPaaS.com is built around webhook functionality. The platform uses external systems' APIs to enable or disable webhooks. When webhooks trigger, iPaaS.com captures the ID and method from the webhook payload to queue the appropriate CRUD (Create, Read, Update, Delete) operation.
Polling
iPaaS.com can poll external systems on scheduled intervals to retrieve new or updated data. When a record is updated through polling, any connected system configured to listen for changes to that data type will have the updates queued in their outbound queue.
Template Mapping
Template mapping allows you to define how data fields in iPaaS.com correspond to specific fields in external systems. These mappings are organized into Mapping Collections, which are grouped by:
Data type
Data direction (inbound/outbound)
Target system
Integration Presets
Integration Presets are configurable field sets that can be reused across integrations. They are commonly used for:
Authentication credentials and settings
Variable definitions for API calls
Standardized configuration parameters