Plan Twilio Organization Access in Codex
Document account and subaccount ownership and the smallest access needed before making a Twilio organization change.
中文Setup for Codex (Twilio Developer Kit)
Use Codex in a scratch workspace. The exercise takes local mock data or a written scenario. Check provider prerequisites before running it against a test account.
- In Codex, open /plugins and install Twilio Developer Kit. To reproduce the exact revision, use the pinned Twilio source linked below and its Codex instructions in the repository README.
- Open the practice project, invoke $twilio-organizations-setup and paste the example inputs. Use the installed package with its related skills and references.
Example task
Ask $twilio-organizations-setup to draw a fictional org with one account, separate demo and production subaccounts, and two users. One person only needs demo access. Ask it to flag any proposed access beyond that scope.Expected result
The plan places the person in the demo scope and flags membership granting production visibility. Role naming and availability are listed as checks against the actual console.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Does this sample apply a new organizational policy?
It validates a role and scope plan using fictional data. Apply signed-off changes separately in the appropriate account.