Allow to control permission that can promote prompt to production level.

[takryo00]

Describe the feature or potential improvement

Currently we don't have fine-grained permission to promote prompt to production.
The ability to ensure that to promote prompt to production should not occur until the approval flow is completed is required for operation in production.

Additional information

No response

[sfarthin]

Additionally, implementing a mechanism that requires users to submit relevant prompt experiments before deployment would be highly beneficial. This process would serve as an audit log, offering traceability and transparency similar to how Pull Requests manage software changes. Moreover, akin to Continuous Integration, it would provide proof of confidence that any changes are likely to improve outcomes, ensuring they are both measured and data-driven. This approach not only enhances the approval workflow, but also creates a structured record for future reference and development.

[sezf-tradify]

Yes it would be useful if:

• admins can enable/disable if approvals are required for a project
• if approvals are disabled; current behaviour is honoured
• if enabled; users who can edit a prompt can only request a prompt version is promoted to production
• if enabled, a user with an approval permission is required to approve the requested change.

[marcklingen]

thanks for sharing! approvals/workflows related to prompts have been on the roadmap for a while already and demand for this increases a lot recently, will try to get to this soon