Portfolio members
A project portfolio is shared with other users from the Members tab. FoxPlan distinguishes two complementary levels of rights:
- The role on the portfolio itself — who can view or administer the portfolio (its views, definition, member list).
- The role propagated to the portfolio's projects — rights granted in bulk on all projects attached to the portfolio.
Sharing the portfolio
- Open the portfolio
- Go to the Members tab
- Click "+ Add a member"
- Pick the user, then assign a portfolio role and/or a project role
- Save
1. Roles on the portfolio
👑 Portfolio owner
The portfolio administration role. The Owner can:
- Manage the portfolio (definition, views, filters)
- Change the portfolio members
- Add projects to the portfolio
- Access projects according to the definition of their members (the owner role does not automatically grant rights on the project content)
👁️ Reader
The consultation role. The Reader can view all projects in the portfolio in read-only, with no editing action.
2. Roles propagated to the portfolio's projects
These roles apply to every project contained in the portfolio. They are additive: when opening a project, FoxPlan keeps the maximum effective role between the role defined on the project itself and the role granted through the portfolio.
| Role | What it grants on all projects in the portfolio |
|---|---|
| 🛡️ Projects admin | Full administration of each project (equivalent to Project Admin across the whole portfolio) |
| 👤 Project leader | Full operational control of each project (equivalent to Project Leader) |
| 👁️ Projects reader | Read-only access to all projects in the portfolio |
A portfolio role broadens rights, it never restricts them. Example: a user who is Reader on a specific project and receives the Project leader role at the portfolio level becomes Project Leader on that project. Conversely, granting Projects reader to someone who is already Project Admin on a project takes nothing away.
- Portfolio owner = administer the portfolio (members, included projects, views).
- Projects admin = administer the content of each project in the portfolio.
A person can hold either, or both.
Reminder: project-level roles
The propagated roles above follow the same logic as project roles (Project Admin, Project Leader, Reader, Resource). For the detail of what each role allows screen by screen, see Project members.
Use propagated roles to factor out recurring access (e.g. give a PMO read access to an entire portfolio) rather than reassigning the role project by project.