Sharepoint - Scope of Features at different level

Features scopes are defined as

Farm Level


  • A farm level feature, as the name suggests, is something that affects the whole farm, for example provisioning a custom timer job or deploying a Business Connectivity Services model.
  • Farm Scoped feature can be activated at the Farm level.
  • It can contain number of element like application logic etc which can be applicable anywhere within deployment. It contacts links to /_layouts pages and files, /_admin pages etc.
  • It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName
  • Alternatively open Manage Farm Features from Central Administrator Central Administrator -> Operations -> Manage Application Features and click activate. Farm scope feature will be activated automatically once it is installed on server.

Web Application Level:


  • A web application feature can be activated so that it only affects a single web application, and a typical example is a feature that modifies the web.config file.
  • Web Application Scoped feature can be activated at the Web application level.
  • It can contains item like administrative web application links, delegate control registrations, document forms registration etc.
  • It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName “url http://sharepointserver
  • Alternatively open Manage Web Application Features from Central Administrator Central Administrator -> Application Management -> Manage Application Features and click activate.

Site Level:


  • A site scoped feature can be activated so that it only affects a site collection, an example being the deployment of a master page to the master pages catalogue.
  • Site Collection Scoped feature can be activated at the site collection level.
  • It can contains item that can apply to Site Collection as a whole like content types that are shared across the site collection, as well as items that can be activated per site for e.g. List Instances, Event Receivers, Custom Actions etc
  • It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName “url http://sharepointserver/site/sitecollectionname
  • Alternatively open site features page by site actions -> site settings -> modify all site settings ->site features and click activate.

Web Level:


  • Finally, a web scoped feature can be activated for a single site, for instance setting the default master page for that site.
  • Web Site Scoped feature can be activated at individual Web site level.
  • List Instances, Event Receivers, Custom Actions etc are the custom elements for Website scope features.
  • It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName “url http://sharepointserver/site/subsite
  • Alternatively open site features page by site actions -> site settings -> modify all site settings ->site features and click activate.

References

  • Understanding Features and Feature Scope
  • Using Features and Solutions to Deploy your SharePoint Customizations

What you have understood is correct.. Scope defines the range of area where your feature will effects on getting activated. If you activate at parent level(web app) it will be available at child site( site collection and subsites ). ..while if you define just a site as a scope..it will be just that site and no other site.

Tags:

Scope