Organisations, people and teams

You open Members, select Invite, type [email protected] and select Send invite. Maya gets an email, makes her account and selects Accept. She is now a Member of your organisation, and she sees no installations yet. You open her page, select + Add access, choose Everything, Log in, and Add. Within a few minutes she can open every installation you have.

An organisation is the unit of the account site. It holds your installations, your plan, your balance and the people who work on them. This page covers its people and what each of them can do. Create and manage your installations covers the installations, and Plans, balance and billing covers what you pay.

Your organisations

The organisation you are in is the first row of the sidebar, under the Player One logo. Select it to switch to another, to create one, or to leave this one. Every page under it, and every setting, belongs to that organisation. Switching shows the same page in the other organisation where it has one.

Create organization asks for a name and makes you its Owner. The line under it says how many organisations you own out of how many you may own. At your limit the item is greyed out.
Leave organization removes you from this one, and you lose access to its installations. To come back you need a new invitation. The last Owner cannot leave: make someone else an Owner first.
A new account belongs to no organisation. The site opens on No organization yet, with Create organization. An invitation's link takes you to the invitation instead.

Rename an organisation in Settings > General, which also shows the organisation ID with a copy button. Only people who manage members can rename it.

Owners and Members

A person in an organisation is an Owner or a Member. Only Owners carry a badge. Nothing else is chosen from a list of roles.

An Owner can do everything, including making and removing other Owners. An organisation can have several.
A Member can do nothing until they are given access. Whatever has not been given is forbidden.

A Member's power comes from rights, and a right can be given to a person or to a team.

Right	On the whole organisation	On one project	On one installation
Log in	Use every installation	Use its installations	Use it
Administer	Run and change every installation	Run and change its installations	Run and change it
Create	Add installations	Add installations to it	Not offered
Billing	Pay and see invoices	Not offered	Not offered
Members	Invite people and give access	Not offered	Not offered

Log in opens the installation as a user. Administer opens it as an administrator and allows start, stop, update, resize, export and delete. Create includes paying for the room a new installation needs, and whoever creates an installation administers it from then on. Billing is not needed to create or resize an installation. Members never covers Owners.

Rights on the whole organisation come with every plan. Rights on a single project or installation need a Team plan.

Invite someone

Open Members and select Invite.
Type their email address. With a Team plan you can also tick teams for them to join.
Select Send invite.

They get an email. Someone new to Player One makes their account from it and types their own name: Signing in and keeping your account safe covers that. Whoever opens the link lands on a page that asks Join Acme?, with the organisation's own name, says who invited them, and offers Accept and Decline. Only the person signed in with the invited address can answer. Anyone else is told which address it was for.

Until they answer, the invitation sits under Waiting to accept on the Members page. Send again mails it afresh and extends it. Cancel withdraws it. An invitation nobody answers expires, and the page tells the person to ask for a new one.

A new Member has no access to anything yet. Give them a right, directly or through a team, or they see No installations yet with a line saying nobody has opened one to them.

Give and take access

Open Members and select a person. Their page shows the rights each of their teams gives them, then Given to the person directly. + Add access at the foot of a list turns into one row you fill in:

On where Maya can right

Choose where (Everything, and with a Team plan a project or an installation), then the right, then Add. Each right in the list comes with its meaning, and Already has marks one she holds. A right you gave directly has a bin beside it. A right from a team, a project or the organisation shows where it comes from and is removed there.

To see who can use one installation or project, choose Access in the installation's ⋯ menu, or in a project's menu. Who can use name lists people under Administer, Log in and, for a project, Create, each with one grey line saying why: Owner, given here, a team and project, all installations. The same sheet has + Add access.

A new right takes effect within a few minutes. A right taken away stops new sign-ins to the installation at once, and ends a sign-in already open within the hour: Sessions and signing out explains.

Owners and removing people

On a person's page, the Danger zone at the foot holds what is left:

Make Owner makes a Member an Owner. It counts towards that person's own limit of organisations they may own.
Step down, on your own page, makes you a Member again. Make Member does the same to another Owner. Both keep the access that was given to the person or their teams.
Remove from the organization takes the person out, and they lose access to everything here right away.

Only Owners make, change and remove Owners. The last Owner cannot step down or be removed.

Teams

A team is a group of Members who are given access together. Give the Editors team Log in on one project once, and everyone in it can use that project. Take someone out of the team and they lose what the team gave them, unless they hold it themselves.

Open Teams in the sidebar. New team takes a name and lets you tick its members in the same step. Open a team to see People, with Add people and a remove button on each, and Access, where + Add access works as it does for a person. The pencil beside the name renames it and Delete team removes it. A team's page says "Everyone in the team has this access."

When the plan has teams, anyone in the organisation can read the list. Only people who manage members can open one.

Projects

A project is a folder of installations. Every installation is in exactly one, and every organisation has a default project. A right given on a project covers every installation in it, including ones added later.

New project on the Installations page names one. Once you have more than one, the page groups installations under project headings. A project's menu has Access, Rename and Delete. A project can be deleted when it is empty and is not the default one: move its installations out first, using Move to project on each card. Choose the project when you create an installation.

People who can manage members see every project. Anyone else sees only the projects their own installations are in, and no headings while those are all in one project.

What needs a Team plan

Projects beyond the default, teams, and rights on a single project or installation come with a Team plan. A plan that lacks them hides them from everyone who cannot buy a plan. If you manage billing, you see them locked, with a Team badge on the Teams row, on New project, on the Projects and Installations headings of the place menu, and at the foot of an Access sheet. Selecting one says what the plan brings and offers Choose a plan.

Losing a Team plan takes nothing away. What you made keeps working, and you can still remove it, but nothing new of that kind can be made.

Yes, in both cases through the organisation.

An installation is shared by giving people a right on it, or on its project, or on the whole organisation. On a plan without a Team plan, the whole-organisation rights are what you have, so a person with Log in opens every installation.
A plan belongs to the organisation. Its installations, memory and storage are one pool that all the organisation's installations share. People with Billing manage it. Everyone else uses what is in it. Someone with Create can add installations, and whoever administers one can resize it, without seeing the billing.

Developer settings

API tokens are made in Developer settings (/developer), in the menu at the foot of the sidebar. A token can belong to you or to one of your organisations. If you manage members, you also see and can revoke the other members' tokens that reach that organisation. Signing in and keeping your account safe covers making one.