Teams and Channels Structure Plan for an Organisation
Design teams, channels and ownership that stay manageable.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Design a Microsoft Teams structure for [ORGANISATION_DESCRIPTION]. Departments and projects: [DEPARTMENTS_AND_PROJECTS]. Current teams and problems (duplicates, unclear owners, too many channels): [CURRENT_TEAMS]. External people who need access: [EXTERNAL_PEOPLE]. Who administers Teams: [ADMINS]. Inactive months before archive: [INACTIVE_MONTHS]. Recommend what should be teams, what channels inside a team, and what private or shared channels [VERIFY the channel types in our tenant]. Provide a naming convention, an ownership rule (at least two owners per team), a lifecycle rule (review, archive after the inactive limit), a standard channel set for a project team (General plus up to four), and a guest access rule. The structure should make sense to a newcomer. Return a table with Team, Purpose (a two-sentence description), Owners, Channels and Access, with counts before and after. Migration plan that merges duplicates without losing files or chat history: say what to do with chats that should have been channels and warn about moving files, since files live in SharePoint behind each team [VERIFY]. List the decisions for the administrator.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.