keybase / keybase/keybase-issues

Have a "Organization" type for businesses

Open
#3,369 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Instead of creating an organization user that would then create teams, maybe have organizations overall so that all company sub teams would fall under them.

Overall this could be done with having one Org user that then creates the teams but I think the naming convention would be better if you could create an overarching organization, similar to slack channels.

This could provide restrictions for users accounts that would limit them from reaching out or messaging others that are not from the Org from their account.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Begin by clarifying the proposed organization model, its relationship to users and teams, and the intended messaging restrictions. Done would require an agreed design and corresponding behavior for organization membership and communication access.

Written by the indexing model from the issue text.

Assessment

Domain
authorization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.