Message types and policies
Every kind of message this platform sends, and the policy governing each.
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
Each message type — what triggers it, whether a customer may switch it off, which consent it requires, and how it is throttled — as a published policy rather than a property of whatever code sends it.
What has to exist first
- Reads
- staffCommMessageTypesList
- Actions
- staffCommMessageTypeSave
- staffCommMessageTypeValidate
- staffCommMessageTypePublish
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.