[UX] Replace raw Dataflow scope IDs with governed target selectors #13

Open
opened 2026-07-29 02:29:32 +02:00 by zemion · 0 comments
Owner

Problem

Dataflow definition settings and the scoped-copy dialog require a raw Scope ID for group/user ownership.

Work

  • Replace both raw fields with readable user/group selectors.
  • User targets must persist the account ID expected by Dataflow resolution, not a tenant membership ID.
  • Group targets must be limited to the active tenant and the actor's permitted ownership scope.
  • Use an optional Access directory provider without importing Access implementation code.
  • Show unavailable historical targets readably and prevent new assignments to inactive targets.
  • Keep system/tenant targets implicit.

Acceptance criteria

Both Dataflow scope entry points can be completed without knowing an internal ID, while API payloads retain stable IDs.

Parent: GovOPlaN/govoplan-core#272

## Problem Dataflow definition settings and the scoped-copy dialog require a raw Scope ID for group/user ownership. ## Work - Replace both raw fields with readable user/group selectors. - User targets must persist the account ID expected by Dataflow resolution, not a tenant membership ID. - Group targets must be limited to the active tenant and the actor's permitted ownership scope. - Use an optional Access directory provider without importing Access implementation code. - Show unavailable historical targets readably and prevent new assignments to inactive targets. - Keep system/tenant targets implicit. ## Acceptance criteria Both Dataflow scope entry points can be completed without knowing an internal ID, while API payloads retain stable IDs. Parent: https://git.add-ideas.de/GovOPlaN/govoplan-core/issues/272
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-dataflow#13
No description provided.