Org Owner cannot see projects without team membership
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Customer report: a user with Org Owner access could not see projects in the org UI at all (not just missing issue/telemetry data), and was not a member of the project team.
Per docs, Org Owners have full access to the organization, its data, and settings, and can perform Team Admin actions without joining the team. Team membership is what gates project access for Members.
Verified (docs)
- Org Owners: full access to org data/settings; Team Admin actions without joining the team (membership)
- Members: access projects their teams own
- Projects page copy currently describes listing projects for teams the user is on (projects)
Unknown / needs confirmation
- Whether the user was truly org-level Owner (vs Member / Team Admin / informal “project owner”)
- Whether projects were missing from Projects overview, Settings > Projects, project picker, or all of the above
- Org plan, open membership setting, multi-org/SSO context
- Whether another Owner in the same org could see those projects
Expected
Org Owners should see and open all projects in the org without being added to a project team.
Requested by Colin Kawai via Junior.
--
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Projects overview, Settings > Projects, and the project picker, confirming the user's org role, plan, membership, and whether another Owner sees the projects. Compare the behavior with the organization membership and projects documentation; done means an actual Org Owner can see and open every organization project without joining its team.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 40/100