Access and permissions in Planview.Me
Planview.Me shows data from your Planview products, so what a user sees starts with what they can already see in those products. This page explains the access model in one place: source-product permissions, workspace membership, Power BI permissions, and how to diagnose access gaps.
The access model at a glance
| Layer | What it controls |
|---|---|
| Planview.Me product assignment and product role | Whether a user can use Planview.Me at all |
| Source-product permissions | What data a user can see or edit. Always applies. |
| Workspace membership | Access to a workspace's capabilities, and whether workspace navigation appears |
| View sharing | Whether a user can see a shared view |
Source-product permissions always apply
- To view data, users require view access permissions to the data in the source product.
- To edit data, users require edit access permissions to the data in the source product.
- Items a user cannot view or access do not appear in Planview.Me, including in widgets and in workspaces. A small indicator may show that some items are hidden. A user does not see confidential items in a workspace that they could not see in the source product.
- Power BI widget reports respect Power BI permissions. If a user does not have access to a report, that is honored in Planview.Me.
Adding a user to Planview.Me does not grant product access to underlying source
Assigning a user to the Planview.Me product does not give them access to AgilePlace, Portfolios, Roadmaps or the other products shown in their views. Recommended order:
- Grant users access in the source products, and make sure the products are enabled in Planview Admin.
- Assign users to the Planview.Me product in Planview Admin. See Setting up Planview.Me (administrators).
- Add users to the relevant workspaces. See Managing workspace membership.
Workspace membership
- Workspace members can access the workspace's capability items. Members can be individual users or groups.
- Membership gives access to all of the workspace's capabilities that are enabled.
- Membership also decides whether a user sees Workspaces in the left-hand navigation. Users who are not members of any workspace see the standard Planview.Me experience, without workspace navigation.
- Capabilities and capability items can be enabled or hidden per workspace. See Managing workspaces.
Membership gives access to the workspace. It does not override source-product permissions: a member who lacks access to a board in AgilePlace does not see that board's items.
Workspace members have a workspace role of Admin or Member. Members of a parent workspace are also members of its child workspaces (downward only), and an administrator can give a user a higher role on a specific child workspace by adding them individually to the workspace. See Managing workspace membership. <!-- CONFIRM WITH PRODUCT: roles shipped as Admin and Member per archive; earlier draft assumed Viewer/Editor. -->
What users see by scenario
| Scenario | What users see |
|---|---|
| Planview.Me views only, not in any workspace | The standard Planview.Me experience with the usual toolbar and product switcher; no left-hand workspace navigation |
| Planview.Me, member of at least one workspace | Home tab plus workspace icons in the left navigation |
| Planview.Me with an Anvi subscription | Home tab plus the Anvi Home icon |
| Planview.Me with an Anvi subscription and workspace membership | All icons in the left navigation |
Diagnosing access gaps
When a user cannot see an item, check in this order:
- Planview.Me product. Is the user assigned to the Planview.Me product in Planview Admin?
- Source product access. Does the user have view access to the item in the source product?
- Product enabled. Is the source product enabled in Planview Admin?
- Workspace membership. Is the user a member of the workspace, directly or through a group? Not being in any workspace explains why workspace navigation is missing.
- Capability enabled. Is the capability or capability item enabled in the workspace? Hidden items do not appear.
- Board placement. A board can be in only one workspace at a time. Check that it is in the workspace the user is in, you can use the global search to verify where it is.