Enable audit by configuration
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
This feature allows to enable audit of actions for app circles.
The motivation for this change is documented in forum.
It's a feature configurable. It doesn't change current behaviour, only adds audit of actions. It can be desirable feature for customers that want to have an wide control of user actions.
The following actions are audited:
- user X creates circle Z;
- user X removes circle Z;
- user X changes name of circle Z to circle W;
- member X is added to circle Y by user Z;
- member X is removed from circle Y by user Z;
- user X shares fiel/folder with circle Y;
7a. user X, that created circle Y, unshares file/folder with circle Y;
7b. user Z,that is member of circle Y, unshares file/folder with circle Y.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the seven actions listed in the issue and read the linked forum discussion for the motivation and expected audit scope. Done means audit can be enabled by configuration, covers each listed circle and sharing action, and leaves current behavior unchanged by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100