I have…
- Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
I’m submitting a…
- Subscription Question
Question
Suppose I have my own custom administration system for users of my own self-hosted application (not Squidex, but a custom app I want to connect with Squidex), and I wanted to open up a limited subset of Squidex schemas for them to edit, but from within my application. One way to do that would be to create a few text boxes on my admin website and have the back-end use Client credentials via the Squidex API to manipulate content.
In that case, the edits are attributed to the API Client, not to a contributor user account, and in this case, the users of my external system don’t need to be in the Squidex User management system.
My question is whether this is fair usage on the Squidex Cloud plan. The subscriptions have different tiers of “Number of Contributors”. In this scenario, does an external user purely interacting through a back-end proxy using Squidex Client Credentials, count as a Contributor?
I couldn’t find any documentation indicating whether that is the intended use or not, and we certainly want to make sure we’re in line with number of Contributor restrictions on the Cloud plan. Thanks!
Environment
App Name:
- Cloud version
Version: [VERSION]
- Cloud version