Let me take a step back and provide some context to highlight why this feature request carries broader significance—it’s not just for adhoc analysis and developers.
Context:
Foundry has the potential to be much more than an internal tool for analytics or application development. With foundational security capabilities like Organization Markings, private spaces, and ontologies, it empowers organizations to extend beyond internal use cases and support business-to-client (B2C) initiatives. To the best of my knowledge, no platform in the market offers such primitives in an intuitive, and enterprise-ready way.
B2C engagements, especially those involving licensed data, come with a host of legal and governance requirements. These often include controlling and limiting user access, tracking data usage, and preserving records of what was shared—even after an engagement ends. Since expanding OrgMarkings are implemented by engineers through PRs, there’s always a margin for error and growing organically. This reality makes it critical for enterprise architects to monitor and have clear visibility into the data being shared and managed across the organization, and to have tools that support this oversight.
While Collibra offers support in this area, it often relies heavily on manual intervention. Foundry, on the other hand, has the potential to be a more effective auditing tool since it already hosts the security primitives. The only missing piece is surfacing this information in the right format.
Coming back to your points:
From my perspective, the removal of Organization Markings sits closer to the south of ontology and data engineering layer. As such, I believe the best way to surface or represent this information would be:
- In the Access Graph, for ad hoc analysis
- Within the Project Catalog or Portfolio view (see Broaden scope of curated resources in the Project Catalog - Propose an Improvement - Palantir Developer Community )
- As a dataset—or alternatively, through an API endpoint exposed in the Platform SDK to enable programmatic access. This approach would offer maximum flexibility, allowing seamless integration with external tools when required by auditors.