-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Code: 403 when creating a new task #639
Comments
@edrdos101 |
@edrdos101 , your user doesn't have enough privileges to create a task. Please read our documentation. You need to assign additional rights. The question was discussed many times on our gitter channel. I will close the issue for now. We definitely need better messages about errors but it is a separate issue. |
For anyone else encountering this problem - the fix is really easy, but it's not stated anywhere in the "User Guide" (as of February 24th 2021). Only a user assigned an admin role in the Django administration panel can create new tasks. Log in as a superuser and assign it properly. Hope that helps :) |
It is not exactly true. CVAT has different user groups: admins, users, annotators, observers. |
Thank you for a very quick reply, Boris! I am just starting with CVAT |
I'm using CVAT online tool, I created a project for my organization, But it is showing a warning message that you can add a project, you want permission. actually, where do I find this permission access to allow. Are there any other methods to add projects to organization? Note: I use admin account and im on the one user for this account. |
@shajahanpc , if you are using cvat.org, you can have only "user" permissions. Users can create 3 projects and 10 tasks on the public instance (see the scope https://github.com/openvinotoolkit/cvat/blob/develop/cvat/apps/iam/rules/projects.csv There are two possible options:
|
I am encountering the following error when trying to create a new task with a shared volume:
Code: 403. Message: {"detail":"You do not have permission to perform this action."}
Couldn't find any mentions of this error in the issues, any advice would be much appreciated
Thanks!
The text was updated successfully, but these errors were encountered: