Team Site Information Architecture With Libraries, Metadata and Views
Plan a SharePoint site that people can navigate and search.
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.
Plan a SharePoint team site. The team and content types (policies, templates, project files, forms): [TEAM_AND_CONTENT]. Who needs to edit and who only reads: [PERMISSION_NEEDS]. Search terms people use: [SEARCH_TERMS]. Retention or approval needs: [APPROVAL_NEEDS]. Propose the home page content (five links at most), the libraries, folders only where needed, and metadata columns (document type, owner, review date, status) with choices defined. Define views (by type, due for review, recent) and a naming convention. Suggest permission groups (owners, members, visitors) with a principle of inheriting permissions and avoiding unique permissions on folders. Provide an upload checklist, a quarterly content review process with the owner and review date metadata, and a migration plan from a shared drive in four steps. Include examples of a metadata set for two document types. Features such as managed metadata, flows and approval depend on plan and tenant settings; mark them [VERIFY]. Add a worked metadata set for 'Policies': Document type (policy, procedure, guide), Owner, Review date, Status (draft, approved, retired); and a view called 'Due for review' filtered to review dates within 60 days. Add a naming convention example such as 'HR-Leave-Policy-v2'.
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 Claude, Gemini, ChatGPT or another assistant.