ProcessTemplatePermissions Class

Inheritance Hierarchy

System.Object
  Microsoft.TeamFoundation.Framework.Common.ProcessTemplatePermissions

Namespace:  Microsoft.TeamFoundation.Framework.Common
Assembly:  Microsoft.TeamFoundation.Common (in Microsoft.TeamFoundation.Common.dll)

Syntax

'Declaration
Public NotInheritable Class ProcessTemplatePermissions
public static class ProcessTemplatePermissions
public ref class ProcessTemplatePermissions abstract sealed
[<AbstractClass>]
[<Sealed>]
type ProcessTemplatePermissions =  class end
public final class ProcessTemplatePermissions

The ProcessTemplatePermissions type exposes the following members.

Fields

  Name Description
Public fieldStatic member AllPermissions
Public fieldStatic member GenericRead Read process template metadata
Public fieldStatic member ManageTemplates Create/Delete/Update process templates.
Public fieldStatic member ReadTemplateContents This lines up with the 'CreateProjects' permission bit, but if process template security had its own security namespace this is what we'd call this permission. Users who can create projects should be able to read the template contents in order to run PCW.

Top

Thread Safety

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

See Also

Reference

Microsoft.TeamFoundation.Framework.Common Namespace