Project members
Add people to the project and give each one a role. Roles decide what they can see and do.
This page applies to the System and project configuration stage.
Page in the app: /p/{projectId}/settings/members
Adding a member
Least access first. Add more when someone asks.
- Find the person. They sign in once through your company login.
- Choose roles. Pick the least access that does the job.
- Review often. Remove people who leave the project.
Project manager guide
The right people in the project, each with the smallest role that does the job.
- Add the core team.
- Do now: Choose the user and a role, then select Add. Start with both project managers, the sponsor, the system owner and the test lead.
- Why: Roles decide what each person sees and approves.
- The app checks: Managing members needs the project administrator permission. A person must have signed in once.
- Next: Check that every approval has a decider.
- Cover every approval.
- Do now: Open Approval rules. Check that someone holds each role that a rule names.
- Why: An approval with nobody to decide it waits until it escalates.
- The app checks: The steering group is made of people with a confirmed steering group role.
- Next: Review the list from time to time.
- Remove people who leave.
- Do now: Remove the roles of anyone who leaves the project.
- Why: Least access is the safe default.
- The app checks: Removing a role takes the person out of open approvals for that role.
- Next: Return to the stage guide you are following.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: