TeamForge roles and permissions

Questions about setting permissions and using roles in TeamForge.

• What does it mean to be a site administrator?
  CollabNet TeamForge administrators are responsible for administering users, restricted site administrators, projects, project groups, roles and integrations with external tools such as software configuration management (SCM) systems.
• How do site administrator roles work?
  Site administrators are default site managers who can create additional site administrators and delegate few site administrative tasks to them. They can also allow some CollabNet TeamForge users to use one or more CollabNet TeamForge tools across several projects, by creating site-wide roles with specific project permissions, minus site administrative permissions. They can also provide ready-to-use roles as global roles, creating uniformity across the site.
• What is a site-wide role?
  A site-wide role grants access across projects, optionally inclusive of administrative permissions.
• What is a project group?
  A project group is a set of projects grouped together for administrative purposes. Project groups enable administrative actions to affect multiple projects and users simultaneously.
• What is a user group?
  To manage multiple users at once, create a group to represent them.
• Can I ensure that only site admins can create projects?
  As of SFEE 4.3 SP1, you can do this using Velocity.
• What does it mean to be an additional site administrator?
  In CollabNet TeamForge, the users who are assigned additional site administration tasks are basically restricted site managers. These restricted site administrators can assist in administering projects, project groups, system tools, users, user groups, roles and categories. However, core tasks like integrations with external tools such as software configuration management (SCM) systems and license key functions can not be delegated to additional site administrators.
• How do I require approval for new user accounts?
  As of SourceForge 4.1 SP3, it is possible to configure the system so that new users can create their own accounts, but the accounts are not activated until a site admin approves them.
• Can I disable creation of user accounts?
  As of SFEE 4.1 SP3, it is possible to disable the creation of new accounts by users so that only a 'site admin' can create new users.
• Can I create new accounts as 'unrestricted' by default?
  As of SFEE 4.1 Hotfix 4, it is possible to configure SFEE so that all new accounts are 'unrestricted' by default instead of the moresecure 'restricted' default.
• How can I prevent users from creating their own account?
  In the site-options.conf file, uncomment the token "DISABLE_USER_SELF_CREATION=true" to disable user self account creation.
• Why is a user restricted and cannot be changed?
  If using the SourceForge integration with CVS, the machine running CVS must be using the default Linux authentication method (/etc/passwd, /etc/group) and not a network service (NIS, MS AD, MS winbind, etc).
• Why don't I have access to the "Reported in Release" information in my artifact?
  If you cannot see the "Reported in Release" information in your artifact, ask your project owner to add the role required to obtain access to this information.
• Can I set permissions so that users can move documents but not delete them?
  You cannot configure document management permissions so that a user can move documents but not delete them.
• Can I grant users permissions to create their own accounts?
  Yes, as of SourceForge 4.1 SP3, it is possible to configure SourceForge such that new users can create their own accounts, but the accounts are not activated until a Site Admin approves them.