In a Redox organization, an asset is any key component used to build your integration, such as a destination, data operation, or an API key. Think of assets like the building blocks you put together to build your integration. These essential pieces work together to send, process, or receive data.
Assets are exclusive to one organization and one environment. Organizations on both sides of the integration have unique assets based on their individual data needs.
Assets allow you to have granular control over your data, security, and workflow.
By treating components of your integration as different types of assets, you can:
- Assign specific permissions: Grant view-only access to some users, while allowing other users to create and manage assets directly.
- Improve security: Limit a user’s role to the types of assets they need to do their job, following the principle of least privilege.
- Organize your integrations: Clearly see all the components of your integration within a specific environment.
A user’s role determines their ability to create or access assets. Learn about roles.
Asset | Description |
|---|---|
Source | A proxy for pushing your outbound data to Redox. |
API key | An authentication mechanism you use to authenticate your source(s) to send data to Redox. Learn about authenticating Redox APIs. |
Destination | An endpoint configured to receive your inbound data from Redox. |
Auth credential | An authentication mechanism you use to authenticate and verify inbound data from Redox. Learn about authenticating incoming data. |
Connection | A business entity that you’re integrating with. Learn about connections. |
Data operations | Any custom settings used for processing data you exchange with your connection. This includes filters, translation sets, or config modifiers. Learn about operation types. |