-
Notifications
You must be signed in to change notification settings - Fork 10
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
Use other groupnames #899
Comments
Hi @robake1 👋 Unfortunately, you cannot use groups other than GeneralManager and WorkspacesManagers. The workspace app uses these groups strongly. We have to these groups in your instance. So, please, disable and enable the workspace to recreate these 2 groups. If it helps you, we prepare an import users system for the next major release of the Workspace : #909 |
@dorianne-arawa , can you take account this issue ? |
Hi @robake1 Thank you for your question. An evolution (indicated by @zak39 ) is currently being developed to allow existing local Nextcloud groups or LDAP groups to be connected to a Workspace. However, this will not replace the "U-workspace" and "WM-workspace" groups, which manage the role of each user in a workspace. I don't think it will fully meet your need, if that is to completely replace the "WM-workspace" group with an LDAP group. If you're interested in this point, don't hesitate to contact us via our "www.arawa.fr/contact" contact form. We'll be happy to discuss it in more detail. Have a nice day! |
We want to change the default groups used for Workspace (GeneralManager & WorkspacesManagers) to groups we have in Nextcloud that is created by us (synced in through LDAP).
Is it possible to change the groups ? , when we in the Group Folders admin options set our own groups and remove GeneralManager & WorkspaceManagers we get a HTTP 403 when accesing the Workspace app.
We are using Workspace 3.0.3 on Nextcloud 27.02 and in the process of upgrading to Nextcloud 27.1.1.
The text was updated successfully, but these errors were encountered: