Who grants access, and where do the records come from?
Your app enables the integrations it offers. A customer authorizes an account and your app uses that connection to access the provider. Unified.to describes on-demand reads. Check which operations a connector supports, what your app stores and what it shows when the source is unavailable.
Do connections and requests count the same way?
A customer can link several accounts, which creates several connections. Unified.to lists API volume pricing and separate negotiated options. Confirm the unit for your plan. Estimate the number of requests your app makes for each user action and any background checks.
What happens if a fictional recruiting account disconnects?
Draw a customer who connects a recruiting tool and then withdraws access.
- Map the allowed readMark the one fictional record your app expects and where it comes from.
- Draw the failure stateRemove the connection and write what the screen should show without using another customer’s account.