Published role version or existing employee snapshot?

A marketplace update does not silently replace the guide of an already recruited employee. This separation keeps running work from changing underneath a task.

Compare the practical differences

Decision	Published role	Local employee
Best fit	Versioned instructions available through the marketplace	The recruited role and its saved configuration
Useful property	Can receive explicit new versions	Preserves the context used in your office
What to check	Does not rewrite old employee snapshots	May remain on an earlier role version

A concrete choice

After publishing a corrected guide, compare the local employee’s Overview with the new marketplace version before assuming it uses the fix.

Verify the choice

Plan adoption of the new role deliberately and retain useful history and outputs from the existing employee.

Write the reason for your choice into the task brief or setup notes. Then run a small representative task and compare the actual result with the requirement that drove the decision. Keep any unmet requirement visible rather than declaring the whole workflow ready from a single successful step.

Continue with the setup

The related desktop guide explains the relevant controls and limits. Use the current application state when applying this comparison; the presence of an option in a document does not mean every dependency on your computer is ready.