Connections and credentials
Which communications provider this deployment sends through, and the state of its credentials.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
The gateway connection per environment, its credential state, and the stage → test → activate → revoke sequence that rotates one — the same shape the AI provider screen already has, for the provider that sends customer email.
What has to exist first
- Reads
- staffCommConnectionsList
- Actions
- staffCommConnectionSave
- staffCommCredentialStage
- staffCommConnectionTest
- staffCommConnectionActivate
- staffCommCredentialRevoke
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.