App-team panel

[pcrespov]

The PO center will be transitioned into a standalone service accessible via a dedicated subdomain (e.g., admin.myproduct.io). The design objectives are as follows:

1. Enable rapid development iterations, allowing views to move quickly from prototype to deployment. For example, SyR statistics can be easily ported and displayed as panel views.
2. Can be extended independently from the development team
3. Prioritise feature richness over aesthetic design.
4. Ensure independent service deployment, minimizing dependencies to allow for production releases at any time.

### Tasks
- [x] Initial Approach: Create a read-only user in PostgreSQL. This user should be accessible through Adminer, allowing them to execute SQL queries to retrieve data. The extracted data can then be exported to CSV format for further post-processing in Excel or using the oSparc/usage_metrics tools.
- [ ] PO-center enhancements: send invitation email by adding `fogbugz` issue
- [ ] PO-center reports: users registration status
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1402
- [ ] PO-center enhancements: Allow POs to setup annoucements

[pcrespov]

MartinKippenberger Sprint

The App team aims to access specific information on user states within the platform. Initial steps include:

• Establishing a read-only user across all production deployments, allowing the App team (SyR & Javier) to access data from their scripts in the usage_metrics repository.
• A self-developed tool have been discarded. Identifying Grafana and Metabase as potential tools for developing this capability. However, a final tool selection will depend on gathering more concrete information on the specific types of data needed.
  • Monitoring required statistics to guide the next steps and refine access accordingly.