Forum Discussion
SP2010 - Splash Page Options
Hi there,
I’m a new member and this is my first post, so please go easy on me! I work for a large organization, divided into multiple teams within multiple branches. I am looking for a solution to the following scenario:
We regularly receive requests for ‘Splash Pages’ for individual teams or branches. On these splash pages people generally want a launch page with pretty icons that bounce to various other IM assets or groups of documents. For example, links to management resources, calendars, operations resources, individual project documents, etc. In the past I have made the mistake of making document libraries and using folders to organize files for easy linking on a splash page. For example, a folder for management resources, operations resources, etc. In doing so, I could lock down the permissions of each folder to the intended audience (i.e. giving only management access to the management resources) and easily link the folder on the splash page.
My question is: is there a better way to organize documents for a splash page without having to use folders or create numerous document libraries for each group of documents? I am familiar with metadata and use it regularly, in addition to grouping, creating views, etc. I have thought about a single document library with one of the metadata fields being Document Theme or something, with the options being the various icons on the splash page. In doing so, I can create views that limit the documents being displayed and can link to the view itself from the splash page icon. My only concern is that people may have access to view documents that they are not privy to, and this cannot happen. For example, people outside of management being able to view the management resources documents when clicking on the splash page icon.
Some things to note: I only have very basic knowledge of SharePoint Designer and the creation of workflows, we do not have access to create sub sites and we are advised not to use document level permissions.
Any suggestions would be appreciated, thanks!
Trevor R.
I’m a new member and this is my first post, so please go easy on me! I work for a large organization, divided into multiple teams within multiple branches. I am looking for a solution to the following scenario:
We regularly receive requests for ‘Splash Pages’ for individual teams or branches. On these splash pages people generally want a launch page with pretty icons that bounce to various other IM assets or groups of documents. For example, links to management resources, calendars, operations resources, individual project documents, etc. In the past I have made the mistake of making document libraries and using folders to organize files for easy linking on a splash page. For example, a folder for management resources, operations resources, etc. In doing so, I could lock down the permissions of each folder to the intended audience (i.e. giving only management access to the management resources) and easily link the folder on the splash page.
My question is: is there a better way to organize documents for a splash page without having to use folders or create numerous document libraries for each group of documents? I am familiar with metadata and use it regularly, in addition to grouping, creating views, etc. I have thought about a single document library with one of the metadata fields being Document Theme or something, with the options being the various icons on the splash page. In doing so, I can create views that limit the documents being displayed and can link to the view itself from the splash page icon. My only concern is that people may have access to view documents that they are not privy to, and this cannot happen. For example, people outside of management being able to view the management resources documents when clicking on the splash page icon.
Some things to note: I only have very basic knowledge of SharePoint Designer and the creation of workflows, we do not have access to create sub sites and we are advised not to use document level permissions.
Any suggestions would be appreciated, thanks!
Trevor R.
2 Replies
Still looking for suggestions, thanks!
I typically recommend controlling permissions at the document library level instead of folders, this makes it easy to align security with different groups of users.
Navigation to content through splash pages, icons and other techniques should be separate from content organization. This makes it easy to change the UI without changing the security/storage architecture.
Keep in mind that SP 2010 is no longer being supported by MS and that 2013 support ends soon. Your organization should be planning on migrating to 2016 or Online.
