Team and Channel Structure for a Department With Guest Access Rules
Design Teams and channels, including guest rules, for a small department.
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 [DEPARTMENT]. People and roles: [PEOPLE_AND_ROLES]. Work types (projects, operations, clients): [WORK_TYPES]. External collaborators: [EXTERNAL_COLLABORATORS]. Sensitive content: [SENSITIVE_CONTENT]. Propose whether to use one team or several, standard channels, private and shared channel use, naming conventions, tabs to pin, file locations, owners per team (at least two), and guest access rules (who can invite, which channels, expiry review). Provide an onboarding message for new members and a one-page 'where does this go?' guide. Include a quarterly review checklist for membership and files, and a plan for archiving projects. Teams settings and features differ by licence and tenant policy; mark them [VERIFY] and note that an administrator may control some choices. Add a worked example for an invented 15-person finance department: one team named 'Finance', standard channels General, Month-End, Audit Requests and Vendors, a private channel for payroll, guest access only in Audit Requests with a 90-day expiry review, and two owners named. Add a short note on what to do when someone leaves.
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.