Tag Info

Hot answers tagged

4

Create a new page layout based on the Enterprise wiki but including your web part. This page layout can then be used by all your Enterprise wiki sub-sites. The simplest way is probably to copy the existing Enterprise wiki page layout in the first instance. You will need to use something like SharePoint Designer to achieve this.


2

I would presume that its not in the aspx but rather in the masterpage! its easily done in sharepoint desinger! or through code in a text editor like notepad++ ect.... doing it in the masterpage will do it for all! if you do it within the layouts it would be within the body! and would look wrong ;)! Layouts aspx is for the body thats defined in the ...


2

It's hard to say as you did not specify number of users, number of wiki entries and overall planned size of these libraries. I would only opt. for separate site collections if you will have more than of 200 GB of content in each wiki. This is how I would design it it: Create a single site collection with a home page (root site) Grant everyone permissions ...


1

If your Publishing Web Application is available on internet, any employee can use their AD credentials to login to the system from anywhere. For external customer, you can implement form based authentication. This is simply storing your external customers in an sql server database other than AD and get it working with SharePoint. Here is a good series of ...


1

Unless you use a third party tool or a custom solution, you will need to add your users to the groups manually. SharePoint groups cannot contain other SharePoint groups, so users need to be added to several groups individually. A third party tool or custom code could help automate that. On the other hand, Active Directory groups can contain other groups, so ...



Only top voted, non community-wiki answers of a minimum length are eligible