Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User group #315

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

parniantaghipour
Copy link
Contributor

@parniantaghipour parniantaghipour commented Dec 11, 2024

It has been reviewed by you. I need this to be able to refer to in the other sections

I need to refer to my tools and prompt set description.
Second-round updates

Update user-group.md

updated
@tjbck
Copy link
Contributor

tjbck commented Dec 11, 2024

Please address all the comments, not just the ones you want to.

2. **User**: Standard users with permissions defined by the group settings.
3. **Admin**: Users with access to all features, models, tools, and other system capabilities.
:::note
Admins can view the chat history of users, including those with pending access.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unless specified with the env var to disable this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which env var?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

look it up.

- **Assign Users to Groups**: Assign users to specific groups.

:::note
For example, to add new tools, users must have **workspace permission** and access to **Tools**. The same applies to managing **Knowledge** and **Prompts**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

weird wording. please rewrite for clarity.

For example, to add new tools, users must have **workspace permission** and access to **Tools**. The same applies to managing **Knowledge** and **Prompts**.
:::
:::info
Members with any access level (Admin, User) have access to use the tools, knowledge, and prompts.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

weird wording here as well, might as well delete this part.

- Define the default permissions for users in the group by navigating to the **Groups** => **Edit User Group** => **Permissions**.
- Use the setting to give access to Workspace sections (Model, Tools, Promps, Knowledge), and Chat Permissions(File Upload, Chat Edit, Chat Delete, Temporary Chat).
:::tip
Admins cannot grant users direct access to Functions, as they are advanced features that can only be managed through the admin panel.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

again with the wording, this can be interpreted in an incorrect way. be more precise here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants