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 project roles and/or creating roles and assigning the roles to project members.
What is a global project role?
A global project 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 an Available upon Request role?
The Available up on Request role is a role which a project member in CollabNetTeamForge can submit a request for. You must be a site administrator or project administrator to create a Available upon Request role.
Who can access an application?
Application permissions help you minimize the need to create and assign many similar roles for individual users. Instead, 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 CollabNetTeamForge project by a combination of project settings, membership rules and user restrictions.
As a project admin, why don't I have permissions to the wiki?
Most likely, your site was installed before TeamForge contained the wiki component. When the wiki was added to TeamForge, 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.
