CloudDeploy Permissions: Per‑Parameter Access Control Unresolved

CloudDeploy Permissions: Per‑Parameter Access Control Unresolved

The goal is to publish an APIFunction as a CloudObject and enforce that only specific Wolfram IDs can supply certain parameters while others remain unrestricted.

Current documentation shows that the Permissions option on CloudObject applies to the entire object, not to individual parameters. This raises uncertainty about whether fine‑grained access can be achieved without wrapping logic inside the function body.

Key constraints: the Permissions option accepts strings like "Public" or rule lists; there is no documented syntax for parameter‑level rules. The default is private to the deploying account, but does not differentiate between callers for distinct arguments.

Specific questions:

• Can Permissions be specified per APIFunction parameter?
• What syntax would allow restricting a particular parameter to a set of Wolfram IDs while leaving the rest open?
• Does the Wolfram Cloud provide a mechanism to enforce such parameter‑level access control natively?