Actions57
- 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
- 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 Rights on a Project
- Update a User's Rights on a Project
- Team Actions
- Task Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to manage projects and their users. Specifically, the "Update a User's Rights on a Project" operation allows you to modify the permissions or roles of a user within a given project. This is useful in scenarios where you need to dynamically adjust user access levels based on changing team structures or project requirements.
Practical examples include:
- Promoting a user from a viewer to an editor role on a project.
- Restricting a user's access by downgrading their rights.
- Automating user permission updates when onboarding or offboarding team members.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. You can select a project from a searchable list or specify its ID directly. |
| User ID | The numeric identifier of the user whose rights you want to update on the selected project. |
Output
The node outputs JSON data representing the updated state of the user’s rights on the project after the operation completes. This typically includes confirmation of the changes made, such as the user's new role or permissions within the project.
If the node supports binary data output (not evident from the provided code), it would represent any file or media content returned by the API, but this operation primarily deals with JSON responses.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- Network access to the Vikunja server hosting the API.
Troubleshooting
Common Issues:
- Invalid or missing project ID: Ensure the project exists and the ID or selection is correct.
- Incorrect user ID: Verify that the user ID corresponds to a valid user in the system.
- Insufficient permissions: The API key used must have rights to update user permissions on the project.
- Network or authentication errors: Check API URL configuration and credential validity.
Error Messages:
- "Project not found": The specified project does not exist or is inaccessible.
- "User not found": The user ID does not correspond to any user in the project.
- "Unauthorized" or "Forbidden": The API key lacks necessary permissions; verify credentials and roles.
Resolving these usually involves verifying input parameters, ensuring proper API credentials, and confirming network connectivity.