Working in a solutions architecture role sometimes means you will have teams come to you and say, "we don't want to give you that permission in a system for that particular integration." Cool! But just accept it won't work. But then they don't love that.

I can offer workarounds with usually more friction, but the integration is the integration.

It always surprises people.

"What do you mean you can't read the table of data I refuse to give you read access to?"

The best is when people will say, "well, it works when I do it from this api over here." And then you have to gently point out that the api doesn't actually have the data they think it does, or isn't supported for partner integration, or a dozen other little things that are always annoying.

I'm really sympathetic here, honestly. It's annoying when you get stuck in binds of wanting to lock things down and also provide useful access, but sometimes those things are mutually exclusive.