Asset Hierarchy and Access Rules
CX Fabric organizes assets in a structured hierarchy, where integrations, flows, connectors, and credentials are interconnected. Understanding these relationships helps in managing assets effectively and ensuring proper access control when sharing.
How Assets Relate to Each Other
Integration → Flows → Connectors → Credentials
Integrations act as containers for Flows that define automated processes.
Flows use Connectors to interact with external services and systems.
Connectors require Credentials to authenticate and establish secure connections.
This hierarchical structure ensures that when a flow runs, it can use the necessary connectors and credentials, maintaining seamless automation.
How Sharing Impacts Accessibility
Sharing assets impacts which users can view and use related assets. Below are the access rules based on sharing settings:
Flow Access Rules
When an Integration is shared, all Flows within it become accessible to the recipient.
These shared Flows appear in the Flows List Page with a "Shared" status.
A user with access to a shared Flow can view and edit it based on their assigned permissions.
Connector Access Rules
If a Flow is shared, users can see the Connectors used within the shared Flow in the Flow Designer’s Connector Library.
Users can access:
Connectors already in the shared Flow
Connectors explicitly shared with them
Connectors they own
However, Connectors in a shared Flow do not automatically appear in the Connectors page unless explicitly shared as a separate asset.
Credential Access Rules
If a Flow is shared, the credentials associated with it are pre-set in the Flow Designer. The Flow owner selects a default credential to be used when sharing the Flow.
Users with access to the shared Flow can:
Use the pre-selected credential
Access their own credentials
Access credentials explicitly shared with them
Credentials do not appear in the Credentials page unless explicitly shared as a separate asset.
Key Takeaways
Sharing an integration grants access to all flows within it.
Sharing a flow does not automatically share its connectors and credentials.
Connectors and credentials must be shared separately to be visible in their respective management pages.
Pre-configured credentials remain in the flow for execution but are not accessible unless explicitly shared.
Last updated