Source owner
You own a source system, and you are the only person who may decide whether a data product can read from it. You cannot answer for any other system, and you cannot answer a request that you sent.
What you decide
- Sign your section of the data contract v0.1 for the system you own: Granted, With conditions, or Refused. A yes or conditional yes closes the approval to load gate.
- Approve or reject the access request that follows a granted or conditional demand.
- Nothing for a system you are not registered against.
rbac.owns_systemchecks the system named on the demand against the system on your row on Users — holding the role is not the same as owning the data. - Nothing you asked for yourself. The use case team or the data hub sends the demand; you answer it, never the other way round.
Important
The application's role badge calls this role Source System. This guide, and the rest of the documentation, calls the person doing it the source owner — the decision belongs to a person, not to a system.
Where you work
- the Data contract v0.1 step, on the product's Source phase page
(
/p/<product>/phase/source#demand) — your section and its answer form - Data contract v0.1 (
/p/<product>/demands) — the whole v0.1, every section and every version of it, with the same answers - Access requests (
/p/<product>/access) — the ticket that follows the demand
Step by step
1. Read your section. Open the one addressed to you — Read it from the step, or its section on Data contract v0.1. It states which tables, why, how often, what the product will rely on being true, and — separately, where any is asked for — the personal data involved.
2. Decide. Granted, With conditions, or Refused. A conditional yes is refused without its Conditions written down — "A conditional yes needs its conditions written down, or it is just a yes." A note is optional either way.
3. Answer the ticket too. If granted or conditional, approve the matching entry on Access requests as well — the demand and the ticket are two separate decisions. A refusal needs no ticket: the step stays open, and the record keeps your refusal by name.
4. Expect a new version, not a resend. A sent document cannot be re-sent. If something about the ask changes, you will see a fresh draft or an upload to answer in its place; only the latest version per system counts.
5. Record feedback, if you want it kept. Record feedback from the owner keeps what you said back, outside the formal decision, on the document itself.
What the record keeps about you
Every answer you give — granted, conditional or refused, with any conditions — and every access request you approve or reject, each with your name and when. If you are signed in as whoever sent the request, the decision is refused: "sent this request, so they cannot also answer it." A Simulate the owner's answer (demo) control exists for walking the process without you; it is marked simulated, and promotion is refused until your real decision replaces it. See Audit events.