We are testing the use of the new Integration License for API use. .
We have been using the Admin license for our portal, which automatically gets assigned permissions to any new classes that are created, but are switching to the new license as it frees up a paid license.
With the switch to the new free integration user profile, however, any new classes are NOT assigned permissions automatically. This is causing issues as developers are forgetting to do the class permission assignment for the api user.
Is there any way to set this on the class when it is created, rather than having to remember to go to either the profile and add it there, or to the class in the list of classes under Custom Code and click on the Security link? Or to set this profile as being updated with permissions as admin (in our case it requires access to all classes)?
I don't want to have to go into the orgs after deploying new classes and set this manually on the profile each time. I know I can create a permission set for the profile, but again, it has to be maintained manually, so there's still the problem of a dev forgetting to do so.