nextcloud / nextcloud/circles

Allow transparent membership/ownership

Open
#1,984 0 comments 0 reactions 1 assignee View on GitHub

@nfebe is already working on this.

Since Jun 6, 2025.

🍂 2025-Autumn 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.

Feature request

In Talk we can add teams to conversations since a long time.
Recently mentions of teams were added.

Now the problem is that I as a team lead own all the sub-teams we have:

  • Talk Backenders
  • Talk Frontenders
  • Talk Mobile
  • Talk Design
  • Talk Team

However that makes me currently a "member" of said teams and if someone pings the "Talk Mobile" devs I still receive a notification and blue unread marker, even though it's not my expertise.

It would be helpful if people owning/moderating/managing a team could either define for the team if "managers" are also "members" or each manager themselves decides if they are a "member" or whether their membership should be "transparent".

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.