Getting Your PBS Affiliate Station on SharePoint Without Losing Your Mind
SharePoint is not glamorous. It is a document management platform with a permission system complex enough to keep most IT departments employed for months. When you are working across multiple PBS member stations — some small, some large, all with different technology stacks and funding realities — it becomes one of the few tools that can actually hold everything together. The trick is knowing how to set it up before you spend six weeks trying to undo a bad configuration. I spent three years helping a mid-size PBS affiliate reorganize their entire document workflow onto SharePoint. We were dealing with FCC filings, grant proposals, engineering logs, production schedules, and EIT data from multiple sources. Everything was scattered across email attachments, local drives, and an ancient network share nobody could navigate without a map. The migration took about four months, and we learned a lot of things the hard way. The first thing you need to understand is that SharePoint does not care about your organizational structure. It cares about site collections, permissions, and versioning. If you build the site structure around your departments — Engineering, Production, Operations, Management — you will be miserable. People do not work in departments. A producer needs access to engineering documents for call sheet coordination. An operations manager needs to see production budgets. Departmental silos in SharePoint just recreate the problems you are trying to solve.
Instead, build around content types and metadata. Create a site collection with subsites or communication sites organized by function — compliance, engineering, production, underwriting — and then use metadata columns so documents can belong to multiple contexts without being duplicated. A single FCC application document tagged with both "compliance" and "engineering" appears in both workflows. This approach saves roughly 10-15 hours per week on filing and retrieval at stations our size. One thing nobody tells you about SharePoint permissions is that inheritance is both your best friend and your worst enemy. By default, every subsite inherits permissions from its parent. This keeps things simple until someone needs a document visible to only three people in the station. Breaking inheritance at that point cascades into a permission nightmare that takes a full day to clean up properly. The workaround I use now is to create dedicated sub-sites for restricted content from the beginning, even if you think you will never need them. The setup time is maybe ten minutes per site and it prevents months of debugging later. Setting up the foundation: Start by defining your site collection architecture. For a typical PBS affiliate with 20-50 staff, a single site collection with 5-8 subsites works well. For larger clusters or consortia, consider separate site collections per function or station with a hub site to tie them together. Microsoft 365 hubs can connect multiple site collections and provide a unified navigation layer. This matters because search across site collections within a hub is comprehensive, while search within a single site collection is faster and easier to tune.
Document libraries and content types: Do not just create document libraries and dump files in them. That is how you create digital landfills. Create a content type for each document category you handle regularly — FCC forms, engineering reports, production schedules, grant applications, board minutes. Each content type gets its own metadata columns. An FCC filing content type might include fields for filing date, due date, responsible party, and status. A production schedule might include episode number, air date, segment type, and clearance status. This turns SharePoint from a file storage locker into a searchable database. The metadata approach changes how people interact with the system entirely. Instead of drilling through folder hierarchies to find a document, users can filter by any metadata field. A producer looking for all "pending clearance" episodes sees exactly that list regardless of which department created or filed it. This usually cuts document search time from an average of 12 minutes per search to about 45 seconds. Version history and co-authoring: One of the more underappreciated features in SharePoint is the combination of major and minor versioning. Enable both on your document libraries. Major versions (1.0, 2.0, 3.0) are publishable. Minor versions (1.1, 1.2, 1.3) are drafts. This means someone can check out a document, make preliminary edits that create draft versions, and only publish when the content is ready. For production schedules that go through multiple revisions before airing, this is essential. It also means you always have a recovery path if someone corrupts a document — version history retains every save, and you can restore any previous version with one click.
Get the Full Details
Co-authoring works well for most collaborative documents, but there are edge cases where it breaks. Large Excel files with complex macros and external data connections will frequently cause conflicts or lock the file for single-user editing. When this happens, SharePoint displays a watermark on the document and forces check-out mode. The workaround is to move heavy Excel workbooks to a dedicated shared folder with traditional Windows file sharing permissions, or use Power Automate flows to trigger version management instead of relying on manual check-ins. I learned this after spending two days trying to debug why five producers were simultaneously breaking a scheduling spreadsheet. Workflows and automation: Power Automate integration is where SharePoint transitions from a filing cabinet to an operational system. Set up automated flows for common processes. When a new FCC filing is uploaded, the flow can notify the compliance officer, add the document to a tracking list, and set a reminder for the filing deadline. When a production schedule is updated, it can automatically distribute notifications to the engineering team and update the broadcast log. These flows typically take 20-40 minutes to configure each and then run continuously without maintenance. One specific edge case that caught us off guard: SharePoint's Recycle Bin has a two-tier system. The first stage is the end-user recycle bin accessible from any library, which retains deleted items for 93 days. The second stage is the site collection recycle bin, accessible only by administrators, which retains items after they are deleted from the first stage. When we had a situation where someone accidentally deleted an entire folder of engineering reports, I initially thought we were done for because the user had emptied their recycle bin. But the site collection admin restore brought everything back in about 20 minutes. This happened during a FCC audit week, so the timing made it particularly stressful. Now I ensure all station staff know about the two-tier recycle bin system during onboarding.
Social features and team coordination: SharePoint's integration with Microsoft Teams is genuinely useful for public broadcasting operations. You can embed site documents directly in Teams channels, set up @mentions that trigger email and push notifications, and create automated posts when documents are updated. Our station uses a dedicated "Engineering & Operations" Teams channel that pulls live documents from SharePoint. When someone uploads a new transmitter maintenance report, it appears in the channel automatically. The engineering team sees it on their phones within seconds. However, there is a real problem with notification fatigue. When you first turn on automated alerts and mention capabilities, people receive dozens of notifications daily. Within a week, they have configured their inbox to ignore everything from SharePoint. The solution is to be selective about what triggers notifications and to use Power Automate to batch them. Instead of emailing someone every time a document is modified, configure a daily digest that summarizes all changes in a single message. This reduces notification volume by approximately 80 percent and actually gets read. Access management across remote locations: If your station operates remote transmitters or has correspondents who work from home, SharePoint handles this reasonably well through the mobile apps and web interface. The main pain point is large video file handling. SharePoint has a 250 GB per-site upload limit and individual file limits depending on your configuration. For public broadcasting, where you might need to share raw broadcast-quality video files, this becomes a constraint quickly. Most stations I work with use SharePoint for metadata, scripts, and documentation, and pair it with a dedicated file transfer service like Sharefile or Box for large media assets. The two systems complement each other — SharePoint handles the paperwork, the file service handles the footage.
Common pitfalls: The biggest mistake I see smaller PBS affiliates make is over-customizing their SharePoint environment. Building custom pages, creating elaborate information architecture diagrams, and spending weeks on permission structures sounds professional but rarely pays off. A simple site with clean metadata and clear navigation beats a heavily customized one every time. Customization creates fragility — updates from Microsoft can break custom code, and the people who built the customizations are usually gone within a year. Keep it simple and functional. Another issue is the assumption that SharePoint will replace all existing tools. It will not. Your station likely has a station management system, a traffic and scheduling system, a camera logging platform, and a donor management database. SharePoint integrates with some of these through APIs and connectors, but it is not designed to be a replacement for specialized broadcast software. Think of it as the coordination layer between your specialized tools, not a replacement for any of them. Training and adoption: Technology is the easy part. Getting people to use it consistently is the hard part. I recommend a staged rollout rather than a big bang implementation. Start with one document type and one team — engineering safety logs, for example. Get that working smoothly, then expand to production schedules, then to compliance documents. Each successful deployment builds confidence and creates internal advocates who help train their colleagues. A full station rollout typically takes 6-8 weeks of active use before people stop asking basic questions about where to find things.
The platform is accessible through any modern browser and mobile app, which matters for shift workers and on-location producers who are not at their desks most of the day. Offline access through the desktop app is also worth enabling — it allows editing documents while traveling or in areas with unreliable internet, then syncing when connectivity is restored. I recommend configuring this during initial setup rather than leaving it as an afterthought. If you are starting from scratch and need an entry point, Microsoft offers a SharePoint admin center through the Microsoft 365 portal at admin.microsoft.com. From there you can create site collections, configure tenant-level settings, and access the SharePoint admin center for more detailed configuration. There is also a free 25-user trial through the Microsoft 365 Developer Program if you want to test configurations before committing to a production environment.
