-
-
Notifications
You must be signed in to change notification settings - Fork 958
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
Add user to the component #8192
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
This can currently be configured at /admin/, adding to teams UI should not be hard. |
This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this. You can learn about how to get started in our contributors documentation. |
Hi, @nijel I would like to work on this issue. Please assign this to me. |
@prakhar1144 Thanks, I've just assigned you this issue. |
Hi, just wanted to say, I would also love to have an option to add users with higher privileges at component base. It would be great to be able to have one user as admin of one component so they can manage that component. This would help to share workload. |
@Danfro as mentioned before – this is possible using Django admin, Weblate UI is currently missing here. |
@nijel yes, I saw that. The missing weblate UI part I primarily meant, that would be great to have. And may I add, it looks like when using hosted weblate, only an admin for https://hosted.weblate.org/admin/ can enter those settings unless I am missing something. At least for our project, adding "/admin/" at the end does result in a "page not known error". |
This is read-only view just to display the information. Issue #8192
Okay, let's implement this because I've already spent enough time explaining it here... |
Thank you for your report; the issue you have reported has just been fixed.
|
Just tried it for the first time. Works great. Thank you very much @nijel ! |
Describe the issue
Mine is a private project and have created multiple components for the project
Each component is a restricted component
I have hired an external translator agency to provide the translation, hence want to share access to a specific component Frontend component with disabled Automatic suggestion. For that created a Team Translator External
and added the user to the group.
But the user is only able to see the Glossary. Can't find how to grant permission to the restricted component.
I already tried
Steps to reproduce the behavior
No response
Expected behavior
I should be able to grant permission to the specific components while hiding other components in the project from external translators.
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
Powered by Weblate 4.14
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: