Opt-IN Opt-out feature for TexEra

[Sarvesh-CSE]

I was wondering if say an organization O is using the platform. Running any application generates logs at the TexEra end. O wants to continue using the platform, but they do not want the metadata (logs generated at the TexEra end) to be used for any further aggregate analytics or any other application, for that matter. So, I see this as providing the end user a capability to own the metadata while using TexEra. They may even say that use my logs for certain kind of analytics only.

[kz930]

I think this is a great idea! We could potentially add a few features to support this:

1. Metadata ownership and access: Allow organizations to view, download, and manage the execution logs generated by their workflows.
2. Opt-in/Opt-out controls: Let organizations decide whether their logs can be used for aggregate analytics or other purposes.
3. Fine-grained permissions: Allow organizations to specify which types of analytics their logs can be used for, such as performance optimization but not usage analytics.

We could start with basic opt-in/opt-out controls and gradually expand to more fine-grained permissions.

[chenlica]

@Sarvesh-CSE Thanks for sharing this interesting idea. We can keep this one on the roadmap. If many organizers want this feature, we can implement it.