Organizations
Learn how organizations work in OpenLib, how teams submit apps together, and how organization roles affect app ownership.
Organizations let multiple people manage apps under a shared project, community, company, or foundation identity.
Why organizations exist #
Many open-source projects are maintained by teams, not individuals. Organization pages help OpenLib represent that reality.
Organizations can:
- Own app listings.
- Show members.
- Submit apps as a shared identity.
- Display verification state.
- Group related apps under one public profile.
Organization roles #
Organization membership can include roles such as owner, admin, contributor, or member. Exact capabilities depend on the site implementation, but the intent is simple:
| Organization role | Typical responsibility |
|---|---|
| Owner | Controls the organization and transfer decisions |
| Admin | Helps manage members and organization metadata |
| Contributor | Can help submit or manage app listings |
| Member | Publicly associated with the organization |
Submitting as an organization #
When a user belongs to an organization with permission, the Submit App flow can allow them to submit under that organization instead of a personal account.
This is useful when:
- The app belongs to a project team.
- A foundation maintains several apps.
- A company publishes open-source tools.
- Multiple maintainers share responsibility.
Verification #
Verified organizations help users identify official project owners. Verification should rely on evidence such as official website links, repository ownership, domain email, or maintainer confirmation.
Related docs #
Contributors
- OpenLib Team