Forum Discussion
Restrict Document Library so that only specific folders shared with a user are visible to them
We are migrating from Slack to Teams and need a historical archive of our Slack channel conversations. I have an export of my Slack channels (roughly 4000 public channels and 4000 private channels). ...
Hi MikeRiley, your plan can work, but there are a few things you should adjust so it runs smoother:
- Raw HTML can be messy in SharePoint, PDF are easier to preview, and more reliably indexed by search, so you can consider this by really understanding the need and limitations.
- Don’t keep each channel’s history as one huge HTML file. Break them into smaller parts (like per month or per year), otherwise the files will be too slow to load.
- Don’t dump all 8,000 folders into two big library. Split them into multiple libraries or structure them by year, department, or project. This avoids performance and list view threshold issues.
- Instead of assigning permissions to every folder directly, create user groups first (e.g., by project, team, or channel). Then give access to groups. This makes it easier to manage and avoids messy unique permissions.
- Think about how SharePoint search works. Teams search won’t index this content, so people need to use SharePoint search (or Copilot). Adding metadata (channel name, project, year) and creating filters makes it easier for users to narrow down what they need quickly.
In short: the idea works, but splitting files, grouping permissions, and structuring libraries will save you a lot of headaches and improve performance.