Plan requirement
| Subscription | Any plan |
| Access | Admin |
Compliance coverage is per product, not per account. That distinction is what catches people out.
The thing to understand
Certifications and programmes cover specific products and specific configurations. "Our account is covered" is not a meaningful statement; a given product, used a given way, either falls inside the scope or does not.
Why it matters in practice
A team operating correctly within scope adds a channel, an app or a new product, and that addition sits outside it. Nothing warns them, because from the interface it is an ordinary configuration change.
The account is now partly outside the arrangement, and it will stay that way until somebody checks.
Where to check
Zendesk publishes which products fall under which programme, and the list changes as products develop. Your agreement then states what applies to your account specifically.
Read them in that order: the general position, then your contract.
Marketplace apps are the usual gap
Apps are third-party software processing your data. They are not covered by the platform's own certifications, and installing one is a decision about a new supplier rather than a feature toggle.
Newer features arrive outside scope
A capability may join a programme later than it launches. On a regulated account, "it is available" and "it may be used" are different questions.
Before adding anything
On an account with compliance obligations, check scope before installing an app, enabling a product or connecting an integration. Ask pluscloud support and we will confirm the position for your account.
Comments
0 comments
Article is closed for comments.