You are here: Building with agents › The kits › Privacy.HumanRequests
Summary#
Osysharp.Privacy.HumanRequests makes the requests put to a person — and the ones the app marks as about them — part of what they can see, have kept out of use, or have erased.
An erasure leaves the request and takes the person: who it was put to, what they were shown, what it was about, and their answer are blanked; that a request was put, what kind of thing it asked, when and how it ended stay — the asker's own record. A request still waiting for their answer holds the erasure until it is answered, called off or runs out.
| Package | Osysharp.Privacy.HumanRequests, version 1.1.0 |
| You add it with | Nothing. It arrives by itself in an app that uses [[agent-kit-privacy|Privacy]] and [[agent-kit-human-requests|HumanRequests]]; osy lock says so. without Osysharp.Privacy.HumanRequests; in the manifest keeps it out. |
| It sits on | [[agent-kit-human-requests|HumanRequests]], [[agent-kit-privacy|Privacy]] |
| It also uses | Identity — parts of the platform's own library |
| Its own test app | A marina that asks its berth holders and an outside surveyor things, and answers their privacy requests — kits/privacy-human-requests/tests |
Description#
What do you get without writing anything?#
- Every request put to a person in their copy of their data, by their account or by the address its link went to.
- A run that told the request is told again without them.
- Requests purged after the app's period, leaving out what a legal hold covers.
- Nobody erases a request by hand: only a privacy request's own run does.
When do you need it?#
Privacy and HumanRequests together. It arrives by itself. You write one line for a request about somebody put to somebody else: MarkAbout.
What does it expose?#
The tables below are generated from the kit itself, not written by hand: osy kits Osysharp.Privacy.HumanRequests --surface lists each of
them with the code of the kit's own test app that uses it, and the tests that show it working.
Settings — one line in the app, each field with a default.
| You write | It says |
|---|---|
app.RequestsPrivacy = new RequestsPrivacySetup { KeepMonths } | How long this app keeps who a request was put to and what they answered, after it closed. |
Functions you call, those its own tests show most first.
| Function | What it does | Tests that show it |
|---|---|---|
AskedRowKind() | What a mark on a request is called (MarkAbout(request.Id, AskedRowKind(), subject)). | 4 |
What to read next#
- Osysharp.Privacy — what the app holds about a person, and what their request does to it — what the app holds about a person, and what their request does to it
- Osysharp.HumanRequests — something put to a person, and their answer coming back — something put to a person, and their answer coming back
- Osysharp.Privacy.Agents.HumanRequests — who handed an inbox item to an agent, under that person's request — who handed an inbox item to an agent, under that person's request
Go deeper#
- The Privacy kit — erasure that keeps only what the company must or may — the Privacy kit: holders, requests, plans, periods
- Requests to people — a question, an approval, a form, and the answer coming back (HumanRequests kit) — requests to people