Allow OAuth clients to request additional permission scopes
When external applications request Front API access through OAuth2, they are limited to the "shared resources" scope, which grants access to API resources belonging to shared workspaces. This idea suggests expanding the available scopes that a user could grant to an OAuth client, including a scope for accessing otherwise private individual teammate resources.
Would be nice to get knowledge base access using OAuth2.
We are currently instructing our users to setup their Front API key and credentials with private resource permissions and then completing the OAuth process in our system. It's confusing to them that the OAuth permissions window does not reflect the actual permissions they'll be granting our system. We'd love for the OAuth permissions workflow to grant additional scopes OR to reflect the additional permissions being granted by their API key.
OAuth clients are also limited from accessing knowledge base resources at the moment. It would be nice to add that as a scope as well.