<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=479947) </details> <!--IssueSummary end--> ### Problem Currently user's approval given for mapping contributions and memberships to them does not expire. By this, we want to avoid "approval fatigue". However, this approval could expire after some time, so that it needs to be refreshed not too often, but periodically, if needed (if the imports are ongoing). ### Proposed solution User's approval expires after a certain amount of time. Proposed time is a month (30 days). If someone is staging many imports from the same source into the same root namespace over a few weeks, an initial approval would cover this period. This would avoid "approval fatigue". But, a month goes by, and a new import happens (from same source to same root namespace etc) and I would be required to approve again.