Running on Galaxy Legacy? Visit the legacy docs.
Galaxy

Organizations

Collaborate with your team on Galaxy. Create shared workspaces, add developers, assign roles, and manage apps together without sharing login credentials.

What Are Organizations?

Want to collaborate on Galaxy? You need an organization.

Organizations let multiple developers deploy, scale, and monitor apps together. Think of them as shared workspaces where your team can access the same resources without sharing login credentials.

Here's the key thing: you always log in as yourself. Organizations don't have passwords. Each team member uses their own Galaxy account, and organizations group those individual accounts together.

Why this matters:

  • Each person keeps their own credentials secure
  • You can track who did what
  • Removing someone doesn't affect others
  • Security settings (like 2FA) are per-person, not shared

Creating an Organization

Ready to set up a team workspace? Here's how.

Open the Account Switcher

Click the account dropdown at the top left of the dashboard. You'll see your personal account listed, plus any organizations you're already part of.

Create New Organization

Click "New Organization" at the bottom of the dropdown menu. Enter a name for your organization.

Choose carefully. Organization names are locked once created. Can't change them later.

Set Up Billing

Each organization has its own billing. Go to the Billing section and add a payment method for your new organization.

Organization charges are completely separate from your personal account billing.

Add Your Team

Head to the Members section and start inviting collaborators. They'll need their own Galaxy accounts first.

See the Members Menu guide for details on adding team members and assigning roles.

Organization names are permanent. Pick something you won't regret, like your company name or project codename.


Switching Between Accounts

Use the account switcher at the top left of the dashboard to move between your personal account and organizations.

Your dashboard view changes depending on what you select. When viewing an organization, you see that organization's apps, databases, billing, and members. Switch back to your personal account and you see your individual resources.

Not seeing the resources you expected? Check which account is selected in the switcher. Apps and databases belong to specific accounts, and you only see what belongs to the currently selected one.


Organization vs Personal Account

What's the difference?

Personal accounts are for individual developers. Apps and databases here are yours alone. Great for personal projects, learning, or solo work.

Organizations are for teams. Multiple people share access to the same apps and databases. Everyone uses their own login, but resources are collectively managed.

You can have both. Keep personal experiments in your individual account and move team projects to an organization.


Roles and Access

Organizations use role-based access control. Every member holds one of four roles, and that role decides what they can do across the organization's apps, databases, and settings.

Owner: Full access. The only role that can transfer ownership. Each organization has exactly one owner: the creator, until ownership is handed off.

Admin: Full access to resources, plus member management. Admins can invite members, remove members, and change member roles.

Developer: Full access to resources. Developers can invite and remove members, but can't change anyone's role.

Viewer: Read-only access. Viewers can't create apps or databases, deploy, scale containers, edit environment variables or Meteor settings, or open deployment history and details.

New members always start as Viewer, the most limited role. An owner or admin promotes them from the Members Menu.

Only Owners and Admins Change Roles

Developers can add and remove members, but only owners and admins can change what role a member holds. To make someone the owner, use Transfer Ownership in Organization Settings.

Billing sits outside the role system. Whether members can see payment methods and invoices depends on the organization's Billing Management setting, which only the owner controls. Configure it in the Settings Menu.

Roles Apply to the Whole Organization

Roles aren't scoped to individual apps. A Developer has the same access to every app and database in the organization. If you need hard separation between projects, use separate organizations.


Deploying to Organizations

When you deploy an app, Galaxy needs to know which account should own it.

Push to Deploy: Select your organization in the account switcher before starting the deployment flow. The app deploys to whatever account is currently selected.

CLI deployment: Use the --owner flag to specify the organization. See the Meteor CLI deployment guide for details and examples.

Deploying Needs Developer or Higher

Viewers can't deploy. Make sure the person shipping has at least the Developer role in the organization.


Transferring Apps

Have a Meteor app on your personal account that the team needs? You can transfer it using the meteor authorized command from the CLI.

See the Transfer a Meteor App guide for the full walkthrough. For non-Meteor apps, contact support.


Organization Billing

Each organization has completely separate billing from your personal account.

  • Own payment method
  • Own invoices
  • Own usage tracking

Charges for organization resources never appear on personal account bills. Make sure to set up billing for each organization you create.


Closing an Organization

Need to shut things down?

Pause without closing: Just stop all apps and databases. Galaxy doesn't charge for inactive resources. The organization stays available if you want to restart later.

Close permanently: Contact support. They'll walk you through closing the organization entirely. All apps, databases, and member associations are deleted.

Closing is permanent. Export any data you need first. Let team members know they'll lose access.


Common Questions


What's Next?