How to Set Up and Manage Stakeholders in Arovy

Overview

Stakeholders in Arovy are a flexible way to document the people and teams who own or have an interest in your Salesforce org — without adding them as active Arovy users. Use stakeholders to tag ownership across applications, metadata, fields, and more, keeping your documentation organized and accountable.

Applies to: Arovy Settings | Feature: Stakeholders

Prerequisites

• An Arovy account with access to Settings
• A clear sense of the teams or individuals relevant to your Salesforce governance work (e.g., Finance, Sales, a specific compliance contact)

Estimated Time

~2 minutes per stakeholder

Background: Stakeholders vs. Users

It's important to understand the distinction before getting started:

Stakeholders are purely for documentation purposes. Adding someone as a stakeholder does not notify them, grant them access, or create any activity in Arovy.

Step-by-Step Instructions

Step 1: Open the Stakeholders Settings

1. Click your initials in the top-right corner of Arovy.
2. Select Settings from the dropdown.
3. Click the Team tab.

4. Select the Stakeholders sub-tab.

   This page lists all existing stakeholders in your workspace.

   

Step 2: Add a New Stakeholder

1. Click Add New Stakeholder.
2. Enter a Name for the stakeholder. This can be:
   • A team or department (e.g., Finance, Sales, Legal)
   • A specific individual (e.g., a key governance contact)
3. Optionally, enter an Email address for the stakeholder. This is useful for documenting who to contact but does not trigger any notifications.

4. Set the type to either Individual or Team to keep your stakeholder list organized.

   

5. Click Add (or your workspace's equivalent confirm button) to save the stakeholder.

   The new stakeholder appears in your list and is now available to assign across Arovy wherever ownership fields appear.

Expected Results

After adding stakeholders:

• The stakeholder is available as an assignable value in ownership and stakeholder fields across applications, metadata, and Data Dictionary entries
• No emails, notifications, or invites are sent to the stakeholder
• Your team has a scalable, consistent way to document ownership without adding noise for external teams

Troubleshooting