Delegation and Impersonation
Neither of these is in 0.2.0. This page exists because both get asked for in every workshop, and because there is an exercise nearby that superficially looks like one of them.
Formal Delegation — “Alex may approve on Sam’s behalf until Friday” — is
preview-only.
Building it means answering questions that aren’t answered yet: what authority transfers and what doesn’t, when it expires and what happens to work in flight, what the audit record shows, and which command checks change. None of that is designed.
The important part: the Day 1 coverage exercise is not Delegation. There, the group’s membership changes and the engine re-reads who is currently in it. Nobody acts on anyone’s behalf, and nobody gains authority they didn’t have. Calling it Delegation in a room full of customers creates an expectation that 0.2.0 will not meet.
Impersonation is preview-only.
It is not a login shortcut, not a support tool, and not a way around authorization. There is no step in the tutorial that does it, and no page may present it as available.
Both stay here until the implementation, the tests, and the release status move together. A page that describes a capability is not a capability.
For what actually decides who may act today, see Authorization.