There are three ways you can prevent users from making changes to SharePoint (WSS) content types. Also there are few things to consider before taking these steps.
1: Read-Only content types:
You can set it read-only using the interface, like this..
But once you set it read-only, then:
- You cannot make changes to the content type thro WSS interface.
- YOU CAN only make Changes programmatically using object model.
- Pushing down parent content type changes (if any) is little tricky.
2. Sealed Content Type.
This provides more control, but a content type can only be made sealed type by editing the XML definition of the content type.
But once you set it sealed, then:
- You cannot make changes to the content type thro WSS interface.
- You cannot make changes programmatically using object model.
- Pushing down parent content type changes to the sealed content type is not possible.
3. Hidden type.
You can assign a content type to a predefined group called, “_Hidden” (case sensitive). You can set it as shown below..
But once you set it to hidden group, then:
- Hidden types are not visible, so you cannot make changes to the content type thro WSS interface.
- You can make changes programmatically using object model ( including inheriting).
- Pushing down parent content type changes to the child content type is possible.
For hidden , see here for more information. Content Type Access Control
Hope it helps.
0 comments:
Post a Comment