Minutes: Workshop III - IT structure and documentation in SharePoint
Minutes: Workshop III - IT structure and documentation in SharePoint
IT structure and documentation in SharePoint
Benedikt Jakobi, University of Paderborn, WinFo
What is SharePoint?
- CMS from Microsoft
- actually for companies, but is also suitable for the FSR
- can be accessed from all operating systems as long as it is connected to a Microsoft account
- already integrated in many Office 365 applications
- no code/low code level -> you don't need to be a Computing Science expert to set it up
What can SharePoint do?
- really a lot
- database
- wiki
- ...
How to link SharePoint with other services
- is created together with a team
- Basis for One Drive
- Power Automated Flow/Apps
- Forms
- ...
In practice
- using the example of FSR Winfo Uni Paderborn
- SharePoint for internal use (documentation, wiki etc.)
- SharePoint is very data orientated
- own database stored
- in Teams: office hours channel
- Power Automated Flow is stored in SharePoint
- emails are automatically assigned to the person who needs to process them (who is currently in office hours)
- Setting up such a Power Automated Flow is relatively complicated: requires coding -> not for amateurs
- it has to be done once, then you can orientate yourself on it
How to create a SharePoint page
- Open Office
- Click on SharePoint
- Create a new site
- Team website
- Focus more on documents and management
- Lists, document library etc.
- Focus more on documents and management
- Communication website
- Focus on communication/interaction
- Team website
- Customise according to individual requirements
- Best made private, but depending on the intended use
- SharePoint is very changeable; you have to see what fits best
Questions
- FSR communication officially runs via Teams
- Power Automated Flow is also used for birthdays and member management (granting/revoking rights)