To decide how to control access to your project, think about what the project is for
and who will be using it.
Consider these elements:
- The project's access setting.
A project can be public, private, or gated
community.
Note: The site administrator can change the default project access
permissions.
- The project's membership.
- Each site user's user type.
- Each site user's license type.
- Each TeamForge user's user type.
- Any parent projects from which members, user groups or roles are inherited.
- Any subprojects that inherit members, user groups or roles from this project.
User type
Users can be restricted or unrestricted.
- Restricted users can access only public projects and projects of which they are
members.
- Unrestricted users can access all projects except private projects of which they
are not members.
License type
Users can have an ALM license or an SCM license.
- An ALM license enables the user who holds it to use the full range of
TeamForge features: both the core
source-code management tools and the extended application life
cycle management functionality.
- An SCM license enables the user who holds it to use the core
TeamForge source-code management
tools.
License type supersedes user type. For example, if you give a user an SCM license,
and then declare that user an unrestricted user, the user can see only the core
source code management tools in any project they can access.
Project access setting
A project can be private, gated, or public.
-
Private - Private projects can only be accessed by
project members. Private projects do not appear on the Home
page, in the All Projects list, or in search or reporting
results to users who are not project members.
Create a private project when
you want to strictly limit project access.
-
Gated - Gated community projects can be accessed by
project members and by unrestricted users. As with private projects, gated
projects are not visible to users who are not allowed to access them.
Create
a gated community project when you want to exclude restricted users, but do
not need to exclude other, unrestricted users. For example, your
organization might wish to designate all contractors or outsourced staff as
restricted users. They will not be able to see any gated community projects,
but all of your full-time, regular staff will have access.
-
Public - Public projects can be accessed by all users.
Create a public project when you have no need to restrict access.
Note: Project access is not the same as project membership. Project access allows a user
to see the project in the All Projects list, visit the
project home page, and browse selected project data. A restricted user may be able
to access a project without being a project member.
This table shows which user types can access projects with each project access
setting.
| Project access type |
Project member (Unrestricted user) |
Project member (Restricted user) |
Non-project member (Unrestricted user) |
Non-project member (Restricted user) |
| Private |
Yes |
Yes |
No |
No |
| Gated |
Yes |
Yes |
Yes |
No |
| Public |
Yes |
Yes |
Yes |
Yes |