Who can access a project?
You control access to your CollabNet
TeamForge
project by a combination
of project settings, membership rules and user restrictions.
- Who should I allow into my project?
To decide how to control access to your project, think about what the project is for and who will be using it.
- How does inheritance work?
Site or project administrators can create hierarchical relationships between projects so that one project can inherit members, roles and permissions from a parent project.
- How does inheritance work for project groups?
Site or project administrators can create project groups and add member projects to the group, to manage several projects as a single unit. Moreover, hierarchical relationships may exist between projects so that one project can inherit members, roles and permissions from its parent project.
- What is a parent project?
A parent project is the base from which a subproject's members, user groups and roles, with their corresponding permissions, are derived. A subproject can inherit project members, user groups and roles from its parent project.
- Can I block a user's access to source code?
From time to time, you may need to prevent a user from using a source code repository.
- Who can see a project page?
A user can see a given project page if the page is not hidden and the user's role includes permission to see the page.
- Who can see a project page component?
To see a given project page component, you must have permission to see both the project page where the component is and the tool that the component represents.
- Who can access project planning information?
A project manager should consider carefully who is able to change the project plan.