Inviting Users & Adding Projects
Updated: Nov 17
Since we have already setup our project, we're now faced with the issue that we don't have anyone else on the team (or the client) on our project. You can click on your picture or the "profile" on the bottom left of the screen and you will see your profile. Since you created the project (and team in this case) you're the Team Admin so you can see the team assigned to this project.
Inviting Team Members
On this profile page, you're able to see the team members that are on the project and add them. By clicking the big + symbol you will see the invitation dialog. Enter the required info
and even add multiple people as well as assigning their team member type (PM, Developer, or Client).
Note that Team Admin is transferable (see below) and is Project Level, so a Team Admin on one project can be a different role on another project on any given team.
You can change the role any user has, including making them Team Admin. On the profile page, you see next to the user's role a pencil and paper. Clicking that allows you to bring up the change permission dialog. You can then select the new type of team member; ie client, developer, PM, or Team Admin and save it. It's that easy!
Adding a Project
You have more than one client, so we need to add a new project. Adding a project to the Mercury Platform is easy. You add a new project by clicking the + in the header (beside the Project Name). Clicking this brings up the new project dialog which, if you created the first
project and signed the team up, you will recognize from the signup process.
You can Easily add the new project's name, click "Create Project" and you'll be set up. From there, you just need to add the client for the new project and any team members that are to be involved. No project is connected so you can rest assured that your information and conversations are private. This works wonders for the client-outsourcer relationship because it aligns the goals and setups up both for success.
Now that we've completed inviting everyone to the team and even created a 2nd project, let's see how those projects act throughout the development cycle. The next post will cover the planning and starting of a sprint.