SharePoint Permission Types SharePoint has “local” groups that can contain Active Directory Groups For example, you can have a SharePoint permissions group called “Sales” which can contain Active Directory groups “Sales” and “Sales Engineering” and “Chess Team” Unlike file shares where local groups are generally avoided, SharePoint specific groups are very common – this is makes it much harder to answer the question “Which human beings can access my data?” There are more default permissions types than you can keep in your head at one time (33 in all): 12 permissions types for Lists 3 permissions types for Personal actions (e.g., views) 18 permissions types for Sites Each permissions type can be grouped into Permissions Levels . For example, the default “Contribute” site permission level contains 8 of the 12 site permission types. for More Details Check This Url: http://technet.microsoft.com/en-us/library/cc721640.aspx
Posts
How to recover deleted files from SharePoint get this link http://solutioncenter.apexsql.com/recover-deleted-files-from-sharepoint/ (OR) When you delete a document from SharePoint it’s not completely gone – at first it’s moved to the Recycle Bin To recover files from the SharePoint Recycle Bin to their original location: Navigate to the Recycle Bin by clicking the Recycle Bin link in the left navigation pane of the SharePoint site where the files were originally located Select the files you want to recover Click Restore Selection If the deleted data files don’t appear in the Recycle Bin: Log in to the SharePoint site the documents have been deleted from as the site collection administrator Navigate to the Site Actions menu above the ribbon and select Site Settings In the Site Collection Administration section, click Recycle Bin In the Recycle Bin’s left navigatio...
SharePoint 2010 – Architecture SharePoint architecture design consists of physical and logical architecture. Physical architecture The physical architecture, which consists of one or more servers and the network infrastructure, enables us to implement the logical architecture for a SharePoint Server solution. The physical architecture is typically described in two ways: by its size and by its topology. Size, which can be measured in several ways, such as the number of users or the number of documents, is used to categorize a farm as small, medium, or large. Topology uses the idea of tiers or server groups to define a logical arrangement of farm servers. The three-tier roles of a Microsoft SharePoint Server 2010 farm can be deployed on a single server or many servers. The three-tier roles include: Web Server roles - Host Web pages, Web services, and Web Parts that are necessary to process requests serviced by the farm. - Direct requests to the appropriate a...
Issue Tracking in Sharepoint 2010 Issue Tracking is an out-of-the-box solution provided by Sharepoint to track issues or problems with a project or item. We can assign issues to users, prioritize and track status. Sharepoint allows user to track, record, document their issues or problems, it also alerts the user according to issues priority. Creating Issue Tracking in Sharepoint 1. Open your Sharepoint site. 2. Click More Option from Site actions , select Issue Tracking . 3. Click Create button to create Issue Tracking list. 4. We can add issues by clicking on Add new Item. 5. Select Assign To people from people picker. 6. Find users in the people picker . 7. Select other option like priority, category & related issues . Summary SharePoint Issue Tracking allows end-users to create and manage their Issues or Problems in one place and let users to track and separate issues according to its category. It consists of features like sending alerts to users ...
Migration of SharePoint 2010 to SharePoint 2013 Lets start! Install SharePoint 2013 on a new separate server. Use the configuration wizard. Choose “create a new server farm”. Choose a server and a database name. Get a passphrase then store it in a secure location, you will need this in the future. Choose a security setting. Verify everything is OK. Wait while server is configuring. Smile, the installation is successful. Go to the SharePoint 2013 Central Administration of your new SharePoint, when this shows, it's all good. Go to your old SharePoint database, then copy the WSS_Content database. Verify source server properties. Set your destination SQL Server. Select the Transfer Method, use the SQL Management Object method if you want a live migration. Select a database to copy, you will only need WSS_Content . Configure the properties of Destination Database. Select Objects, you only need Logins here. Saving the package created. Run immed...