nextcloud / nextcloud/circles

expose roles of team member to apps

Open
#2,777 0 comments 0 reactions 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.

Feature request

Expose the role of a team member to apps when loading information about the team.

Use case

There are different roles in a team that works together on a task. Ideally, these can be reflected in Teams and access to the resources it owns.

Right now, Teams has the roles owner, admin, moderator and member. We want to add a 'guest' role in the future.

We should allow apps to map these, for example:

  • Only owners and admins can manage ACL's in Teamfolders
  • Only owners and admins can create new Talk rooms for the team
  • Moderator role and up are managers of all Deck boards
  • Moderator role and up are moderator of all team-owned Talk rooms
  • Moderator role and up can modify permission of Deck boards
  • Guests can not edit anything in Deck boards and Collectives

For this, apps would need to know about the role of a member. So the API where apps can query information about membership of a team should be extended to also allow informing the app about the role of that team member.

This should be implemented under the assumption that roles in Teams can be expanded in the future, adding more roles, and perhaps even support the creation of custom roles.

For now, apps can act on the roles as defined (owner/admin/moderator/member) and implement some sane mapping of behavior.

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 locating the API endpoint or entry point where apps query team membership information and review how current roles—owner, admin, moderator, and member—are represented. Define the API response and extension approach so apps can identify the current role and future roles without breaking existing consumers, then verify the membership information exposes the required role data.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.