---
# System prepended metadata

title: Untitled

---


Inspiration: https://cloud.google.com/compute/docs/logging/activity-logs

> After each service action, we trigger a creation of an activity log:

```typescript=
'activity-log': {
    id: "hH43nfg4",
    organization_id: "didomi",
    created_at: "2022-02-17",
    actor: "ghH7hwf",
    actor_type: "user",
    action: "create" | "update" | "remove" | "duplicate",
    service: "notices/configs",
    entity_id: "39gh3aa",
    request: {...},
    resource: {...},
    result?: {...},
}
```

Result:
**Christopher Ventura** updated the notice config "**CMP - Testing**" 2 days ago.

> Show a diff of `resource` <> `result|request`


## Technical Notes
- Is request needed?
- Can we only store the affected fields from the og request?

---
Possible solutions:
- Use docker compose to fork the admin API and add the service on top so the frontend can use it locally (How to demo?)
    - Use the admin API for the demo
    - Use a separated service
- Use Didomi Test AWS account to deploy the services there
