Your developer user name (your individual publisher).In the top right-hand corner of the Chrome Web Store developer console is a pull-down that contains the following items: In this case you are not a direct member of Group B, and cannot publish using that group. Group A is a member of Group B, which is a group publisher.Group publishing does not recognize "indirect" membership of Google Groups: only explicit members of a group can publish.
Only the group owner or manager (or the last remaining group member) can delete the group publisher, unlinking the Google Group from the Chrome Web Store. Once the group publisher account is created, the Google Group you select remains linked to that account. You cannot replenish this quota, even if you delete the group. It avoids unintended deletion of items that can happen when a developer leaves the org (because their account gets deleted and that individual account was the item's publisher).Ī Chrome Web Store developer account can only create one group publisher, ever.It's easy to transfer ownership of items when a developer leaves the organization.It's a convenient way for teams to share the publishing capability among all their members.Group publishers provide a number of benefits for organizations and development teams: Any Chrome Web Store developer who belongs to the group can publish updates to the item, as depicted in the following diagram: Group publisher By setting up a group publisher, you use a Google Group to associate multiple developers into a composite entity. The following diagram describes this scenario: Individual publisher When an individual developer acts as a publisher of an item, only that developer can upload and publish updates to the item. When you register as a Chrome Web Store developer, your developer account is automatically enrolled as an individual publisher.
0 kommentar(er)
