Overview
Your iPaaS.com interface depends on which experiences you can access. Different company types see different views, and some users can switch between experiences to view the platform from multiple perspectives.
The access model works as follows:
A User is assigned a Role.
A Role contains the Permissions available and active for that Role.
An Experience is defined at the company level as a set of Permissions for a specific Role. An experience can only be added to a company by an iPaaS.com admin.
NOTE: An experience is NOT a role, but a set of permissions assigned to the role. |
Experience Types
Subscriber Experience
Default view for standard subscribers.
View that Managed Integration Service Providers (MiSPs) see when managing client accounts.
MiSP Experience
Dedicated view for Managed Integration Service Providers.
Includes the ability to switch to Subscriber view when assisting clients.
Integrator Experience
Specialized view for developers creating subscriptions.
Can switch to Subscriber view for testing purposes.
Access Management Components
Users
Users are individuals with login credentials to access iPaaS.com. Key characteristics:
Must be assigned a role to perform any actions on the platform.
Cannot be restored once deleted.
Recreating a user with the same email provides fresh access without previous settings.
Roles
Roles are collections of permissions that enable specific platform actions. Key characteristics:
Organized by platform section for easier management.
Include varying access levels: view, create, edit, delete, or administer.
Cannot be restored once deleted.
Understanding the distinction between users and roles is essential for effective access management on iPaaS.com.