Independent Handbook
About TeamPractice
We are two practitioners who spent years answering the same questions in onboarding sessions, and eventually wrote the reference we kept wishing existed.
24
Chapters
6
Chapter groups
2
Authors
2025
First published
Why This Handbook Exists
Team collaboration software is usually introduced to employees in a forty-five minute launch webinar and never again. The questions do not stop at minute forty-six: where should this file live, who can see that channel, why did my notification never arrive, what happens to the project space when the project ends?
Vendor documentation answers feature questions precisely and workflow questions rarely. TeamPractice inverts that: every chapter starts from a situation a person actually encounters — a messy channel list, a client call gone wrong, an audit request — and works toward the settings and habits that resolve it.
Independence
TeamPractice has no commercial relationship with any software vendor. We accept no sponsored chapters, no affiliate arrangements and no paid placements. Where a chapter describes a configuration choice, the reasoning is ours and the trade-offs are stated, including the ones vendors prefer left unsaid.
Product and platform names that appear in these chapters are used descriptively to identify the software being discussed; all such names remain the property of their respective owners. Nothing here implies endorsement by, or affiliation with, anyone.
Independence notice: TeamPractice is a self-directed educational publication. We are not affiliated with, endorsed by, or sponsored by any software vendor, and we are not a support channel for any product.
The Authors
Elena Marsh
Workplace Collaboration ConsultantElena has run onboarding and rollout programmes for several thousand employees across mid-size companies. She writes the everyday-usage chapters: interface, chats, channels, meetings, files and the human side of adoption.
Owen Brackett
IT Security & Compliance AnalystOwen covers the control side: admin consoles, policies, external access, retention and the privacy questions employees ask but rarely get straight answers to. He writes the administration and security chapters.
Editorial Principles
Situations before features
Chapters open with a problem a reader recognises, not with a menu tour. Settings appear when the situation demands them.
Trade-offs stated plainly
Every control has a cost in usability or maintenance. We name it, because unmentioned costs are how bad configurations survive.
No vendor vocabulary where plain words work
We write "the file library", "the lobby", "the admin console" — terms that transfer between products and stay understandable when interfaces change.
Reviewed when platforms change
Each chapter carries a review date. When a major platform update invalidates a step, the chapter is revised and the date moves.
What the Handbook Covers
- Everyday Basics — interface orientation, chats, channel structure, notifications and focus
- Meetings & Calls — scheduling, meeting options, calling, presenting and co-editing live
- Files & Sharing — channel libraries, co-editing, link permissions, search and pinned tools
- Admin & Policies — the admin console, group policy assignment, creation rules and lifecycle
- Security & Privacy — pre-launch checklists, external collaboration, retention and employee privacy
- Rollout & Habits — change management, adoption metrics, etiquette and troubleshooting
Corrections and Contact
If a chapter is wrong, outdated or unclear, tell us — corrections are published with credit where the reader wants it. Reach the editors at hello@teamspractice.it.com, by phone on (816) 683-1333, or through the contact form.
Our editorial office is at 7077 Elmwood Ave, Kansas City, MO 64132, USA.