Skip to main content

Portfolio permissions

Learn how to set Company data access levels within Roles

Carly Hammond avatar
Written by Carly Hammond
Updated over 3 months ago

Summary

  • "Portfolio permissions" are set of permissions within Roles. Roles are how you (as a Planhat admin) can apply different access levels to groups of Users within your Planhat tenant

  • "Portfolio permissions" define which Companies can be viewed and updated by Users with that Role

  • You can choose from 4 options for each Role:

    • Only My Portfolio

    • Full Access

    • Team Access

    • Filter Based (where you configure a custom filter)

Who is this article for?

  • All Planhat Users

  • This is particularly relevant for Planhat admins/builders who configure their tenant for their team (e.g. CS Ops)

Introduction

Planhat is incredibly powerful, with a wide variety of features; and also your Planhat tenant is home to a large amount of data, with all your customer data compiled in one place. So that Planhat isn't overwhelming for individual Users, and to enable security and control, you (as a Planhat admin) use "Roles" to configure access levels (set permissions) for groups of Users, streamlining what they see in the UI.

"Roles" are typically based on job role, such as Administrator, Manager, CSM and Developer. They are a similar concept to profiles or permission sets in other tools. In upgraded Planhat (ws.planhat.com), you configure Roles within the "Settings" Global Tool. See here for more general information about Roles.

The main groups of permissions within Roles are data model permissions and workflow permissions (for features and Modules), which are tabs within Roles (shown to the right-hand side of the screenshot below).

In this article, we will focus specifically on the "Portfolio permission" section at the top of each Role (shown in the screenshot below). Portfolio permissions define which Companies (customers/prospects) Users with that Role can see (e.g. in the Data Explorer). This means you can restrict access for data security, while ensuring each Planhat User sees the Company data they need. For example, you might want a CSM to only see the Companies that they manage. Or you might want a Manager to view the Companies managed by their team.

"Portfolio permission" is a dropdown menu within each Role, where you can choose from 4 options:

  • Only My Portfolio

  • Full Access

  • Team Access

  • Filter Based

We describe each of these in more detail below.

You can click on the images throughout this article to view them enlarged.

πŸš€ Tip

Ensure you distinguish between these permissions, which restrict access to groups of Companies based on their Owners (or Co-Owners) or other properties, and the set of data model permissions for the Company data model.

In the data model permissions, you set Create/View/Update/Remove/Export permissions for the Company data model, and also determine these access levels for Company properties/fields.


Only My Portfolio

Definition

This is the most restrictive portfolio permission.

It means that (e.g. in the Data Explorer) you only see the Companies where you are either the Owner or the Co-Owner. "Owner" and "Co-Owner" are standard (default/system) team member type fields on the Company model.

Use case

For data security reasons, or so their view isn't cluttered with irrelevant data, you may want Users with the "CSM" Role to only have access to the Companies that they manage.


Full Access

Definition

"Full Access" means that Users with that Role will have access to every Company in your Planhat tenant.

Use case

This is typically selected for the "Administrator" Role, as Planhat admins will need to see all data. You might also want to give Full Access to the "Manager" Role.


Team Access

Definition

"Team Access" is a portfolio permission aimed at managers.

It uses the "Team" feature, which you can configure in the "Settings" Global Tool. "Teams" allow you to group your choice of Users based on job role (e.g. CSM team) or location (e.g. Australia team), etc. Once created, you can then apply the Team as a filter throughout Planhat, as well as using the Team within portfolio permissions as discussed here.

"Team Access" gives you access to Companies managed by your teammates within the Team (i.e. Companies where they are Owner or Co-Owner, in addition to Companies where you are the Owner or Co-Owner), but only if you are selected as a "Manager" within that Team.

The screenshot below shows you where to configure Teams, and shows a Manager specified within the Team. (Note that this is set within the Team itself, by hovering over a name and selecting "Promote to manager"; it's independent of a User being assigned a "Manager" Role.)

Use case

A typical use case would be the manager of the Enterprise CSM team needing to see the entire Enterprise portfolio managed by their team, but not other Companies managed by other CSM teams.

"Team Access" is typically applied to the "Manager" Role.


Filter Based

Definition

This portfolio permissions option enables you to configure your own choice of Company filter to apply to a Role. This gives you more flexibility, as it enables you to specify/limit Companies based on properties other than who is the Company Owner or Co-Owner.

You can specify different filters within different Roles.

Use case

For example, if you have a Renewals team working specifically on renewals (but those Companies are managed by a separate CSM team), you could create a filter of "Phase is equal to Renewal" for a custom "Renewals" Role.

You can include multiple conditions if desired, such as "Company Tier is SMB and Region is Americas".

πŸš€ Tip

Click "+ Update filter" (shown in the screenshot above) to save your filter configuration.


Extended Groups

If you've given a Role "Full Access" for its portfolio permission, that's it! You can move on to setting the data model permissions in the Role.

However, if you've assigned any of the other options, another setting will display underneath the "Portfolio permission": "Extended Groups". This is a toggle switch, as shown in the screenshot below.

This setting is related to Company group structures: parent and child Companies (e.g. you might have Coca-Cola Global as a parent Company, with Coca-Cola Germany and Coca-Cola Spain as child Companies).

If the "Extended Groups" permission is enabled, it extends the Role's access so its Users can see all Companies in the group structure, if the Planhat User has access to at least one Company. This can be useful for situations where a different User is the Owner of the parent than the child.

Did this answer your question?