Who can use this feature?
- Global admins or users with advanced permissions
- Available on all plans
Privileged data will only be visible on accounts within a team's core scope. If a team member views an account profile that falls in the team's extended scope (if enabled), privileged data will be hidden from the profile. Any account-level attribute can be marked as privileged.
In addition to attributes, optionally mark layout components of the account profile for privileged access (e.g., Contacts widget or particular collections).
Mark an attribute or custom metric as privileged
Privileged access for a hierarchy roll-up is derived from the attribute or custom metrics used in the roll-up.
- Within Settings, expand Data Management > Data Modeler.
- From the Account Attributes tab, click on the attribute or custom metric you want to modify.
- From within the attribute properties, select the box next to Mark as privileged access. (If modifying a custom metric, you must click to Preview the affected accounts.)
- Click Save.
The attribute will be denoted with a shield icon in Data Modeler.
Team members that have an account in their team's account set can view this attribute on the account profile:
Team members that do not have the account in their team's account set but have extended scope enabled cannot see or search for this attribute on the account profile:
If a hierarchy roll-up was based on the now privileged attribute, the hierarchy roll-up will be privileged as well.
Mark a collection as privileged
- From an account profile, click the Ellipses (...) > Settings.
- On the Visibility tab, select the collection(s) to mark as privileged access.
- Click Save.
Team members that have an account in their team's account set can view the collection on the account profile. Team members that do not have the account in their team's account set but have extended scope enabled cannot see or edit items in the collection.
Question: Will privileged data be hidden everywhere else in Totango, including the account profile?
Answers: The only instances where a team member in an extended scope may be exposed to privileged data is if a SuccessPlay task is assigned that includes a privileged attribute as dynamic data in the description, or if the health reason is denoted as a privileged attribute. In both cases, the creator of the SuccessPlay and the designer of the health profile will see a shield icon next to the attribute with a notification that they are potentially exposing privileged data to users outside their team.