[FEATURE] Revamping Assistant Creation: User-Centric Design and Enhanced Sharing Capabilities

[enricobellato]

🔖 Describe the Feature

The process of creating new assistants is being moved from the admin section to the user section of the application. This change will democratize assistant creation, allowing three distinct user roles to create assistants:

• Normal users without extra permissions can create an assistant for their personal use, without the ability to share it with others (neither in workspaces nor organization-wide).
• Users with one or more Workspace Admin roles can create an assistant and share it with users within their specific workspace. This sharing is exclusive; for example, an admin of Workspace A can only share with Workspace A users. These users also retain the abilities of a normal user, including creating personal assistants.
• The Super Admin (current installation admin) can create assistants and share them organization-wide. This role is ideal for creating assistants of broad interest (e.g., HR assistants) without needing to create a catch-all workspace. It also covers standard assistants (like GPT-4 basic assistant, clause basic assistant) configured during the application's deployment.
• The redesign of the assistant creation tool will align with the principles defined in issue #18, featuring a tabbed design to enhance the user experience during assistant creation.

Additionally, a new draft and publish mode will be introduced (as suggested by @protoism in issue #34), allowing users to draft an assistant and publish it to the desired space (personal, a specific workspace, or the entire organization) only when it is ready. This feature builds on the existing test assistant functionality, which enables testing without leaving the assistant creation page.

The assistant creation page will be designed without a sidebar to maximize the usable space for creating and testing assistants.

🎤 Justification for the Feature

This enhancement is driven by the need to make assistant creation more accessible and flexible for users at different levels of the organization. By enabling users with various roles to create and share assistants, we foster a more collaborative and efficient environment. The introduction of draft and publish modes further supports this goal by allowing for thorough testing and refinement before sharing, ensuring the quality and relevance of assistants shared within the organization.

✌️ Proposed Solution

Relocate the assistant creation feature from the admin section to the user section, making it accessible to a broader range of users.

• Implement role-based assistant creation and sharing capabilities:
  • Normal users can create personal assistants.
  • Workspace Admins can create assistants for their workspace.
  • Super Admins can create organization-wide assistants.
• Integrate the redesign principles from issue #18 to improve the assistant creation UX.
• Introduce a draft and publish mode for creating and refining assistants before sharing.
• Design the new assistant creation page without a sidebar to optimize space for creation and testing activities.

🔄️ Considered Alternatives

No response

👀 Duplicate Check

• [X] I have searched and found no similar feature request

🏢 Code of Conduct Acknowledgement

• [X] I have read the Contributing Guidelines

[protoism]

Not everything is clear, but... a bit of brainstorming led to these rules:

• Sharing of an assistant is managed only by the Assistant owner, to avoid lack of confidence in privacy
• Assistant owner can manage sharing to workspace only if he is admin/owner of that workspace
• Assistant owner can manage sharing to all only if it is the organization admin

[protoism]

While there's no complete overlap with #63, we're fine for now. Draft mode moved to another ticket, as possibly not necessary for 0.2.0