Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

Expected result:

(maybe it only works for 100) - Not worrying about consistency (i.e. Consistency between MFs internal DBs i.e RBAC, Inventory and SpiceDB)

Acceptance Criteria 

• Uses a mature API (on Kessel side)
  • We do not believe it will require breaking changes
• Go through HBI (vs direct to Kessel)
  • Stretch: use HBI UI
• Solves org-level access (staleness)
• Covers HBI workspace access usecases (see comments)

TODO

• Work with HBI to harden access and resource schema
• Review Kessel Check Service and Kessel Resource Service to reconcile naming, concepts etc between the APIs to present a uniform Management Fabric API
• Talk about generated names with effective permission application patterns

Checklist

Open Questions

Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed.