TeamForge 8.2 Permissions for Resource Patterns

Permission Mapping Details

CollabNet Enterprise Edition Permission	TeamForge 8.2 Permission	Change in Behavior	Functionality Loss/Gain Details	Comments
Resource - Add		User loses permission	The user will lose the ability unless it is a project role and the user gets project administrator permissions.	Path-based permissions (PBP) is the equivalent and is configurable only by project administrators. No such feature at domain level.
Resource - Delete		User loses permission	The user will lose the ability unless it is a project role and the user gets project administrator permissions.	Path-based permissions (PBP) is the equivalent and is configurable only by project administrators. No such feature at domain level.
Resource - Edit		User loses permission	The user will lose the ability unless it is a project role and the user gets project administrator permissions.	Path-based permission (PBP) is the equivalent and is configurable only by project administrators. No such feature at domain level.

Tip: Some examples given below may give you an idea of how PBP can be used to replace the regular patterns that were being used.

Example of regex that can be transformed completely using PBP:	/tags($\|/.*) - This pattern implies anything that starts with /tags/ or exact '/tags'. As the regex is like a super path pattern, here a PBP like [/tags] can suffice.
Example of regex that can be transformed only partially:	/branches($\|/$) - This pattern implies only '/branches' and it does not match '/branches/xyz'. This can not be achieved using PBP as [/branches] would match everything under '/branches'. However, as a complex approach, you may need to grant access to [/branches] and disable all its child path access with explicit path components.

Note: It is recommended that you try this on stage before doing it in production.