Provinite / Provinite/chardb

Create audit log for item grants

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
2h 52m
Merged PRs (30d)
85

Description

Problem

Currently, there is no audit trail for when items are granted to users. This makes it difficult to:

  • Track administrative actions
  • Investigate inventory discrepancies
  • Provide accountability for moderators/admins
  • Debug issues with item grants
  • Maintain historical records

Proposed Solution

Implement an audit log system that tracks item grant events with the following information:

  • Granter: Who granted the item (user/admin ID)
  • Recipient: Who received the item (user ID)
  • Item: What item was granted (item ID, name)
  • Quantity: How many were granted
  • Timestamp: When the grant occurred
  • Community: Which community context (if applicable)
  • Reason: Optional reason for the grant

Use Cases

  1. Audit Trail: Admins can review who granted items and when
  2. Accountability: Track moderator/admin actions
  3. Investigation: Look into suspicious inventory changes
  4. Transparency: Users can see their item grant history
  5. Debugging: Troubleshoot inventory issues

Technical Considerations

  • Should this be a new database table/entity?
  • Should it be accessible via GraphQL query?
  • Who should have permission to view audit logs?
  • Should we audit other inventory operations (transfers, deletions, etc.)?
  • How long should we retain audit logs?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the existing item-grant flow and its persistence and API layers, then clarify the table or entity, GraphQL access, permissions, scope of audited operations, and retention policy. Done cannot be defined until those design questions are resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend, database, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.