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
- Task Actions
- Team 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 access levels for team members based on changing responsibilities or project phases.
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 as part of a workflow 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 generally represent attachments or files related to the project or user, but this is not indicated here.
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.
- The node depends on the Vikunja API being accessible and responsive.
Troubleshooting
Common Issues:
- Invalid or missing project ID: Ensure the project exists and the ID 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 connectivity issues with the Vikunja API endpoint.
Error Messages:
- Authorization errors usually indicate invalid or insufficient API credentials.
- Not found errors suggest the specified project or user does not exist.
- Validation errors may occur if the input parameters are malformed or incomplete.
To resolve these, double-check all IDs, ensure proper API credentials are set up, and verify network connectivity.