Actions57
- Team Actions
- Webhook Actions
- 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
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 project access control needs to be adjusted dynamically, such as granting additional rights to a team member or restricting access after role changes.
Practical examples:
- Updating a user's role from "viewer" to "editor" on a project.
- Revoking certain permissions for a user who no longer requires full access.
- Automating user rights management 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. This typically includes confirmation of the changes made, such as the user's new role or permission set within the project.
If the node supports binary data output (not evident from the provided code), it would relate to any file or attachment data associated with the project or user rights update, but this is not indicated here.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- Uses the Vikunja REST API endpoints to perform operations on projects and users.
Troubleshooting
Common issues:
- Invalid or missing project ID: Ensure the project exists and the ID is correct.
- Incorrect user ID: Verify the user ID corresponds to a valid user in the system.
- Insufficient permissions: The API key used must have rights to modify user roles on the project.
- Network or connectivity problems with the Vikunja server.
Error messages:
- Authorization errors usually indicate invalid or insufficient API credentials.
- "Project not found" errors suggest the specified project ID does not exist.
- Validation errors may occur if required fields are missing or malformed.
To resolve these, double-check input values, ensure proper API credentials, and verify network connectivity.