The document provides an overview of the architecture of a SharePoint application used to support the California Project Management Methodology (CA-PMM). It describes the key components including the farm, web applications, databases, site collections, sites, lists, libraries, folders, and more. It then provides step-by-step instructions for administrators to set up and manage the application, including creating a web application, site collections, sites, libraries, permissions, templates, and more.

1. -B-Stream -
-Consulting-
User Manual
Administrator


CA-PMM Online
December 11, 2015
© CSUS College of Business Systems Development Life Cycle – MIS 160 – Professor Spiros Velianitis

2. 2
MIS 160/161 Project
Team Number 1
B-Stream Consulting (Team 1):
Darrell Nygard
David Scott
Matt Gibbs
Nhu-Yen Tran
Nicholas Grant
Noora Azar
Thang Nguyen
Instructor: Spiros Velianitis
12/11/2015
I declare that the entire work submitted in this package is the results of our efforts. The files created and the
work submitted are neither a copy nor the results of another individual’s or group’s efforts. The organization
and methods of this program are of my own design based upon the requirements of this assignment.
Signed by all members

3. 3
Table of Contents
INTRODUCTION ................................................................................................. 4
ARCHITECTURE OVERVIEW................................................................................. 6
I:FARM ..........................................................................................................................................7
II: WEB APPLICATIONS.......................................................................................................................7
III: DATABASES ................................................................................................................................7
IV:SITE COLLECTIONS........................................................................................................................7
V: SITES (WEBS)...............................................................................................................................8
VI: LISTS AND LIBRARIES.....................................................................................................................8
A. Large Lists..................................................................................................................................................................8
B. Security ......................................................................................................................................................................9
VII:FOLDERS...................................................................................................................................9
VIII: LIST ITEMS ...............................................................................................................................9
IX: IISFILES...................................................................................................................................10
X: SHAREPOINT ROOT......................................................................................................................10
XI: SHAREPOINT SYSTEM DATABASE....................................................................................................10
XII:SHAREPOINT_CONFIG................................................................................................................10
XIII:SHAREPOINT_CONTENT_ADMIN..................................................................................................10
A. WSS_Content ..........................................................................................................................................................11
XIV:WEB PART WEB PAGE...............................................................................................................11
XV:INFOPATH FORM.......................................................................................................................11
GETTING STARTED ........................................................................................... 12
I: MANAGE AN ACTIVE DIRECTORY......................................................................................................13
II: CENTRAL ADMINISTRATION............................................................................................................17
A. Create a Web Application.....................................................................................................................................17
B. Create a Site Collection .........................................................................................................................................19
III: MANAGE A SITE COLLECTION ........................................................................................................22
A. Upload the Project Site Content Type.................................................................................................................22
B. Create Project Manager Level Permissions .......................................................................................................26
C. Invite a User to the Site Collection ......................................................................................................................29
IV: MANAGE A SITE.........................................................................................................................31
A. Create a Manager Subsite ...................................................................................................................................31
B. Change the permission level for Project Managers in the Subsite ................................................................33
C. Add a Library to a Manager Subsite Using a Site Content Type ....................................................................33
D. Add Web Parts and Configure Web Part Connections.....................................................................................36
E. Create a Subsite template ....................................................................................................................................39
F. Create a Subsite from a site template ................................................................................................................41
G. Invite a User to the Subsite ..................................................................................................................................44
V: DELETE WEB APPLICATIONS, SITE COLLECTIONS, AND SITES ...................................................................46
A. Delete a Web Application .....................................................................................................................................46
B. Delete a Site Collection .........................................................................................................................................46
C. Delete a Site............................................................................................................................................................47

4. 4
Introduction

5. 5
The CA-PMMOnline toolkitisawebapplicationusedtosupportanddocumentthe use of the
CaliforniaProjectManagementMethodology.The toolkitwasbuiltintoSharepoint.The applicationis
intendedtoimprove accessibility,sharingandcollaboration,aswellas supportthe effective completion
of the toolkit. Twogeneral typesof usersexistinthe CA-PMMtoolkit:AdministratorsandProjectTeam
Members.Administratorssetupthe basicarchitecture andsupportprojectteammembers.Project
Team membersuse the applicationtocomplete the toolkit.
In thismanual,we firstgive youa general overview of SharePointarchitecture tohelpyou
betterunderstandhowourappoperateswithinSharePoint.Then,we provide specificproceduresto
setupthe application,site collections,andsites.
You are an Administrator.Assuch,yourgeneral dutiesinvolvemanagingawebapplication,
managingsite collections,andmanagingsites.One webapplicationcontainsmanysite collectionsand
shouldcontainall the contentwithinthe application(i.e.youshouldnotneedtocreate additional
applicationstomanage the toolkit).Withinthisapplication,youwill create atleastone site collection.At
the site collectionlevel,youwillperformtaskslikecreatingapermissionlevel,invitingusers,and
uploadingasite contenttype.Withinsite collections,youcancreate manysites.Atthe site level,you
performprocedureslikecreatingalibrary(usingthe site contenttype youcreatedinthe site collections
top level site),adding webpartsandwebpart connectionstopages,creatingatemplate site,generating
newsitesfroma template,andinvitingusers.
Warning:This usermanual isintendedtoprovide guidancerelatedtothe managementof the CA-PMM
WebApplicationasconfiguredwithinSharepoint.Modificationstothe structure or settingsof the
applicationmayimpactfunctionality,inwhichcase thismanual maynotprovide sufficientguidance.
Please considerthisimpactbefore makingchangestothe configurationof the Sharepointapplication
and consultMicrosoft’sdocumentationforfurtherguidance.
Note:This applicationwill reference the namesof site collections,site contenttypes,permissionlevels,
sites,andlibraries,aswell asapplicationCentral AdministrationURL,toplevel Site CollectionURL,and
Site URL. All of these shouldbe createdusingarational namingconventionandstoredforreference by
administration.

6. 6
Architecture Overview

7. 7
In thissection, we will provide anoverview of SharePoint components.We will focusprimarily
on the componentsutilizedbythe CA-PMMweb application tohelpthe administratorbetter
understand howtomanage the toolkitwithinSharePoint.
I: Farm
The SharePointFarmisa collectionof SharePointandMicrosoftSQLServerrolesthatare held
togetherbya single configurationdatabase.Whenbuildingthe farm, the firstcomponentthatwill be
createdisthe SharePointConfigurationandAdminContentDatabases.These databaseswill be created
while runningthe SharePointProductsConfigurationWizard.
II: WebApplications
In orderto have a SharePointFarm, itmustcontainat leastone SharePointwebapplication.The
SharePointCentral Administrationwebapplicationiscreatedonce the installationprocessiscompleted.
Thisand everyotherwebapplicationwill be hostedwithinIIS.Whenselectingfromthe existingIIS
website,the websitemustexistonall serverswithinthe farmandhave the same name,orelse the
actionwill notsucceed.The firstwebapplicationgenerallydefaultstoport80, howeverthe GUI will
autogenerate aportnumberonce a webapplicationisassignedtothe port.The host headerallowsthe
specificationof URLs andthese will be configuredintthe DomainName System(DNS) andwillbe
directedtothe servershostingrequestsbydirectlytoa server orto a networkloadbalancerthatwill
directthe networktraffic.The SharePointwebapplicationswill onlybe createdonSharePointservers
that are currentlyrunningthe WebApplicationSharePointService.
III:Databases
A database inSQL Serverisrequired tosupporteverySharePointwebapplication,thisalso
includesthe SharePointCentral Administration.A contentdatabase isrequiredalongsidethe farm
configurationdatabase.The Contentdatabasesare essential inanySharePointenvironment.
IV:Site Collections
AnyfunctioningSharePointwebapplicationisrequiredtohave one site collectionwhichisthe
logical containerof one ore more SharePointsitesthatdeliverscontenttothe endusers.SharePoint

8. 8
supportsbothpath-basedandhost-namedsite collections.Anyadditional sitecollectionscanbe added
usinga managedpath.Managed pathsare cachedon the individual webserversandwillrequirethe
CPU to processincomingrequestsagainstalistof managedpaths.If itexceedsthe supportedboundary
it can cause poor performance.
The SharePointsite collectionisthe highestlevel of securityautonomy.The onlyexeceptionto
thisisthat the userpolicysettingscanbe manipulatedtoallow aparticulardomainaccountexplicit
access to the entire SharePointwebapplication.Site collectionadministratorswill be responsible for
grantingusersrightsto the varioussite collectionsthattheycontrol.Usersandgroups createdat the
site-collectionlevelare availabletoall siteswithinthe sitecollection.All inall,the site administratorhas
complete control overthe entire site collection.
V: Sites(webs)
The site collectioniscomposedof atleastone top-level sitewhichiscalledaweb.Whenusers
create a newsite,theywillbe instructedtocreate a website URLthat will have tobe attachedto the
DNS name assignedtothe site collection.Site ownerswillhave the abilitytogive permissiontoaccess
the site to the same userswhohave access to the parentsite or grant permissiontoaunique setof
users.Encouraginguserstodocumentthe permissionstructureswithintheirsitesisimportantfora
numberof reasons.The firstreasonisthat it can become difficulttotrackdocumentlevel permission
and finda particulardocumentif the wrongpermissionsare set.The secondreasonisthatif the user
may choose tobreak inheritance forthe sole purposeof havingtotal control overtheirownsite.
Breakinginheritanceiswhenthe usercreatesanew permissionstructure differentfromthe the parent.
If permissionsare infactinherited,theywillnothave the abilitytochange userpermissionsonthe new
site unlesstheyare the site collectionmanagers.
VI:Lists and Libraries
The SharePointenvironmentcancontaina single librarythathasthe potential to contailn
millionsof documentsorcontaina large numberof librariesthatwill containdocumentsspecificto
businessunits.
A. Large Lists
SharePoint2013 supportsthe use of large lists.Fromthe SQL Serverscalabilitypointof view,it
will notbe an issue asall of these itemsare essentiallystoredontoone table inthe backend.Thisallows

9. 9
liststobe brokenupintosmallerunitsandwill notimpactperformance.Whatcanimpactthe
performance isthatnumberof itemsthe usersdecide tobringback into a particularview.Asa default,
SharePointwillbringbackpagesinchunksof 30, however,thisisasettingthatcan be easilyoverriden
by the user.Asa listviewcomesto5,000, the performance will graduallydegradeandcouldhave
potential toimpactserverperformance.
B. Security
Lists,like sites,canbreakinheritancefromthe parent.Thiswill resultinthe abilitytorestrict
userswhohave site accessfrom a specificlistorlibrary.
VII:Folders
Foldersare critical inthe SharePointinformationstructure andprovide scalabilitytothe listsand
libraries.THe negative aspectshave beenfromhow individualsorganize theirowndocumentsintheir
networkfile systems.Inmanycases,documentsarthrownintoanyfolderandwheninformation
workersmove the contentfromtheirfile system,oftentimestheywill bringthe datainas is.
The SharePointviewshouldbe restrictedtoasfew itemsaspossible,while maintainingthe
businessvalue.The performance hitisfromthe submissionof thousandsof items,The foldersallow the
organizationof these itemsintosmallerunits.The large listthresholdsaidtokeepthe designsfrom
havinga negative impactonthe infrastructure.Folderssupportthe use of unique permissionsandhave
the abilitytotake advantage of the libraryfeaturessuchasthe Column defaultvaluesettingsfeature
whichallowthe automaticconfigurationof metadataoriginatingoff of heirarchiesinside the document
library.
VIII: List Items
The lists,libraries,andfolderswouldamounttonovalue withoutthe listitem.Thisincludes
everythingimportanttothe organizationwillmostlikelyfallwithinthiscategory.Listitemsare capable
of inheritingpermissionsfromthe item, folder,list,andsite orhave a unique permissionassignedto
them.A unique permissionisnottypicallyrecommended,butanice feature withthe comingtogetherof
automatedworkflows.

10. 10
IX: IIS files
Each SharePointserverinthe farmdemandshavingthe IISrole configured.IISisresponsiblefor
hostingthe applicationpool andwebapplications.Italsoreceivesandrespondstouserrequests.Each
webapplicationgetsaunique folderthatwill containaseriesof files.The file systemandthe database
tablesare relativelystationarythroughoutthe life of the SharePointenvironment.Asnew listsand
librariesare addedtoSharePoint,newfilesanddatabasesare notcreated.Each webapplicationgets
bothan exclusive setof filesforthatindividual webapplicationandagroup of common filesthatare
usedbythe entire SharePointfarm.
X: SharePointRoot
The SharePointRootfoldercontainsall the necessaryfilesthatare usedby the SharePoint
infrastructure.The virtual IISfolderslive inmultiple placeswithinthisfolder.
XI: SharePointSystem Database
While creatingthe initial farm,twodatabaseswill alsobe created: SharePoint_Config and
SharePoint_Content_Admin. SharePointwebapplicationsstore dataincontentdatabases.
XII:SharePoint_Config
Thiscontainsdata aboutall SharePointdatabases,all IISwebapplications,trustedsolution,Web
Part packages,site templates,site templates,andfarmandwebapplicationsettingsparticularto
SharePoint,suchasdefaultquotasandblockedfile types.Itmustbe allocatedwiththe Central
Administrationcontentdatabase (SharePoint_Content_Admin) andonlyone database
SharePoint_Configdatabase issupportedperfarm.The database isn'texpectedtogrow significantly.It
isconsideredsmall andcangrow up to1 GB.
XIII:SharePoint_Content_Admin
Thisdatabase storesthe actural data for the Central Administrationwebapplication.The
SharePoint_Content_Admindatabase mustalsobe allocatedwiththe SharePoint_Configdatabase.Itis
similartoSharePoint_Configdatabase,itisnotexpectedtogrow significantly,soitisconsideredtobe a
small database andcan grow up to 1 GB.

11. 11
A. WSS_Content
It storesall site content,includingfilesindocumentlibraries,listdata,WebPartproperties,
auditlogs,SharePointapplications,andusernamesandrights.All of the data for a particularsite will be
locatedinone contentdatabase.Contentdatabasescanhave one or more site collections.The size will
vary onthe contentdatabase;the databasesare supportedupto4 terabytes,however,itisstrongly
recommendedtokeepitunder200 GB. Administratorsare highlyencouragedtoscale updatabasesthat
supportsa site collectionandscale outtosupportwebapplicationsthatwill needadditional site
collections.
XIV:WebPart WebPage
All the contentona webpart page isdisplayedusingwebparts.Theyare structuredwebpart
contentcomprimisinglists,libraries,andothercollaborative contentincludingrichmedia,otherweb
pages,searchresults,anda collectionof information.Webpartpagesprovidesamiddle landscape
where the usere still have semi-strictformattingcontrolslikepublishingpagesandpartially-controlled
collaborative editingcapabilities.Havingthe capabilitytobe storedinanydocumentlibraryitismainly
storedinsite assets,site pages,oranyother documentlibraryof choosing.
XV:Infopath Form
Thisis the maindocumentthatProjectManagers will be usingthroughoutthe phasesof each
individualproject.The formcapturesdatato be savedandpostedon SharePoint.The documentisused
to access anddisplay datafrom divergentsourcesandhave interactive behaviorsbasedonrules,
conditions,andactions.InfoPathformshave the capabilitytobe submittedtoSharePointlistsand
libraries.Itwill be placedina"FormLibrary" whichessentiallyisadocument libraryhavinganInfoPath
template asthe designateddocumenttype.InfoPathfieldshave the capabilitytobe promotedwhen
publishingtoSharePointsotheycanbe displayedas"Column"datainlibraryview.InfoPathformscan
alsohave workflowsassociatedwiththemthatcanaccess the promotedfields.

12. 12
Getting Started

13. 13
Warning:In general,these procedures are writtensequentially.Thatisto say,each stepshouldbe
performedafterthe priorstephasbeencompleted.Forexample,if you wanttocreate a Site Collection,
youmust firstcreate the Web Applicationyouwanttocreate the Site Collectionin. However,afteryou
have createdone WebApplication,youcancreate manySite Collectionswithouthavingtocreate a new
WebApplication.Inthe same fashion,youcancreate manyManager Sitesaftercreatinga site
collection.
I: Manage an Active Directory
Procedure Overview:Thisstepadds userstothe active directory.Lateron,thisallowsusers tobe
invitedtositesandgrantedpermissions.
Loginto your WindowServer.
Clickon the toolbox on the bottomleft.

14. 14
Rightclickon Tool tab on the up rightcorner.
Select Active Directory Usersand Computers.

15. 15
Once you in Active Directory Users and Computersscreen, rightclickon the Users folder.
Select:UsersNewUser

16. 16
Fill outall the requiredfields.
Clickon Finishbuttonto create a NewUser.

17. 17
II: Central Administration
A. Create a WebApplication
Procedure Overview:In thisprocedure,we create aWebApplication.Thisisthe toplevel of hierarchical
organizationwithinSharepoint.All othermoduleswill be createdandmanagedwithinthisweb
application.
Note:This procedure will require permissiontoaccessCentral Administrationand the following
information:
 SharepointCentral AdministrationURL
 Your User Name
 Your Password
Opena browserandnavigate to the SharepointCentral Administration URL.
Note:The SharepointCentral AdministrationURLshouldbe recordedbythe administratorwhoinitially
configuresandinstallsSharepoint.
The AuthenticationRequired popupwindow will promptyoutoenterauser name andpassword.Enter
your username and passwordandchoose “Log In”.
On the SharepointCentral Administrationpage,click Manage WebApplications (markedinred inthe
screenshotbelow) underApplicationManagement.

18. 18
In the page that is displayed,the WebApplicationstabshouldbe selectedinthe ribbon.
Selectthe Newbutton (highlightedinthe screenshotbelow) inthe Contribute section.
The Create NewWebApplication pop updialogue box shouldappear aspicturedbelow.

19. 19
Make the changeslistedinthe followingtable.Leave all otherinputcontrols attheirdefaultvalues.
Field Data
Name Choose a meaningfuldescriptionforthe application(e.g.,CA-PMM).
Enable FormsBased
Authentication
Selected
ASP.NETRole ManagerName Enter a managername.
Aftermakingthese changes,scroll tothe bottomof the dialogue box,ignore the warning, andselectthe
OK button (highlightedinthe screenshotbelow).
The “Web ApplicationsManager”screenshouldappear,andyour newlycreatedwebapplicationshould
appearas an iteminthe list.
B. Create a Site Collection
Procedure Description:This procedure createsaSite Collection.The site collectioniswhereSite Content
Typescan be uploadedandmanaged.Also,manyManagerSubsites(around2,000) can be createdfor
each Site Collection.
Opena browserandnavigate to the SharepointCentral Administration URL.
Note:The SharepointCentral AdministrationURLshouldbe recordedbythe administratorwhoinitially
configuresand installsSharepoint.
The AuthenticationRequired popupwindow will promptyoutoenterauser name andpassword.Enter
your username and passwordandchoose “Log In”.

20. 20
On the Central AdministrationPage, clickCreate Site Collections (markedinred below) under
ApplicationManagement.
The Create Site Collection screenshouldappear(see the screenshotbelow).

21. 21
Make the changes listedinthe followingtable.
Field Data
WebApplication(dropdownlist) Selectthe correctWeb Application.Any applicationcreatedusing
the proceduresoutlined“Create aWebApplication”will work.
Title Addan appropriate title (e.g.active managers,archive,etc.).
Description (optional) Addameaningful descriptionforthe new site.
Site Address–Chooseasite prefix /sites/
Site Address–Sitename Use a meaningful sitename forthe site collection(e.g.active,
archive,etc.)
Selectatemplate Make sure the “Collaboration”tabisselectedthenchoose “Team
Site”fromthe listof available options.
Primary Site Collection
Administrator–UserName
Enter the site collectionadministrator’susername.Clickthe “Check
Names”button to the right of thisfieldtoverifythe
administratorhasbeenproperlyaddedtothe application’sactive
directory.
Secondary Site Collection
Administrator–UserName
(optional) Enterthe site collectionadministrator’susername.Click
the “CheckNames”button to the rightof thisfieldtoverifythe
administratorhasbeenproperlyaddedtothe application’sactive
directory.
Scroll downand clickthe OK button at the bottomof the screen.

22. 22
III:Manage a Site Collection
A. Uploadthe Project Site ContentType
Procedure Description:This createsa site contenttype onthe top level site of the site collectionusing
the CA-PMMtoolkitInfopathtemplate file.Thissite contenttype canbe usedtogenerate a document
libraryinany subsite throughoutthe site collection.Thislibrarywill use the Infopathtemplate to
generate andstore documents(a.k.a.Projects).
Opena browserandnavigate to the Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharepoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone SharepointApplication.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Selectthe SettingsIcon and choose Site Settings(markedinred below).

23. 23
In the Site Settingsscreen,selectSite ContentTypes (markedinredbelow) under WebDesigner
Galleries.
In the Site SettingsSite Content Types screen, click the Create icon (marked in red below).

24. 24
The Site ContentTypesNewSite ContentType screenshouldappear.Enterthe datalistedinthe table
below.
Field Data
Name Enter an appropriate title (e.g.Project,CA-PMMToolkit,etc.)
Description (optional) Enterameaningfuldescription.
Selectparentcontenttype from DocumentContentTypes
ParentContentType Form
Put thissite content type into Existinggroup
Existinggroup CustomContentTypes
Note:If youdo not select DocumentContentTypes inthe Selectparent content type from drop down
list,then Formwill notappearin the Parent ContentType dropdownlist.
Scroll to the bottomof the page and clickthe OK button (markedinredbelow).

25. 25
In the Site Content TypesSite ContentType screen,click Advancedsettings(markedinredbelow).
In the Site Content TypeAdvancedSettingsscreen,selectUploada newdocument template andclick
the Choose File button. Navigate tothe InfopathForm Template that will serve asthe projectdocument
template forthiscontenttype.
Scroll downto the bottomof the screenandselectthe OK button (markedinredbelow).

26. 26
B. Create Project Manager Level Permissions
Opena browserandnavigate to the Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharepoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone SharepointApplication.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Selectthe SettingsIcon and choose Site Settings(markedinredbelow).
In the Site Settingsscreen,selectSite permissions(markedinredbelow) underUsersandPermissions.

27. 27
Make sure the Permissionstabis selectedinthe ribbonandclickthe Permissionlevelsicon
(markedinredbelow) inthe Manage group.
In the PermissionsPermissionLevelsscreen,click Adda PermissionLevel (markedbelow inred).
The PermissionLevelsAddaPermissionLevel screenshouldappear(see below) andenterthe
changeslistedinthe table below.

28. 28
Field Data
Name ProjectManager
Description (optional) Enteranappropriate description.
SelectAll Unchecked
List PermissionsManage Lists Checked
List PermissionsOverride ListBehaviors Checked
List PermissionsAddItems Checked
List PermissionsEditItems Checked
List PermissionsDelete Items Checked
List PermissionsViewItems Checked
List PermissionsApproveItems Checked
List PermissionsOpenItems Checked
List PermissionsViewVersions Checked
List PermissionsDelete Versions Checked
List PermissionsCreate Alerts Checked
List PermissionsView ApplicationPages Checked
Site PermissionsManage Permissions Checked
Site PermissionsViewWebAnalyticsData Checked
Site PermissionsCreateSubsites ***Unchecked
Site PermissionsManage WebSite ***Unchecked
Site PermissionsAddandCustomize Pages ***Unchecked
Site PermissionsApplyThemesandBorders Checked
Site PermissionsApplyStyle Sheetss Checked
Site PermissionsCreateGroups ***Unchecked
Site PermissionsBrowseDirectories Checked
Site PermissionsUse Self-Service SiteCreation ***Unchecked
Site PermissionsViewPages Checked
Site PermissionsEnumerate Permissions Checked
Site PermissionsBrowseUserInformation Checked
Site PermissionsManage Alerts ***Unchecked
Site PermissionsUse RemoteInterfaces ***Unchecked
Site PermissionsUse ClientIntegrationFeatures ***Unchecked
Site PermissionsOpen Checked
Site PermissionsEditPersonal UserInformation Checked
Personal PermissionsManage PersonalViews Checked
Personal PermissionsAdd/RemovePersonal Web
Parts
Checked
Personal PermissionsUpdate Personal WebParts Checked
Scroll downto the bottomand clickthe Create button .
Note:Since the site contenttype iscreatedand managedonthissite,itis necessarytoaddthis
permission(eventhoughthe projectmanagershouldneversee thissite) soProjectManagerscan
interactwiththe the Librarieswe will generateoneachSubsite usingthisSite ContentType.

29. 29
C. Invite a Userto the Site Collection
Procedure Description:This procedure invitesthe usertothe Site Collection.Thisallows the userto
interactwiththe ProjectLibrarywe will create inour ManagerSite usingthe ProjectSite ContentType
that has beenuploadedtoandcan be usedthroughoutthe Site Collection. Withoutgrantingthe team
memberproperpermissionsatthe Site Collectionlevel,theywouldnothave permissiontouse thisSite
ContentType evenif theyhave the properpermissionsettingswithintheirownsubsite.
Note:Before thisprocedure canbe performed,the usermustfirstbe addedtothe active directory.
Opena browserandnavigate to the Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharepoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone Sharepoint Application.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Selectthe Share icon (markedinredbelow).
In the Share ‘[Subsite Name]’popupwindow,enterthe namesof the usersyouwantto invite. Youcan
selectthe full usersname inthe dropdownlistthatappearsas you type intheirname.

30. 30
Thenclick Show Options,and make sure Members[Edit] isselected inthe Selectagroup permissionor
level dropdownlist,andclickthe Share button.

31. 31
IV:Manage a Site
A. Create a Manager Subsite
Procedure Overview:For eachmanager,we will create a subsite tomanage all of theirprojects. In
SharePoint2013, you can Create a Subsite usingthe “new subsite”Linkavailableon the Site Contents
Page.
Opena browserandnavigate to the Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharepoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone SharepointApplication.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Clickon Site SettingsWheel inthe upperrightcornerof yousite and select“Site Contents”page.
In the Site Contentspage,clickon the newsubsite linkunderthe Subsitesheading.

32. 32
WhenSite ContentsNewSharePointSite page appears,enterameaningfulTitle andDescription and
WebSite Address(URL).
For Selecta template,choose the TeamSite underthe Collaborationtab.
For UserPermissions,selectUse Unique Permissions.
For NavigationInheritance,selectNo.

33. 33
Scroll downto the bottomand click Create.You will be redirectedtothe Site Contentspage andthe
Subsite will be listedtowardsthe end(underSubsites)See below.
B. Change the permissionlevel forProjectManagers in the Subsite
Go to Site Settings
Clickon Site Permissionsunder‘UsersandPermissions’headingandchange permissionlevelsfor
ownersgroupby clickingonthe checkbox andclickedituserpermissions.
NowdeselectFull ControlunderpermissionsandselectProjectManagerpermissions.
ClickOK
C. Add a Library to a Manager Subsite Usinga Site ContentType
Procedure Overview:Thisstepusesthe Site ContentType we manage at the root site of the site
collectiontogenerate adocumentlibraryinthe currentmanager’ssite.
Opena browserandnavigate to the Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharePoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone SharePointApplication.

34. 34
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharePointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Clickon Site SettingsWheel inthe upperright cornerof yousite and select Site Contentspage.
Your new ProjectSite shouldbe visibleunder Subsitesonthe Site Contentspage.Clickonthe Site to
openit.
ClickSite Contentsonthe lefthandside of the site.

35. 35
From the Site ContentsPage, clickAdd an App underthe Lists, Libraries,and otherApps header.
Choose FormLibrary underthe Apps you can add heading.Pickanew name for yourform library.
The newlibraryshoulddisplayinthe leftnavigationpane. Clickthe newlycreatedformlibrary,andthen
selectthe Library tab inthe ribbon.Click LibrarySettingsin the Settingsgroup (markedinred below).
Under General Settingschoose AdvancedSettings andSelectYesonAllowmanagementofcontent
types. ClickOK.
Back on the Settingspage,click addfrom existingsite content types.
Selectyourmostcurrentform contenttype inthe Available Site Content Types group box and clickAdd.
It shouldpopulate intothe ContentTypesto Addgroup box.
ClickOK.

36. 36
Under ContentTypesin the Library Settings,selectChange newbutton order and defaultcontent type
Selectthe PositionfromTop dropdownlistand selectnumber 1for the top buttonorder
ClickOK.
D. Add WebParts and Configure WebPart Connections
Procedure Overview:WebParts are componentsthatcan be usedacross manydifferentsites.Also,
manywebparts can existonone page.We will addthe librarywe createdinthe laststepas a webpart
to the home page of our projectmanager’ssite.Then,we willaddanInfopath FormWebPart. Finally,
we will configure the webpartconnectionbetweenthesetwowebparts.Thisallowsthe InfopathForm
WebPart and Library webpartto retrieve andsubmitformdatato and from eachother.
Opena browserand navigate tothe Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharepoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone SharepointApplication.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Clickon Site SettingsWheel inthe upperrightcornerof yousite and select“Site Contents”page.

37. 37
Your Site shouldbe visible under SubSitesonthe Site Contentspage.Clickonthe Site to openit.
ClickEdit on the topnavigationbar.
Delete all existingwebparts onthe site homepageusingthe checkbox anddropdownarrow.
Clickthe Insert tab onthe Ribbonandunderthe Parts section,click WebPart.
Inside the Categorieslist,click Appsandunderthe Parts list,clickthe documentlibraryyoucreated.
Once selected,clickthe Addbuttontoadd the webpart.
Nowwe will adda secondwebpart to the site.Startby selecting the Inserttabinthe Ribbon.

38. 38
Under Categories,selectFormsandadd an InfoPathForm webpart to the site. Your new site should
now have two newwebpartson it as seenbelow.
Clickthe drop downarrowin the newlycreatedwebpartandselect Edit WebPart. On the newly
openedwebparteditpane,seenbelow,select yourlibraryalongwithyour contenttype.Click OK.

39. 39
ClickEdit on the topRibbonagain.
Clickthe drop downarrowon the Infopath Form WebPart andmake the followingselections:
ConnectionsGetFormFrom[YourLibraryName]
E. Create a Subsite template
Procedure Description:This procedure isusedtocreate a site template forourProjectManager sites.
Thisallowsusto avoidrepeatingthe previousprocedureswhengeneratingnew managersites.
Opena browserandnavigate to the Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharepoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone SharepointApplication.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.

40. 40
Clickon Site Settingswheel inthe upperrightcornerof yoursite and selectSite Contents.
Your new site shouldbe visible under SubSitesonthe Site Contentspage.Clickon the site toopenit.
Clickthe Site Settingsicon and selectSite Settings.
Under the Site Actions header,selectSave site as template.

41. 41
In the Save as Template page,name yournew file andtemplateandclickthe checkbox to Include
Contenton your newtemplate.
ClickOK. You shouldsee amessage similartothe one below indicatingthe OperationCompleted
Successfully.
F. Create a Subsite from a site template
Procedure Description:Use the previouslycreatedsitetemplate togenerate anew managersubsite.
Opena browserandnavigate to the Root Site URL for the desired Site Collection.
Note:The Root Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site Collection
inSharepoint.Make sure youhave the correct URL since multiple SiteCollectionscanpotentiallyexist
simultaneouslyinone SharepointApplication.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.

42. 42
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Clickon Site Settings Wheel inthe upperrightcornerof yousite and select“Site Contents”page.
Your newProjectSite shouldbe visible under“SubSites”onSite Contentspage.Clickonthe TeamSite to
Openit.
Clickon the TeamSite to Openit.
From the site homepage,click Site Contentsonthe leftNavigationPane
Clicknewsubsite.

43. 43
On the NewSharePoint Site page and name yourpage,selecta new unique URL,and whenselecting
Template Selection,choose yournewlycreatedtemplate underthe Customtab. Leave othersettings
the same.
ClickOK

44. 44
G. Invite a Userto the Subsite
Procedure Description:This procedure invitesthe usertoaccessthe Site as a Project Manager. Atthe
site collectionlevel we invitedthe userasa Memberso the user couldinteractwith the ProjectLibrary
we createdon thissite.Thisisnecessarybecause the ProjectLibrary isgeneratedusingaProjectSite
ContentType managedon the toplevel site forthiscollection.Grantingthe user ProjectManager
permissionsallowsthe usertoperformamanymore tasks than a Member.However,theystillcannot
performsome actions,suchas creatingsubsites.
Note:Before thisprocedure canbe performed,the usermustfirstbe addedtothe active directory.
Opena browserandnavigate to the Site URL forthe desired Site.
Note:The Site URL shouldbe recordedbythe administratorwhoinitiallycreatesthe Site inSharepoint.
Make sure youhave the correct URL since multiple Site canpotentiallyexistsimultaneouslyinone Site
Collection.
In the AuthenticationRequired popupwindow, enteryourusername andpasswordand choose Log In.
Note:If youare loggingintoSharepointusingaVPN,youmustadd “domainserver”tothe frontof your
username whenloggingon.
Selectthe Share icon (markedinredbelow).

45. 45
In the Share ‘[Subsite Name]’popupwindow,enterthe namesof the usersyouwantto invite. Youcan
selectthe full usersname inthe dropdownlistthatappearsas you type intheirname.
Thenclick Show Options,and make sure Members[Edit] isselected inthe Selectagroup permissionor
level dropdownlist,andclickthe Share button.

46. 46
V: Delete WebApplications,Site Collections,andSites
A. Delete a WebApplication
Procedure Description:This procedure allowsyoutodeleteanapplication.
Warning:When youdelete anapplication,all site collectionsandsiteswithinthatapplicationwillbe
lost.
Opena browserandnavigate to the SharepointCentral Administration URL.
Note:The SharepointCentral AdministrationURLshouldbe recordedbythe administratorwhoinitially
configuresandinstallsSharepoint.
The AuthenticationRequired popupwindow will promptyoutoenterauser name andpassword.Enter
your username and passwordandchoose “Log In”.
In the Central Administrationmain screen,click Manage WebApplicationsunderApplication
Management.
In the WebApplicationsManagementpage,selectthe applicationyouwanttodelete.
Make sure the WebApplicationstab isselectedinthe ribbon,thenclick Delete inthe Contribute
section.
B. Delete a Site Collection
Procedure Description:This procedure allowsyoutodeleteSite Collection.
Warning:When youdelete Site Collection,all siteswithinthe applicationwillbe lost.
Opena browserandnavigate to the Site CollectionURL.
Note:The Site Collection URLshouldbe recordedbythe administratorwhoinitially createdthe Site
Collection.
The AuthenticationRequired popupwindow will promptyoutoenterauser name and password.Enter
your username and passwordandchoose Log In.
Go to the Site Collection.
Clickthe site settingsiconandselect Site Settings.

47. 47
Clickthe Delete thissite optionunderthe Site Actions heading.
Ignore the warningandclick Delete.YourSite collection isnow deleted.
C. Delete a Site
Procedure Description:This procedure allowsyoutodeleteanapplication.
Warning:When youdelete anapplication,all site collectionsandsiteswithinthatapplicationwillbe
lost.
Opena browserandnavigate to the SharepointCentral Administration URL.
Note:The SharepointCentral AdministrationURLshouldbe recordedbythe administratorwhoinitially
configuresandinstallsSharepoint.
The AuthenticationRequired popupwindow will promptyoutoenterauser name andpassword.Enter
your username and passwordandchoose Log In.
Clickthe site settingsiconandselect Site Settings.
Clickthe Delete a site optionunderthe Site Actions heading.
Ignore the warningandclick Delete.Yoursubsite isnow inthe site recycle binandcan be restoredif
needed.