Allow team owners to edit their application roles#6555
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6555 +/- ##
=======================================
Coverage 76.62% 76.62%
=======================================
Files 398 398
Lines 20093 20093
Branches 4836 4836
=======================================
Hits 15397 15397
Misses 4696 4696
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
dimitrieh
reviewed
Jan 22, 2026
Contributor
dimitrieh
left a comment
dimitrieh
left a comment
There was a problem hiding this comment.
@cstns Ideally, we make some adjustments to make this UI less confusing :) See our chat : https://flowfuse.slack.com/archives/D09MYHTTTKR/p1769089990916549
- Extend `roles` object by replacing `none` with 'no access' label. - Replace 'Role' label with 'Access' in team members table. - Enhance dialog text formatting for better user clarity.
Member
|
Failing UI tests appear related |
dimitrieh
approved these changes
Jan 30, 2026
cstns
deleted the
6508_prevent-owners-from-locking-themselves-out-of-applications
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Simplified continuation of #6478 in which we exposed restricted applications to team owners (in the team members area).
Now, while team owners can restrict their access to certain applications they can easily revert that too.
owner-app-lockout.mp4
I took this route because it was the simplest to implement after #6487. I can go ahead with the full restriction for owner to prevent them from assigning themselves and/or other owners an application role of none if needed
Related Issue(s)
closes #6508
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel