Document a team chat tool by recording who controls the workspace, how roles are assigned, which settings apply, why each important choice was made, and how access or data can be recovered. Cover ownership, membership, guests, retention, exports, applications, channel conventions, notifications, security, billing responsibility, and change approval. Do not place passwords or recovery codes in the guide.
Start with authority and account ownership
Name the primary owner or equivalent, additional administrators, billing contact, identity-system owner, legal or records contact when applicable, and operational backup. Record the organizational email or identity used, recovery route, and the procedure for an owner departure. Link to the current admin page and record when access was last verified.
Slack's workspace ownership guidance states that only the Primary Owner can directly transfer primary ownership and that recovery assistance can depend on whether a workspace belongs to a legal entity. Microsoft documents separate Teams owner and member roles, with different permissions for team and channel management. These examples show why the exact vendor role, not a generic label such as `admin`, belongs in the register.
Record settings and their reasons
Document workspace visibility, membership approval, guest access, channel creation and deletion, private or shared channel rules, application installation, external connections, notification defaults, message editing, file sharing, and naming conventions. For each controlled setting, record the chosen value, business reason, owner, approver, scope, effective date, and exception process.
Use a decision log for changes that affect access, deletion, exports, or external sharing. Include the old value, new value, reason, risk check, test, rollback, and people notified. Screenshots help with context but should not replace text values that can be searched and compared.
Treat retention and export separately
Slack's retention documentation explains that retention settings can automatically delete messages and files, may vary by plan and scope, and can affect what appears in exports. Slack's export documentation lists export capabilities that differ by plan, role, and conversation type. Record both the deletion rule and the tested export coverage; one does not prove the other.
Before changing retention, confirm applicable business, legal, privacy, and contractual requirements with the responsible owner. Export a non-sensitive sample and verify its fields, file links, timestamps, channels, users, and readability. Never state that all messages are preserved unless the current plan, permissions, retention, and test evidence support that conclusion.
Inventory integrations and channel dependencies
List each application, bot, webhook, calendar, storage connector, identity integration, support workflow, and custom automation. Record its purpose, data scope, installer, credential owner, permissions, failure behavior, renewal, and removal test. Store secret locations, not secret values.
Define channel naming, purpose statements, topic ownership, archival criteria, and where decisions must be copied when chat is not the formal record. A useful example is a project channel whose owner, lifecycle, guest policy, and final archive destination are stated at creation.
Verify the documentation
Ask a qualified backup administrator to locate the current owners, add a test member, review a guest restriction, identify the retention rule, run an allowed sample export, find integration owners, and explain the offboarding path. Use test accounts and avoid changing production permissions merely to complete the exercise.
Review the register after an owner departure, plan change, identity migration, retention update, new integration, or security incident. The documentation works when another authorized person can administer the workspace and explain the major decisions without relying on the former owner's memory.
Sources
- Transfer ownership of a workspace or org — Slack Help Center
- Assign team owners and members in Microsoft Teams admin center — Microsoft Learn
- Customize data retention in Slack — Slack Help Center
- Export your workspace data — Slack Help Center