SharePoint Setup and Configuration for Teams and Organizations
A step-by-step guide to configuring SharePoint Online — site creation, document libraries, permissions, workflow automation, and integration with Microsoft Teams.
What is SharePoint Online?
SharePoint Online is Microsoft's cloud-based platform for document management, collaboration, and intranet portals. It's tightly integrated with Microsoft 365, Teams, and OneDrive.
Key Concepts
| Concept | Description | |---------|-------------| | Site | A collection of pages, libraries, and lists | | Team Site | Collaboration site linked to a Microsoft 365 Group | | Communication Site | Publishing site for news and announcements | | Document Library | Storage for files with versioning and metadata | | List | Structured data (like a spreadsheet or database table) | | Hub Site | Groups related sites under a common navigation and search |
Site Architecture
Planning Your Site Structure
SharePoint Hub: Company Intranet
├── Communication Site: Company News & Announcements
├── Team Site: Engineering
│ ├── Document Library: Technical Docs
│ ├── Document Library: Project Files
│ └── List: Equipment Inventory
├── Team Site: Operations
│ ├── Document Library: SOPs
│ ├── Document Library: Maintenance Records
│ └── List: Asset Register
├── Team Site: HR
│ └── Document Library: Policies
└── Communication Site: Training Portal
└── Document Library: Training Materials
Creating a Team Site
SharePoint Admin Center → Sites → Create → Team Site
Configure:
- Site name: "Engineering"
- Group email: engineering@company.com
- Privacy: Private (members only)
- Language: English
- Time zone: Your timezone
- Site template: Team collaboration
Creating a Communication Site
SharePoint Admin Center → Sites → Create → Communication Site
Templates:
- Topic: General-purpose with sections
- Showcase: Visual layout for products/projects
- Blank: Start from scratch
Document Libraries
Setting Up a Document Library
Site → New → Document Library
Configure:
- Name: "Technical Documentation"
- Description: "Engineering technical documents and specifications"
- Versioning: Major and minor versions
Adding Metadata Columns
Metadata makes documents searchable and filterable:
Library Settings → Columns → Add Column
Useful columns:
- Department (Choice: Engineering, Operations, IT)
- Document Type (Choice: Specification, Manual, Report, Drawing)
- Status (Choice: Draft, Review, Approved, Archived)
- Project (Lookup: linked to Projects list)
- Expiry Date (Date)
- Confidentiality (Choice: Public, Internal, Confidential)
Document Templates
Set default templates for consistent document creation:
Library Settings → Advanced Settings → Template URL
Upload templates:
- Report_Template.docx
- Specification_Template.docx
- Meeting_Minutes_Template.docx
Versioning
Library Settings → Versioning Settings
Recommended:
- Create major versions: Yes
- Create minor versions: Yes (for draft workflow)
- Keep number of major versions: 50
- Require check-out: Yes (for critical documents)
Permissions and Access
Permission Levels
| Level | Capabilities | |-------|-------------| | Full Control | Everything (site owners) | | Design | Create lists, edit pages | | Edit | Add, edit, delete items and documents | | Contribute | Add and edit items (not delete) | | Read | View only |
Setting Permissions
Site Settings → Site Permissions
Best practices:
1. Use Microsoft 365 Groups for team sites (automatic)
2. Break inheritance only when necessary
3. Use SharePoint Groups (not individual user permissions)
4. Create custom permission levels for specific needs
Library-Level Permissions
Library → Settings → Permissions for this document library
Example: HR Policies library
- HR Team: Edit (can add and modify)
- All Employees: Read (view only)
- Contractors: No access
External Sharing
SharePoint Admin → Sharing
Levels:
1. Anyone: Public links (not recommended)
2. New and existing guests: External users with authentication
3. Existing guests only: Previously invited
4. Only people in your organization: No external sharing
Recommended: "New and existing guests" with approval workflow
Microsoft Teams Integration
Every Microsoft Teams team automatically gets a SharePoint site:
Teams Channel → Files tab = SharePoint Document Library
Team: Engineering
├── General Channel → /Shared Documents/General/
├── Project Alpha → /Shared Documents/Project Alpha/
└── Research → /Shared Documents/Research/
Sync Libraries to Desktop
SharePoint Library → Sync button → Opens OneDrive sync client
Files appear in File Explorer:
C:\Users\{user}\{company}\{library-name}\
Add SharePoint to Teams Tab
Teams Channel → + (Add Tab) → SharePoint
- Add a SharePoint page as a tab
- Add a document library as a tab
- Add a list as a tab
Lists (Structured Data)
SharePoint Lists are like lightweight databases:
Creating a List
Site → New → List
Templates:
- Issue tracker
- Asset manager
- Content scheduler
- Custom (blank)
Example: Equipment Inventory List
Columns:
- Equipment Name (Single line text)
- Serial Number (Single line text)
- Category (Choice: Network, Server, IoT, Safety)
- Location (Choice: Site A, Site B, Warehouse)
- Status (Choice: Active, Maintenance, Decommissioned)
- Purchase Date (Date)
- Warranty Expiry (Date)
- Assigned To (Person)
- Notes (Multi-line text)
Views:
- All Equipment (default)
- Active Equipment (filter: Status = Active)
- Expiring Warranty (filter: Warranty Expiry < 30 days from now)
- By Location (grouped by Location column)
Power Automate Workflows
Automate common tasks with Power Automate (formerly Microsoft Flow):
Example: Document Approval Workflow
Trigger: When a file is created in "Specifications" library
Actions:
1. Set Status column to "Pending Review"
2. Send approval request to Manager
3. If approved:
- Set Status to "Approved"
- Move to "Approved Specs" folder
- Send notification to author
4. If rejected:
- Set Status to "Rejected"
- Add comment with rejection reason
- Send notification to author
Example: Expiry Notification
Trigger: Scheduled (daily at 8 AM)
Actions:
1. Get items from Equipment list where Warranty Expiry < 30 days
2. For each item:
- Send email to Assigned To person
- Post message in Teams channel
Search Configuration
Managed Properties
Map crawled properties to managed properties for better search:
SharePoint Admin → More features → Search → Manage search schema
Create mappings:
- DocumentType → RefinableString00
- Department → RefinableString01
- ProjectName → RefinableString02
These become refiners (filters) in search results.
Search Best Practices
- Use metadata consistently — Well-tagged documents are findable
- Create site columns — Reuse the same columns across libraries
- Content types — Define document types with required metadata
- Hub sites — Enable cross-site search within a hub
Administration Best Practices
- Plan before building — Define site architecture, naming conventions, and governance
- Use hub sites — Group related sites for shared navigation and search
- Content types over folders — Metadata-driven organization scales better than deep folder structures
- Train users — SharePoint adoption requires user training
- Set storage quotas — Prevent sites from consuming excessive storage
- Regular cleanup — Archive old sites and delete unused content
- Backup strategy — While Microsoft handles infrastructure, consider third-party backup for data retention
- Monitor usage — Use admin reports to identify inactive sites and storage trends
Conclusion
SharePoint Online is a powerful platform for document management and collaboration when properly configured. Focus on good information architecture (site structure, metadata, permissions) from the start, integrate with Teams for seamless collaboration, and automate workflows with Power Automate. A well-organized SharePoint environment becomes the single source of truth for your organization's documents and data.
Related: Microsoft 365 Admin Center Guide and Network Monitoring Best Practices.