I agree but I would say if there are variable token costs depending on report it would be nice if client sent request to server, server calculates x tokens to be used, sends x to client, client confirms that's acceptable, server does work.
Like if I expected a report to be 2 tokens but because of some quirk or a typo or something it cost 200 tokens I would like a chance to cancel it if it's not worth it.
I had a job as a software engineer at corporate job but got let go. Mostly I enjoy backend. I can do front end programming but am very bad at making pretty things. Like sketch something out for what you want for a interface I can program it, but ask me "just make an gui for users" and it will be like win-me quality of bad.
Oh, ok I interpreted multitenant wrong. I was thinking it was like a apartment complex so you have like a manager and a sales person with access and that's it. Still a valid security risk but not as severe as what you are saying now.
Yeah but simply using entity framework would of made the configuration file a list of systems.