OpenFn / OpenFn/lightning

Allow editing collaborator roles & permissions after they are added

Open
#3,603 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature enhancement
Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

Is your feature request related to a problem? Please describe.

Right now, once a collaborator is added to a project, their role and permissions cannot be changed. If you assign the wrong role by mistake or if responsibilities shift later, the only workaround is to remove and re-add the collaborator. This is disruptive and makes managing project access more difficult.

Tell us about your idea - describe the solution you'd like.

I’d like to have the ability to update a collaborator’s role directly from the project settings. For example, an “Edit” option in the collaborator list where an Admin can change a user from Admin → Viewer → Editor without needing to remove and re-invite them.

Additional context

The last time I faced this issue was when a collaborator needed Admin rights during setup but only needed Viewer access later. I had to remove and re-add them, which was inconvenient. This happens often whenever team responsibilities change. Being able to update roles directly would save time, reduce errors, and make collaboration smoother.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the project settings collaborator list and trace the existing add, remove, role, and permission flows. Identify where Admin users are authorized to manage collaborators and how role changes are represented. Done means an Admin can edit an existing collaborator’s role without removing or re-inviting them, with the resulting permissions applied correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
authorization
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.