Actions60
- Label Actions
- Project Actions
- Add a Team
- Add a User
- Create
- Create a Kanban Bucket
- Create a Link Share
- Create a Project View
- Delete
- Delete a Kanban Bucket
- Delete a Link Share
- Delete a Project View
- Duplicate
- Get
- Get All Link Shares
- Get All Project Views
- Get All Teams
- Get All Users
- Get Many
- Remove a Team From a Project
- Remove a User From a Project
- Update
- Update a Kanban Bucket
- Update a Project View
- Update a Team's Permissions on a Project
- Update a User's Permissions on a Project
- Task Actions
- Team Actions
- Webhook Actions
Project → Update a User's Permissions on a Project
AI-generatedOverview
This node operation updates a user's permissions on a specified project within the Vikunja API. It is useful for managing user access and roles on projects, such as granting or modifying permissions for collaboration or project management purposes.
Use Case Examples
- Updating a team member's access level on a project to allow editing tasks.
- Changing a user's permissions to restrict or expand their capabilities within a project.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | Specifies the project to operate on, either by selecting from a list or providing the project ID. |
| User ID | The ID of the user whose permissions are to be updated on the project. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings. |
Output
JSON
user_id- The ID of the user whose permissions were updated.project- The project on which the user's permissions were updated.
Dependencies
- Vikunja API with an API key credential
Troubleshooting
- Ensure the provided project ID or selected project exists and is accessible.
- Verify the user ID is correct and the user is part of the project or can be added.
- Check API credentials and permissions to ensure the node can update user permissions.
- Timeouts or SSL issues can be resolved by adjusting the request options such as timeout duration or ignoring SSL certificate validation.