Enhanced Multi-Organization Management Tools for Large-Scale Enrollments

Product Feedback
, ,
1

Hi ,

In large-scale enrollment with multiple organizations there are several friction points that make day-to-day administration and usage monitoring more complex than necessary. While the platform supports multi-tenancy, there are gaps in tooling and visibility that hinder effective management at scale.

Below are several specific areas where improvements could meaningfully enhance the experience for platform administrators:

1. Filter Issues by Organization

  • Current State: Issues can be tagged with OrgMarkings, and visibility settings are respected and clear within individual tickets.
  • Problem: There’s no way to filter or group issues by Organization, which makes managing issues across tenants cumbersome. Additionally, OrgMarkings are not currently displayed in the thread list view within the Issues app.
  • Request:
    • Add ability to filter issues by OrgMarking.
    • Display OrgMarkings in the thread list view to improve issue triage and organizational visibility.

image
image1539Ă—719 110 KB

2. Filter Data Connections by Organization or Space

  • Current State: The data connections interface lacks sufficient filtering and sorting capabilities.
  • Problem: It’s not currently possible to:
    • Filter by Organization or Space.
    • Filter based on properties like presence of exports, code imports, or compute modules.
  • Request:
    • Introduce filtering options in the Data Connections UI to support these use cases, which are essential for users managing many assets across different orgs, and most importantly the potential outflows of data across the enrollment.

image
image573Ă—502 17.3 KB

3. Improve Visibility and Management of Egress Policies

  • Current State: Egress policies can be assigned to multiple organizations. When one of these organizations is decommissioned, the policy remains on associated data connections but appears as “Insufficient permissions”—even to platform admins.
  • Problem:
    • There’s no way for admins to identify which egress policies belong to which organization.
    • Visibility is degraded, and orphaned policies become hard to manage.
  • Request:
    • Allow platform admins to filter egress policies by Organization in the Network egress menu and approvals flows of the control panel.
    • Improve visibility and management tools for orphaned or cross-organization policies.

image
image1519Ă—722 62.9 KB

4. Resource Management App – Org level usage monitoring

  • Current State: Usage data in personal spaces must be manually compiled by user, even when organizations or spaces are the unit of interest. Also, one needs to manually add projects to usage accounts.
  • Problem: This approach is time-consuming, error-prone, and not scalable for large or client-facing environments.
  • Request:
    • Introduce grouping by Organization or Space within the Resource Management App
    • Allow direct association of usage accounts with a space or organization (across all its projects), rather than adding individual projects manually

image
image1527Ă—391 60.9 KB

My Recommendation

Currently, the concept of multi-organization enrollment is powerful, however, is not fully realized across key applications, including:

  • Approvals
  • Usage tracking
  • Issues
  • Data Connections
  • Egress policy management

Providing better visibility, filtering, and management options tailored to multi-org setups would improve the platform’s usability for complex enrollments.

2 Likes
2

Hi @HugoRodrigues,

Thanks for the detailed feedback! I’m here from the team that works on Resource Management App (RMA). We have started to notice a pattern of users who want to see RMA organized by space or organization, and we would love to hear more about how this could help you so that we can take it into account for our planning. Delving into the specifics of your requests:

Is there a particular part of RMA that you would like to see organized in this way, maybe Analysis? You may already be aware, but in Analysis the usage account filter could be a helpful proxy if there is a relationship between usage accounts, on the one hand, and spaces or organizations, on the other.

A couple of thoughts/suggestions here:

  • Did you know that you can assign a usage account to a space, which then becomes the default usage account to which new projects get assigned? Obviously this only helps with initial assignment.
    • https://www.palantir.com/docs/foundry/platform-security-management/manage-orgs-and-spaces/#create-a-space
  • In the “Assign projects” dialog in RMA, you should be able to search for projects by space because the space forms part of the file path. It’s not a perfect workaround, but maybe you will find it convenient.

Thanks again,
Noah