nextcloud / nextcloud/circles

Remove single owner concept from Teams

Open
#2,784 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
177
Forks
68
Avg merge
2d 22h
Merged PRs (30d)
60

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

We should remove the owner concept from Teams.

Problem

When you have a team and its owner leaves the organization, what do you do? Same problem as with other resources - ownership being tied to an individual - which Teams was meant to resolve 🤔

This is an issue for SURF, Dataport and many other larger organizations.

Use case

After creating a team, multiple people should be assigned its highest level of control - Admins, right now, other than owner that is. Having multiple owners is fine, too, but what can the owner do the admin can't?

Proposal

We should simply remove the owner role.

Not in scope

Acceptance criteria

After creating a team, the creator is admin, and can add other members and admins. There is no special role of owner.

Open questions

I can imagine this is technically hard - there might be a need to have an owner. For that, some system user perhaps might suffice, and we otherwise hide this?

Contributor guide

Open the contributing guide

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 by tracing the Team creation, membership, and role/ownership handling paths in the repository. Determine where owner permissions are defined and whether an owner is required internally; done means the creator becomes an admin, admins can add members and other admins, and no special owner role remains, with existing relevant checks still passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authorization, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.