UrbanCode Release's role- and team-based security system enables you to model releases that mimic your internal organization. Roles logically represent user functions and have actions defined to them, such as editing release plans or scheduling deployments.
Actions are defined per resource type. A resource type is a part of the product that can have user actions restricted by role. UrbanCode Release has several resource types, such as release, and life-cycle model. You define the actions a role can take for each resource type when you create the role. A role can have any or all actions granted to it.
Teams are collections of users grouped around a shared activity. Teams have access to particular resources (taken from the various resource types).
When a roles is assigned to a team, its actions are granted to the team. If a role grants the edit action to the project resource type, then the team can edit any project to which it has access.
Finally, before a user can perform any meaningful activity, he or she is assigned to a role on a team. The role defines the actions available to the user, and team membership determines the actual resources on which the actions can be applied.