I have to create a team site with Sharepoint 2010 for a company that has several departments.
Requirements (simplified) are:
Top Menu: company / department-A / department-B
Main-page (default, home page):
company news
department-A tasks
department-B tasks
company quick launch menu (on the left)
Department-A-page
department-A news
department-A tasks
department-A quick launch menu (on the left)
Department-B-page
department-B news
department-B tasks
department-B quick launch menu (on the left)
So I have 2 lists of departments tasks to share between pages. I have to create personalized quick launch menu per each page (home, department-A, department-B) also.
How can I do this?
If I create several site pages (one page per department) and customize top level menu, then I can't customize quick launch menu per page. Because it seems to be the only one for the whole site.
If I create nested team sites (one site per department) I can't share task lists anymore?
What are the ways to customize quick launch menu per every page or share lists between sites?
Thank you in advance!
I recommend you to create sub-sites for each department and store department-specific data under them. It will help you in future (when sites will grow) to:
not have mess of lists in home site
create department site template (to create site for department "C" in few clicks)
sitemap and navigation controls will be automatically populated
easier to configure permissions (no need to set-up permissions for each departmental list)
The only disadvantage of this approach is that it will be more complex to show task from child site on the home site (do you really need it?). However this can be achieved by implemented custom webpart or using dataview webpart (xslt).
QuickLaunch can be customized from site settings or from code (for example via features).
Let me know if you have any other questions.
Related
I'm pretty new to Sharepoint, but my company wants me to set up a Sharepoint to manage discussions, documents and tasks.
The company has two different departments, so I made one main site and two subsites, one for each department.
On each subsite I have a discussion board. I'm trying to show the "hottest" discussions from each board on the main site. What is the best way to do this?
(I'm using Sharepoint Online)
The best way to do this is using a SharePoint content search webpart. To get your head around the basics of how to pull search results from multiple sites see SharePoint 2013 Search: My Open Tasks
I have a SharePoint Site called ProxymGroup which has multiple affiliates and departments.
I created the webApplication and added 2 managed Paths of type WildCard called Affiliates and Departments.
Under affiliates i needed to create 3 site collections and under departments 2 other SiteCollections. So, here i have the links for the siteCollections:
http://MyHostName/affiliates/SiteCol1 ... and http://MyHostName/departments/SiteCol1 ... etc.
My goal is to display all that hierarchy in theTopNavigationBar menu of the siteCollection because when i activated SharePoint server publishing feature and checked Show SubSites in navigation tab under site sittings it only showed me the subsites, not the siteCollections created under this site.
How can i do please to get that hierachy shown in my TopNavigationBar menu???
Thanks in advance
as far as I know there is no ootb way to show information in the navigation shared among site collections. each site has its own master page and can only display subsites, not other site collections.
alternatively, you can create a powershell script that sets the same navigational items for all the existing site collections, adding links for all the existing sites in all menus of all sites
...or just create subsites
Go to Site settings -> Look and Feel -> Navigation and you can add links manually and change the hierarchy as you want , Please check below image for same.
I have one main site with many subsites. Each subsite is basically a department within the organization. I have a time card infopath form (with workflow) that everyone in the organization needs to fill out. However, I want keep the form so that each department can only see within their own unit. I know I can create a form library within each subsite, but that would make it a maintenance nightmare. I just want to create the form under the main site and create links within each subsite. When a user click on the link, it will take them to the central repository but I filter by the department or permissions? I believe you can set some sort of permission that each department can view their own? user roles for the form?
Can someone point me to the right path?
Thanks,
Environment: SP2010,Sql server 2008, Office 2010
After searching and searching,
One option if security is not a concern is just to use a custom view with filtering by Department and created by = [Me] or just simply by Department.
or if security is a concern:
technet q/a
I have a site collection with the following structure:
Sales Dept Site (site collection top-level site)
Sales Dept Sub-Site 1
Sales Dept Sub-Site 2
We now have a need to insert a new top-level site so that the new structure will look like the following:
Sales Public Site (site collection top-level site)
Sales Dept Site
Sales Dept Sub-Site 1
Sales Dept Sub-Site 2
So, I need to shove all the existing content down a level and insert a new content at the site collecteion top-level site.
What is the best approach to accomplish this? My thought is to create a new site collection with the top-level site created as I need it (Sales Public Site). I can then export the content of the Sales Dept Site and import it into the new site collection as a sub-site.
You can move entire sites via the 'Manage Content And Structure' from the 'Site Actions' menu on the top level site, so there is no need to export and import sites.
Follow this guide for getting access to the 'Manage Content And Structure' if it doesn't exist in the 'Site Actions' menu.
That approach should work. The easiest method is to export a site template, but that does have a fairly small size limit. For larger sites you may be able to get something working with the content deployment wizard.
Of course any customization of the site that assumes the current structure can't be guaranteed to continue to work. Is it an option to simply change the url and navigation to look like a part of the main site?
You approach is the right one. However if you are using MOSS you should use use Manage Content and structure feature instead of exporting sites. This feature allows you to move your sites and restructure your collection. Learn more...
If you created your site collection as pure collaboration site you will have to activate SharePoint standard Publishing features on the top level site to enable this option.
Please note: This feature is not available in WSS.
I am a beginner in SharePoint and I need to create publishing site that will have multilevel menu. Requirement is that levels will not be fixed and that client should be able to add pages and customize menu.
If I am not mistaken pages can be created only in the first level under the site. I don't see something like folders concept. For the navigation purposes I can add heading and it will be shown as another level. If I need more levels I need to create sub sites.
Site
Page1
Page2
Heading
Page3
Is this correct?
Site
Page1
Page2
Sublevel_1
Page1_1
Sublevel_2
Page2_1
Sublevel_3
Page3_1
...
Can I do something like this without creating SharePoint sub sites ?
If I don't need I will skip writing some custom menu control or write custom SiteMapProvider. I will than need to write UI for managing navigation also.
EDIT:
I have managed to create Folder in Pages list and create (actually move) pages to that folder and even create sub folder but they are not showing on the menu not even in the navigation settings page. I can't approve folder, it is in pending status what ever I try.
I looks like this is not possible by the Andrew Connell: Subfolders are not Supported in the Pages Library in MOSS Publishing Sites
Out of the box, you can modify the navigation for a Publishing site manually.
I assume that you are after a more automated way to do this. Unfortunately, the way to modify the navigation for a PublishingWeb is through the object model and the PublishingWeb.CurrentNavigationNodes object, which would require a timer job or some other method to update as pages are edited/added/deleted.
This is non-trivial and you will still need to create a solution/feature package.
The other way is to create a custom navigation provider.
The issue with both of these options (aside from the actual coding and release) is caching the navigation structure. We have used the standard web cache for the object holding the navigation structure, but using the standard user browsing (i.e. the menu code itself) to kick of a refresh of the navigation is fraught with threading issues.
You can create multiple document libraries in a site and then put the pages in the various libraries. That way you wouldn't need to create sub-sites