Admin Project

This is the issue that tracks the progress of the development of the admin side of Graasp.

## Definition

The Graasp admin is a series of API routes and pages that allows super users (graasp developers and team members) to investigate and take action on behalf or registered users for tasks related to the well working of the platform.

## Development

- working authentication different than the regular authentication

## Features

### Publication management

Allow to un-publish content that should not be published (infringes in personal data, inapropriate content, violation of licenses DMCA et ...)
Should notify the user responsible for the publication ?
Should we provide a reason why the publication was removed ? the admin should be aware that what they provide as a reason will be visible to the user. They should be considerate of that (should not say "bad content" as it does not provide constructive input).

Provide options for sending more info in the email if necessary.

Should we provide already categorized by most common reasons faced for de-publication.

### Failed content validation

When a user wants to publish some content in the library they may hit a content validation error.
These might be false positives and we would like to bypass the check and still authorize the publication.

We need a way to see the infringing content as well as potentially its surrounding.
Admins should be able to see the content that wants to be published.

We need a way to access the content as an admin to proof that it is correct.
This could be done by an "log as user" mechanism where the admin can be given a short lived session cookie as the creator of the publication.
Otherwise we could specifically for the need of this feature we could ensure that it is available publicly so admins can browse the collections freely. This is however maybe not desirable.

### Management of highlighted collections

Currently we expose collections published by a specific user (Graasper) as the featured collections.

We would like to be able to mark interesting collections as "featured" so they can be retrieved from multiple publishers (users).

### Monitoring recently published elements

As admins we want to ensure that the quality of publications stays consistent and that published elements follow our standards.

We need a way to explore recently published content.
This could be done in a page that is accessible to all users of the library under the `/recent` path.
or it could be done with a specific view only in the admin.

### Member management
- change member storage

### Application management

We allow apps developed by third parties to access the apps api.
For this we need to register them in the database with a key that we communicate to the application developer.
We need to:
- add new apps
- remove old apps
- create new publishers
- rotate application keys
- update application properties (name, image, description, url, publisher association)

### Member lookup for user support

Provide a page that allows support staff to lookup members based on partial email matching, id lookup, partial name matching.

### Provide user support via "log in as user"

Users that are facing an issue can request support. They have a button in their account where they tell us about the issue they are facing. The admin can see users that have requested support and what the issue might be. They have a button they can press to get a "log as user" to view the interface as the user and debug from their perspective.

### Notification system

Allow to send system emails to users to inform them of issues, or planned maintenance, new features, or surveys.

Notify users of an item specifically ?

### Manage reported items

See and examine items that have been reported by users.

### Platform-wide Analytics

As administrators of the platform we need to understand and monitor metrics related to the platform.

By defining goals we elaborate metrics that evaluate goal completion.

Platform growth:
- user acquisition: see user creation metrics and evolution accross time
- users invited by other users
- users registering via a referal link
- user retention: see returning users
- content being worked on: see active content, update, actively maintained

View analytics of the platform regarding:
- users
- memberships
- types of item
- storage capacity
- feature usage
- active users