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 update a team's access rights on a specific project. It allows users to modify the permission level that a team has for a given project, such as setting read-only access, read & write access, or admin privileges. This is useful in collaborative environments where project access needs to be managed dynamically, for example, granting a marketing team read-only access to a project while giving the development team full admin rights.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to update. Can be selected from a searchable list of projects or specified by its ID. |
| Team ID | The team whose rights on the project will be updated. Can be selected from a searchable list of teams or specified by its ID. |
| Right | The permission level to assign to the team on the project. Options are: Read Only, Read & Write, Admin. |
Output
The node outputs JSON data representing the result of the update operation on the team's rights for the project. This typically includes confirmation of the updated rights and possibly the updated team-project association details. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Uses HTTP requests to interact with the Vikunja REST API endpoints related to projects and teams.
Troubleshooting
Common Issues:
- Invalid project or team ID: Ensure the IDs provided exist and are accessible with the current API credentials.
- Insufficient permissions: The API key used must have rights to modify team permissions on projects.
- Network or connectivity issues: Verify the Vikunja API URL and network access.
Error Messages:
- "Project not found" or "Team not found": Check that the selected project and team exist.
- "Unauthorized" or "Forbidden": Confirm the API key has sufficient permissions.
- "Invalid right value": Make sure the right property is set to one of the allowed options (0, 1, 2).