You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 24, 2021. It is now read-only.
Moving this issue over from meteor/meteor#3850. I'm not sure if this should be documented in the Guide (maybe under Writing Atmosphere Packages) or in the API Docs, but I'll assume the Guide for now. One of the best references I've seen for Meteor developer organization information is the Meteor 0.9.1: Meteor developer organizations, solidified Blaze APIs blog post.
(originally reported by @rgoomar)
I have not seen anything in the docs mentioning organizations and how to manage them.
It is an important part of the package system (IMO) and should be documented so that it can more easily be utilized.
There should probably be something in the meteor admin section, writing packages because I did not see how to manage organizations. But, I did end up finding it under meteor.com/account-settings/organizations
The text was updated successfully, but these errors were encountered: