[Twilio Connector] How to use in a multi-tenant environment?

[Twilio Connector] How to use in a multi-tenant environment?

Forge Component
Published on 2017-12-06 by OutSystems R&D
13 votes
Published on 2017-12-06 by OutSystems R&D
How can we use this in a multi tenant environment with different numbers for each tenant?
Hey, Preston,

Sorry for the late reply. I'm not the biggest multi-tenant expert, but I think we can configure the connector's site properties for each tenant individually. More specifically, we could configure the same AcountSID for every tenant, but a different "default from". But this looks, personally, somewhat hackish: not sure if tenants can't access the property values and manipulate them.

What I'd do (again not being the biggest multi-tenant expert) is create a tenant-by-tenant backoffice where I'd associate each desired number to each tenant Id and then modify the connector to fetch it, along with the AccountSID, during the "OnBeforeRequest" action.

Does this make sense? If so, does it fit your use case?

Best regards,

Carlos Simões