Projects and Assignments - Temporal Cloud
Temporal Cloud project lifecycle, scoped users, groups, service accounts, and project access assignments. Generated from Temporal's byte- and hash-locked official v0.18.0 Cloud Ops OpenAPI (8eccf9183cd7…) at https://saas-api.tmprl.cloud/spec.json. This leaf carries 12 of all 87 official operations at the origin-pinned https://saas-api.tmprl.cloud boundary. Every call uses an encrypted Bearer API key inside the trusted connection adapter and remains subject to Temporal Cloud RBAC. All documented bodies are required bounded verbatim JSON objects; all responses are JSON with lossless unsafe integers. One-time API-key tokens and expiring billing-download URLs are labeled sensitive and excluded from reusable workflows. Documented page-token collections paginate at 100 records per request; a 1000 maximum is applied only where the provider declares it. Reads are uncached, every mutation requires approval, and provider failures receive no hidden retry. No control-plane namespace, identity, or project is misrepresented as a task, note, or user-work project Source.
What this pack installs
- temporal-cloud-projects-assignments Ingredient
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.