About controlling access to templates

As described in the sections about security policies, you use permissions in security policies to control the following kinds of access:

Based on their security roles, which users can create new projects, plans, programs, and so on

Based on their security roles, which users are allowed to view and interact with items that others create but not to create things themselves

Based on their project and object roles, which tabs users have access to when they create projects

You also use security policies to specify which templates a user can select when creating a new item.

When a template developer creates a template, the Summary tab includes one or more security policy fields. The value specified in the security policy field determines which users can access the template; if you don’t have a security role that grants you the ability to create objects of that type in the security policy assigned to the template, the template does not appear in your template list when you create an object of that type.

Additional access controls for projects and requests

Example security configuration for project requests