Aha, now I see what you mean. Sorry for misunderstanding earlier.
For this use case, I would definitely recommend using the Admin API endpoint. I’m sure you can encode the authentication logic into your IDEA plugin. And since you’re trying to build something that lets users test functions, the Admin API endpoint is perfect (since it’s meant for testing functions).
The function privacy setting shouldn’t matter in this case. See the documentation on the function privacy setting – basically, setting a function to “private” stops users from calling your function directly using the Realm SDK. This is useful for situations where you want to write logic for some privileged functionality (like updating a user’s custom data, or administrating something) but you don’t want to expose that functionality to all users through a typical function call.
The privacy setting doesn’t impact running a function through the Admin API. The Admin API is an administrative feature by nature – you can use it to add, update, and remove logic, functions, rules, etc. in the backend. If you think about it, you could use the Admin API to set any function to “private: false” and then run it anyway… so it doesn’t even make sense for the privacy setting to apply there. So that should work well for your use case. Let me know if you hit any other snags! This sounds like a really cool project and is something I’ve actually wished for myself in the past when developing projects with Realm.