A senior operations manager leaves. Their scheduled reports still run, their agent instructions still name them as the approver, and a dozen useful pages have no active owner. The company kept the files and lost the people and decisions that made them safe to use.

In an Atlassian discussion about page ownership, customers raise the difficulty of transferring many pages when an employee leaves. Agents add a layer: retained instructions keep acting on an outdated ownership model long after a document's byline changes.

Inventory the work, not the employee's whole history#

Begin with the business processes the person owns: recurring tasks, approved methods, customer exceptions, maintained reference material, and pending decisions, plus the agent workflows that depend on them.

Separate knowledge transfer from access removal. The company can keep an approved procedure while immediately removing the former employee's credentials and approval authority. Keeping knowledge needs no personal connection token and no agent impersonating the departed person.

Take a monthly customer adoption report. Its useful assets are the metric definitions, account exclusions, report template, and interpretation notes. The manager's personal mailbox connection and informal list of people to chase need different treatment: a successor approves the new delivery list and owns the connection for future reports.

Review what the next agent will rely on#

Item	Transfer decision	Successor's check
Maintained procedure	Assign a new business owner	Can a colleague perform it?
Customer exception	Reconfirm scope and validity	Does current agreement support it?
Scheduled delivery	Reapprove owner and recipients	Is it still wanted?
Personal draft or opinion	Keep only as history	Should future work rely on it?
Credential or approval role	Revoke or reassign through normal controls	Does the old authority stop working?

Ask the successor to review the decisions behind the procedure as well as its wording. A note such as "exclude these accounts" needs a reason and a current list.

Keep attribution where it explains the history, so reassigning responsibility does not imply the successor wrote the original guidance. The new owner approves a revised version and keeps the previous one as historical evidence.

Test a real task under the new owner#

Run a representative task with the successor's authorized access and check that the agent retrieves the right sources, asks the right approver, produces the expected artifact, and delivers only to intended recipients.

Also try a case the old instructions handled badly. If the departing manager repeatedly corrected one account classification, turn the reviewed correction into a specific test.

When a task fails, repair the authoritative dependency: move approved shared material to its maintained location, update the designated approver, or replace a personal connection with a team-owned one. Never copy a departing person's credentials into another agent to keep the schedule running.

Retire work that no longer earns its place#

Offboarding often reveals recurring outputs nobody reads. If no recipient owns the decision the report supports, retire the scheduled delivery through the normal process and keep any required historical outputs. Preserving every routine turns a staff change into years of needless agent activity.

For ambiguous knowledge, mark it as needing review and give it an owner. Keep uncertain notes out of general instructions because the original author is unavailable. The agent can still cite historical context while stating it is not an approved current method.

The success condition is that the successor can complete the important jobs and explain the retained rules, while the old authority is removed. Count unresolved dependencies and failed handoffs.

Deixic keeps reviewed company knowledge and reusable skills in the company layer, so a procedure stays when a person or the agent changes. Review connected tool access as ownership changes. The company should inherit the useful procedure, the reason it works, and a way to revise it, and it should not inherit a former employee's authority.