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 update a team's access rights on a specific project. It allows users to modify the permission level that a team has within a 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 based on team roles or changes in responsibilities.
Practical examples include:
- Granting a marketing team read-only access to a development project.
- Elevating a QA team's permissions to read & write for testing purposes.
- Assigning admin rights to a project management team to allow full control over the project settings.
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. Selectable from a searchable list of teams or specified by 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 specified project. This typically includes confirmation of the updated rights and possibly the updated team-project association details.
No binary data output is involved.
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 and map projects and teams for selection lists.
Troubleshooting
- Invalid Project or Team ID: If the provided project or team ID does not exist or is incorrect, the API will likely return an error. Verify IDs by using the searchable lists or confirm the IDs directly from the Vikunja interface.
- Insufficient Permissions: The API key used must have sufficient rights to update team permissions on projects. Errors related to authorization indicate the need to check API key scopes or user permissions.
- Network Issues: Connectivity problems with the Vikunja server can cause request failures. Ensure the API URL is correct and accessible.
- Invalid Right Value: The "Right" property must be one of the predefined options (0, 1, 2). Providing other values may cause errors.