General

1. Whose platform API keys are going to be used in the enterprise data platform?

The developer, which is you in this case, will need to register with the work platform and obtain their own API keys to be used with the Enterprise Data Platform.

2. Who handles API usage quota and related restrictions/conversations with the work platform?

The developer, which is you in this case, will need to develop a relationship of their own and manage the API usage & quotas with the work platform directly.

3. Do I have to use the Phyllo Connect SDK to onboard users?

No, you can use your own connection flows or SDKs. But we highly recommend to use the Phyllo Connect SDK since we have perfected the login flow over hundreds of thousands of connections. In case you decide to use your own login flow, you will separately have to share the user access tokens with Phyllo.

4. Who does the user connect with - Phyllo or me? Whose name appears on the platform login screen while granting permissions?

The user connects with you, since the platform API keys are yours. Your name appears on the login access and permissions screen.

5. Can I request the user for more permissions?

Yes, if you have been approved by the work platform to ask for more permissions, you can ask the user for those permissions during the login flow. Depending on whether the user grants these permissions, you can then use the access token to fetch this additional data.

6. Do I get access to the user access tokens?

Yes, since the platform API keys are yours, you get full access to all data including the user access tokens. They are your IP and Phyllo is merely holding them as a custodian of the data and service manager for the infrastructure used to connect with the work platform.

7. Does Phyllo store the data?

Yes, in order to make the Enterprise Data Platform perform its intended functionality, Phyllo needs to store the data on their servers.