TeamForge roles and permissions

Questions about setting permissions and using roles in TeamForge.

• How do user roles work?
  Project administrators can define specific access permissions for individual project members. They do this by using global roles and/or creating roles and assigning the roles to project members.
• What is a global role?
  A global role is a ready-to-use role available in all projects. Only site administrators or restricted site administrators can create and manage a ready-to-use role.
• What is a requestable role?
  A requestable role is that role which a project member in CollabNet TeamForge can submit a request for. You must be a site administrator or project administrator to create a requestable role.
• Can I assign a role to all users of the site at once?
  If you are a site administrator in CollabNet TeamForge, you can assign a role to all the system users (non-site administrators) at one go.
• Who can access an application?
  Application permissions help you minimize the need to create and assign many similar roles for individual users. You can permit or restrict access to individual applications within the project for whole classes of users.
• Who can access source code?
  Project administrators can give project members specific kinds of access to a whole Subversion repository or any path within that repository.
• Who can access a project?
  You control access to your CollabNet TeamForge project by a combination of project settings, membership rules and user restrictions.
• Does the project owner receive a mail when a discussion forum is started in his project?
  Yes. Whenever a discussion forum is started the project owner gets an email.
• Do project owners get automatically subscribed to the discussion forum started by another member?
  A project owner does not get subscribed to the discussion forum started by another user.
• Is the discussion forum creator subscribed by default?
  Yes. The user creating the discussion forum is subscribed by default.
• When a discussion forum is set up, do all members receive a notification mail?
  Yes. A mail informing users about the creation of discussion forum is sent to all the members of the project.
• Who is an owner of the subcomponent?
  The user who creates the subcomponent is the owner of the subcomponent.
• 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.
• How can I make the project pages invisible for any user who is authorized to see the project?
  This can be customized by a Project Administrator as shown in the steps below.
• How do I give read-only anonymous access to cvs/svn repository?
  Set the default access permissions of the project to public and allow Source Code to view permission for all or specific repositories to All users while restricting other permissions.
• Why do I see the project home page though I lack the necessary permission?
  This has been set so that when users are provided access to a project, they do not see an empty page.
• As a project admin, why don't I have permissions to the wiki?
  Most likely, your site was installed before SourceForge contained the wiki component. When the wiki was added to SourceForge, it was decided that there was no way for us to know the security requirements at customer sites, so permissions for the new wiki component were not assigned to project admins by default. As a project admin, you can alter any existing role to grant this permission, or create a new role for this permission and then assign to the appropriate project members as needed.