An example of multiple actions using the same uicomponent is the Team pages in Product/Project/Library share the same code, but each action is defined separately for each object. Each action has the same uicomponent of "PROJECT_TEAM". This allows the same resource entry to be used, and helps to minimize the size of the action display table in the New Profile page. PROJECT_TEAM still needs to be defined in roleaccessprefs.xml for each tab type in which it is used, and different defaults can be set for each.