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, teams, tasks, labels, and webhooks. Specifically, for the "Update a Team's Rights on a Project" operation, it allows users to modify the access rights of a team within a given project. This is useful in collaborative environments where different teams require varying levels of permissions on projects, such as read-only access for observers or admin rights for managers.
Practical examples include:
- Updating a marketing team's rights to "Read & Write" on a product launch project.
- Changing a development team's access to "Admin" to allow full control over project settings.
- Restricting a support team's access to "Read Only" to monitor progress without making changes.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to update. Can be selected from a searchable list or specified by its ID. |
| Team ID | The team whose rights are being updated. Selectable from a searchable list or by ID. |
| Right | The level of access to assign to the team on the project. Options: Read Only, Read & Write, Admin |
Output
The node outputs JSON data representing the updated team rights on the project. This typically includes confirmation of the updated rights and relevant identifiers (e.g., project ID, team ID). There is no indication that binary data is output by this operation.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential.
- The node expects the base URL of the Vikunja instance to be configured in the credentials.
- Uses internal methods to search for projects and teams to facilitate selection in the UI.
Troubleshooting
Common Issues:
- Invalid project or team ID: Ensure the IDs exist and are accessible with the provided API credentials.
- Insufficient permissions: The API key used must have rights to modify team permissions on the project.
- Network or API endpoint errors: Verify the Vikunja API URL and network connectivity.
Error Messages:
- "Project not found": Check if the project ID or name is correct.
- "Team not found": Verify the team ID or name.
- "Unauthorized": Confirm the API key has sufficient privileges.
- "Invalid right value": Ensure the 'Right' property is set to one of the allowed options (0, 1, 2).