User's who are evaluating DSP and OpenTDF need help to understand how the system works and what their role will be when administrating the platform.
Non-fed scenario context:
medical
Dependencies
Create new CLI command
Scaffold basic TUI interface
...
Demo scenarios
Starting up OpenTDF (booting the services, using the CLI)
Experience Control (adding attributes, encrypting, decrypting, removing attributes, test)
Add an attribute
Entitle someone with the attribute
Try decrypting data
Inspect policy (see what the data looks like and who would have access)
Inspect entity (see what the entity would have access to)
Visibility (execute small scenarios and see audit change)
Simulate sharing with another entity
User A creates data
User A sends data via email to User B
User B does not have access and responds to email
User A makes request with Admin
Admin grants User B with attributes
Admin let's User A know
User A let's User B know
...
Feedback
@astanley1 - has used some "learn to code" websites and finds the demo and live experience very helpful
@suchak1 - feels that it will be helpful and having self-contained documentation would be very useful. Recommends having tests to ensure the demo doesn't break.
@jakedoublev - finds it "pretty sweet" but wants more clarity about where each CLI will live
Description
User's who are evaluating DSP and OpenTDF need help to understand how the system works and what their role will be when administrating the platform.
Non-fed scenario context:
Dependencies
Feedback
@astanley1 - has used some "learn to code" websites and finds the demo and live experience very helpful
@suchak1 - feels that it will be helpful and having self-contained documentation would be very useful. Recommends having tests to ensure the demo doesn't break.
@jakedoublev - finds it "pretty sweet" but wants more clarity about where each CLI will live