Make organizations easier to change

[Lermatroid]

No description provided.

[Lermatroid]

Currently orgs are hard coded. Should be changed to some kind of config file or other solution.

[Xevion]

So, what are our actual interests in doing this? Currently, they're all statically typed and available to Typescript values, which makes them annoying - but gives them resiliency.

If we change to a configuration file

• We give the ability to create and modify attributes about an organization slightly faster
• We have to rewrite a lot of things to make this happen
• But only software engineers can do this. We assume at this moment in time, long term, people won't be editing our code or doing much to it.

So is a configuration file the right choice? What about a database? What's the difference in loading from JSON files and connecting to Prisma?

With a database

• It's still dynamic, same as a file.
• Stronger typing through Prisma, although it's still pretty much the same.
• Allows us to build interfaces long-term for people to edit, configure, and change organizations.