Approvals from Teams and Slack, and electronic signature
Committee requests where the approvers already talk — and decisions signed so that nobody can later deny or alter them.
Microsoft Teams and Slack
In Administration › Change governance › Teams and Slack, paste the channel's incoming webhook (Slack) or Workflows webhook (Teams). When a Deployment reaches a committee gate, the channel receives a card with the change, its project, phase, type and risk, and Authorize, Reject and Defer buttons; decisions are announced too.
- Each button is a one-time link that opens the decision in DevGob; the approver signs in and confirms.
- The chat identity is never trusted: a forwarded card grants nothing to someone without the committee permission.
- The decision is the same as one taken on the Committee tab — same rules, same audit trail — marked as decided via Teams or Slack.
- Links expire after 7 days and stop working once the request is decided; only their fingerprint is stored.
Electronic signature
When the change policy requires it, an approver signs each committee decision: they re-enter their password — and their authenticator code when two-factor is on — and confirm the meaning of the signature. DevGob records the exact decision as a canonical JSON record, its SHA-256 and an Ed25519 signature with the platform key.
- The Committee tab lists every signature, re-verified each time it is shown.
- Signatures travel in the change's consolidated report and evidence package.
- Failed attempts are limited and audited; credentials are never stored.
cd Signatures # in the change's evidence package
base64 -d 01-Authorized.sig.b64 > 01-Authorized.sig
openssl pkeyutl -verify -pubin -inkey ../SigningKey.pem \
-rawin -in 01-Authorized.json -sigfile 01-Authorized.sig