Part of epic #1017, dependent on #1780
AS a maintainer (and/or possibly stakeholder),
I WANT there to be a place on platform (either under the hood or on the frontend) to add a Twilio API key,
SO THAT the application will be able to trigger Twilio SMS notifications.
How it works now
It doesn't! Twilio is new territory for Ruby For Good applications, including this project.
How it should work
There are a couple ways this could work, depending on the outcome of #1780. It looks likely that there will need to be a place on platform (on the frontend) for stakeholders or maintainers to enter a tenant specific Twilio API key.
This could either go:
- in prod under "Edit Organization Details", only accessible by admins
- in prod All CASA Admin editable per organization, only accessible by maintainers
This could alternatively be hard coded into the backend (especially if the app will be relying on one API key vs numerous), but probably easier to maintain if we create a place for it on the frontend.
Part of epic #1017, dependent on #1780
AS a maintainer (and/or possibly stakeholder),
I WANT there to be a place on platform (either under the hood or on the frontend) to add a Twilio API key,
SO THAT the application will be able to trigger Twilio SMS notifications.
How it works now
It doesn't! Twilio is new territory for Ruby For Good applications, including this project.
How it should work
There are a couple ways this could work, depending on the outcome of #1780. It looks likely that there will need to be a place on platform (on the frontend) for stakeholders or maintainers to enter a tenant specific Twilio API key.
This could either go:
This could alternatively be hard coded into the backend (especially if the app will be relying on one API key vs numerous), but probably easier to maintain if we create a place for it on the frontend.