This is a small thing, but, in the interest of clarity, I'd love to see a list of the permissions required for a specific asset, lead database or authentication controller included in Marketo's developer documentation. This would take any guess work out of the equation when configuring or updating an API user and allow developers to adhere to the best practices suggested in the role permissions section:
When constructing a role, think carefully about what actions you should permit the application using it to do. Award only the minimal set of permissions required to carry out those actions. Allowing an unnecessarily permissive set of permissions can allow integrations to perform unwanted actions in your subscription.
There is already a list of role permissions that includes an explanation for each permission, but I think including it in the documentation for each asset, lead database or authentication controller would be useful and remove any ambiguity.
The developer documentation is so fulsome and, from my perspective, is really just missing this one thing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.