It would be particularly useful if you have a complex and changing Perforce permission scheme (done using "p4 protect") that Fisheye would automatically respect that and not force administrators to duplicate the permissioning twice:

• Once in P4 itself
• Once in Fisheye

Particularly this could make things quite complicated under the repository protection scheme, because you'd have to have wholly different repositories to represent the permissions, since permissioning is done against a particular repository and not against a sub-hierarchy.