Your orgs

An org owns what you make across GreenMind: games in the publishing console and Game Designer, universes in OnlyLore, bands in Ensemblis. Its admins reach every one of them. This page is about the org pages on your GreenMind account, under Orgs, where an org's people, credits and settings are managed. What an org, a team and a role are across every product is explained in the publishing console's Concepts.

The list of orgs

Orgs lists every org you work in, your default org first. Every account comes with one, its default org, where what you make goes unless you choose another org in the app you are working in. Your default org is an org like any other: name it for your studio and invite more admins.

Making more orgs is for supporters of GreenMind Media, who keep them if their support ends. New org asks for a name, and you are its first admin. Somebody who is not a supporter is shown how to become one instead.

Open an org to see its tabs: Projects, Admins, Teams, Roles, Targets, Billing and Settings, and, for its admins only, Connections and Audit log.

Projects

The org's projects in every product, each with the product it is in and an Open button that takes you to it in its own app. A project is made and changed in its own app; this tab only lists them, and moves them.

Moving a project to another org

An admin of the org who is also an admin of another org can Move a project there. Choose the org it goes to, and before anything is done the dialog says what the move does:

• the new org's admins reach the project at once, and the old org's no longer do;
• everybody holding a role on the project themselves keeps it;
• the project's own teams move with it;
• teams of the old org lose the roles they held on it, since a team of one org cannot hold a role in another's project;
• roles the old org made itself, held on the project, are taken away;
• invitation links offering those roles are withdrawn.

A publishing project takes its environments, keys, players and usage with it, and counts against the new org's plan from then on. Where the project cannot go to that org yet, for example because the new org has not accepted the publishing agreements or has no room on its plan, the dialog says why and nothing moves.

If you are an admin of no other org, ask an admin of the org the project should go to to invite you as an admin first.

Admins

The org's admins manage it and reach every project of every product it owns. The tab lists them, with your own row marked and whose default org it is.

Invite an admin makes a link: whoever opens it while signed in becomes an admin of the org. It works once, for 14 days, and is shown only when it is made, so copy it then. You can add their email address and a note for yourself, which tell your links apart in the list. Links not used yet are listed under Links waiting to be used, where Withdraw stops one working at once. A withdrawn link cannot be made to work again.

An admin can take another admin out, and can be put back with Undo straight after. Leaving yourself is asked about first, since another admin then has to invite you back. An org keeps at least one admin, so the last one cannot be taken out. Taking somebody out of the org their account came with also stops it being their default org; their account gets a new one the next time it needs one.

Teams

A team is a group of the org's people. It holds nothing until it is given a role, on a project from that project's People page, or on the org itself from this tab. Everybody in it then holds that role for as long as they are in it.

The org's admins see and change its teams, and so does whoever they let manage the org's people. Anybody else is told who manages them.

• New team takes a name, such as Artists, QA or Writers.
• Rename and Delete are on each team. Deleting one takes every role it was given from everybody in it, in every product, at once, and cannot be undone.
• Add somebody already in the org puts a person in the team straight away; Invite by link makes a link that puts whoever opens it in the team, used once within 14 days.
• Leave takes you out of a team, with every role it gave you.
• In the org itself lists the org's own roles that act on the org (its people, roles, usage and making projects), each with a box to give the team that role on the org.

Roles

The roles the org has made, each carrying the permissions it names. Admin and Support are built in to every org; make your own when neither fits, such as a level designer who changes config, or somebody who only reads crash reports.

New role asks for a name, a line saying what it is for, and its permissions. The kinds of permission, and where a role can be given, are in the console's Your org's own roles. A role is given on a project's or an environment's People page, or to a team on the org from the Teams tab.

Changing a role changes it at once for everybody who holds it. Deleting it takes it from everybody, wherever it was given, and withdraws invitations offering it. Deleting cannot be undone.

Targets

Target profiles are the specs your projects aim at on each platform: a name, the platform, an optional device tier such as low or flagship, and the values the target sets. A project picks one profile per platform and overrides what it needs to. Every value keeps its key when a profile is renamed, and a profile's platform cannot be changed once it is made.

Everybody in the org sees the profiles; its admins make, change and remove them. Projects targeting a profile that is removed keep their targets and their own overrides, and stop reading its values.

Settings

• Name: what the org is called everywhere. Any admin can rename it.
• Handle: the org's name in the publishing console's addresses, such as /your-studio/projects/your-game/apps/production. It is lower-case letters, digits and hyphens. After a change, links with the old handle in them still open the org's projects, but not the org's own pages.

Your default org

On the org your account came with, Stop using it as my default hands it on, for example to the studio it now belongs to. You stay one of its admins, and nothing in it changes. What you make from then on goes in a new default org of your own, unless you choose this one.