Skip to content

Administration

Roles and permissions in Palantir "Gotham" Integration & Governance

Each role in Palantir "Gotham" Integration & Governance: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Palantir "Gotham" Integration & Governance as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 5 min readReport a problem
On this page
  1. Roles
  2. Data owner
  3. Data steward
  4. Classifier
  5. Analyst
  6. Moraph data engineer
  7. ISSM
  8. Oversight reviewer (read-only)
  9. Permissions at a glance
  10. How access is controlled

Who can see and do what in Palantir "Gotham" Integration & Governance. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in the platform vendor as part of the managed service.

Roles

Data owner

Mission data owner, collection or program manager, chief data officer's staff. Authorizes each source, confirms the authority to use it, and approves how it is mapped and governed.

  • Sees: Sources they own, with run health and held records; Mappings and rules for their sources; Changes affecting their sources
  • Does: Requests new sources and confirms the authority to use them; Approves mappings to the data model; Approves pipeline and rule changes for their sources; Decides whether a source is retired
  • Cannot: Change markings on records; Change access controls in Gotham through the service; Approve changes to sources they do not own
  • Approvals: Approves onboarding, mappings and changes for their sources; marking decisions remain with classifiers.
  • Notified about: Source run failures, sources not delivering, changes awaiting approval and aged held records.

Data steward

Data steward, data quality analyst, information manager. Keeps the data fit for analysis by approving quality rules and deciding on records held for quality.

  • Sees: Quality rules and their results; Records held for quality in their sources; Patterns of failure by source
  • Does: Approves quality rules; Decides to fix, override or reject held records, with a reason; Requests rule changes; Feeds recurring problems back to source owners
  • Cannot: Decide on marking failures; Deploy pipeline changes; Delete records from the audit trail
  • Approvals: Overrides of a quality rule are recorded with a reason and reported to the data owner.
  • Notified about: New held records in their queue and records approaching the age your procedures set.

Classifier

Derivative classifier, security manager, classification management officer. Decides on records held because of missing or inconsistent markings, under your classification procedures.

  • Sees: Records held for markings, with the rule that held them; Any suggested marking and its basis; The source's classification guidance reference
  • Does: Reviews held records and records a marking decision; Applies a decision to a batch where your procedures allow; Rejects records that should not be loaded; Reports suspected spillage under your procedures
  • Cannot: Change pipeline rules or mappings; Load records that have not passed checks
  • Approvals: Their decisions follow your classification procedures; batch decisions can require a second classifier if you choose.
  • Notified about: Records held for markings and possible spillage flagged by checks.

Analyst

Intelligence analyst, all-source analyst, operations analyst. Uses lineage to understand the records they work with and reports suspected data problems.

  • Sees: Lineage for records they are permitted to see; Source descriptions and freshness
  • Does: Looks up a record's lineage; Exports lineage for an analytic product; Reports suspected data issues to the data steward
  • Cannot: Change records, rules or markings; See held records
  • Approvals: None; their reports go to the data steward.
  • Notified about: Responses to data issues they reported.

Moraph data engineer

Moraph data engineer, Moraph service manager. Builds, runs and maintains the pipelines and checks, and runs the service, within the approvals your organization gives.

  • Sees: Pipeline code, configuration and run logs; Held records needed to diagnose pipeline issues, where cleared and permitted; Changes and service records
  • Does: Profiles sources and drafts mappings and rules; Builds and maintains pipelines under version control; Monitors runs and fixes pipeline failures; Applies approved changes; Runs monthly service reviews and manages vendor cases
  • Cannot: Make marking or classification decisions; Override a quality rule; Deploy a change without approval
  • Approvals: Every pipeline, rule and mapping change has a recorded approval from your organization.
  • Notified about: Run failures, sources not delivering, changes approved and vendor notices.

ISSM

Information system security manager, cybersecurity lead. Approves the security of the pipelines and the mapping of markings to access controls.

  • Sees: Pipeline architecture and environments; Marking-to-access mappings; Administrative activity and changes
  • Does: Approves pipeline architecture and environments; Approves changes to marking-to-access mappings; Reviews administrative activity; Uses evidence packages in your authorization
  • Cannot: Edit or delete audit records; Approve their own change requests
  • Approvals: Approves security-relevant changes; their own requests need a second designated approver.
  • Notified about: Security-relevant changes, possible spillage reports and incidents.

Oversight reviewer (read-only)

Intelligence oversight officer, inspector general staff, internal auditor. Reviews lineage, decisions and changes without being able to change anything.

  • Sees: Source authorizations and descriptions; Steward and classifier decisions; Lineage and change records within the scope granted
  • Does: Reads records within the scope granted; Exports evidence, with each export logged; Records review notes where enabled
  • Cannot: Change, approve or delete anything
  • Approvals: Their access is approved by the data owner or ISSM with a scope and an end date.
  • Notified about: Nothing by default; access granted and expiring is confirmed to the approver.

Permissions at a glance

ActionData ownerStewardClassifierAnalystMoraph engISSMOversight
Request and authorize a sourceOwn work––––ViewView
Approve data model mappingApprovesView–––––
Approve quality rulesApprovesFull–––––
Decide on quality holdsViewFull––––View
Decide on marking holds––Full––ViewView
Build and deploy pipeline changesApproves–––Full––
Change marking-to-access mappings––––FullApproves–
View record lineageOwn workFullFullOwn workFullViewView
Report a data issueFullFullFullFullFull––
View audit trailView–––ViewViewView
Manage users and roles––––FullApproves–

"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.

How access is controlled

  • Duties are separated: data engineers build and run pipelines, data stewards decide on quality, trained classifiers decide on markings, and no one approves their own change.
  • Roles are scoped by source and by clearance, so people see only the sources and held records they are entitled to.
  • Suggested corrections are only suggestions. Every override, marking decision and rejection is made and recorded by a named person.
  • Moraph's accounts are named and role-based.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.