A project can succeed or fail depending on the character of the community formed by its members. This is true regardless of the project being private or public. It is the members who contribute their effort and time (for whatever compensation) to realize the project's ideas and goals. Accordingly, because the project members are so important to the eventual success of the project, it is important that the Project owner clearly establish the rules and guidelines determining member participation, including their roles, and articulate what they can expect from the project.
Project members are often added at the time the project is created. However, you can invite and add new members at any time by going to your Project home page and clicking on the Membership link. The following discussion first goes through the procedure of inviting someone to be a member of your project, then looks at how to add a new member.
Once in the Membership page, clicking on the Invite new members link allows you to send an invitation to a prospective member. Click on the link, and a new page opens with fields allowing you to specify the e-mail address or addresses of the persons you wish to invite, and an invitation message. There are two parts to this message. The first, which you compose here, should be in plain text only (HTML is not supported), and should be a greeting and welcoming message. You can, depending on your needs, stipulate here what role you would prefer the invitee to take. There is time later, both for the invitee and for you, as Project owner, to change the member's role.
The second part of the invitation message is the project description which you composed at the time the project was created. If you added several e-mail addresses in the People to invite field, each will receive the same message, so the welcoming message should be inclusive enough to accommodate the interests of everyone you have invited.
You can invite anyone with a valid email address to be a member of your project. They need not, at the time of invitation, already be registered users. However, those you invite who are not registered users are prompted to register on the site as part of viewing your project information.
Note:The ability to invite new users is controlled by the Allow User Join option in the Access policy for your domain. Contact your domain administrator if you are unable to invite new users.
Users you have approved for project membership (whether by your invitation or their request), are listed by username on the Membership page along with boxes indicating their role or roles (project members may hold more than one role). As Project owner, you can change those roles by checking the box by the role name and then clicking on Revoke checked roles button.
If you wish to add a registered user without sending an invitation:
To add multiple users through Mass add:
You can add as many users to your project as you wish. Because every member in a project must have a role, when you add someone to your project you must, at the same time, specify a role. Accordingly, the Grant these roles to all designated users check box lists all available roles. Once you have selected the user(s) you want and the appropriate role(s), click on the Grant roles button. Those users will be added to your project with the roles you have stipulated.
If you wish to return to the Membership page immediately after granting roles, select the Done granting roles check box before clicking the Grant roles button.
For more information about member roles, see Project roles.
You can change a project member's roles by revoking one or more of them and adding new ones. Roles are revoked directly from the member list on the Membership page.
To revoke an existing role:
To grant new roles:
For more information on granting roles, see Adding new members above.
If no existing role fits the needs of your project, you can create roles specific to your project. To learn how to create project roles see Adding project roles.
You have the option to create custom roles and assign the appropriate permissions to them to meet the needs of your project. You should take some time to plan the scope of any new role you create before beginning the creation process. Project roles enable associated user actions within your project only.
Click the Create role button. Use this feature with extreme caution! Assigning permissions to roles may have security implications.
Some permissions you associate with roles require the assignment of resources. Assigning resources allows you to limit the areas of the project that can be affected by persons with the permission. Those permission for which you can assign resources have a drop down box in the resource column in the Project permissions table. Use this box to limit the permission's scope to specific resources within the project.
Selecting ".*" applies the selected permissions for this role universally to all project resources available to this role, including both web content and source code.
Choosing the "/www/.*" option within this list limits the selected permission for this role specifically to web pages. This means the scope of this permissions does not pertain to any source code level access, but only to web page content. For example, assigning the "Version Control - Commit" permission to a role and designating "All web pages /www/.*" as the resource results in users with this role only being able to check out and commit web page content, not project source code.
After you have selected the permissions to add and determined the site resources to apply these to, click the Create role button.
A member might request a new role at any time. If someone has requested membership in your project, or an existing member has requested a new role, the Requests pending approval table will appear on the Membership page. You can approve, defer, or disapprove these requests by selecting the appropriate radio button in the Operations column of this table. If you are disapproving a request, you should enter a comment explaining why in the Reason for role disapproval text box. This comment will be included in an email to the user notifying him or her that the request was denied. When you are finished, click the Submit button. The change is effective immediately.
The tracking components enables you to manage and assign tasks to your project members. As the Project owner, you may assign issues/artifacts to members, or you can give other members the ability to assign issues/artifacts. For help with Issue Tracker, see the Project issues. For Project Tracker help, see Introduction to Project Tracker.