How do Teams work?

In short

• Put several people in the same world, spending from one balance
• A team has its own balance, so members work from it without needing their own subscription (One balance)
• Invite by email from the team page and pick a role as you invite: full can generate, viewer can see the work but not spend (How you’ll use it)
• Everyone works from the same briefs and projects, so the brief one person wrote is the one everyone else is building on
• Usage is shown by person and by media type, which is what you need when the work is billed to a client (Reviewing usage)
• Seats include the owner, and the cap comes from your plan (Managing the team)

A team exists so several people can work in the same world without each of them buying their own subscription, and so the person paying decides who can spend.

One balance, not many wallets

A team has one credit balance, and it is the team’s own. It is not the owner’s personal balance and it is not split into per-member wallets. Three things fund it: the team plan’s monthly grant lands in it, credit packs can be bought straight to it, and auto top-up, if the owner turns it on, refills it before it runs dry. See Buying credits.

Members hold nothing and never choose a balance. A generation on a team project spends the team’s balance, always, for everyone on the team, the owner included. There is no fallback to anyone’s personal credits, and a team balance never pays for personal work.

Nothing is transferred, in either direction, ever. Credits do not move from a person to the team or back. When someone leaves, nothing is stranded in their hands, because nothing was ever in them.

There is no per-member spending cap. The control is the usage report: every credit the team spends is attributed to the person who spent it, by media type. See Reviewing usage.

How you’ll use it

Invite by email, and choose the role as you invite. A full member can do the work: compose prompts, generate, use the agent. A viewer can see everything the team has made and cannot spend on it.

Seats count the owner. If your plan allows five, that is you and four others. The invite is refused once the cap is reached rather than silently seating someone.

Members do not pay. They work from the team’s balance. Someone who already has their own Lorvara account keeps it: their personal work stays theirs, their own plan is unaffected, and being on your team neither adds to nor takes from it.

Team projects count against the team’s storage; personal projects count against the person’s own. Work done for the team is the owner’s; work someone does on their own account is theirs.

For Team leaders (Directors and Producers)

Entitlement is worked out, never stored. Whether a person can generate right now is computed each time from their own plan, their seat, and whether the owner’s plan is current. There is no flag to get out of step with the truth.

If the owner’s plan lapses, the team stops generating and says so. Members are told the owner’s plan needs attention rather than being shown a generic failure. Nothing is deleted and nothing is lost. The work is there when the plan is current again.

A viewer who is refused is told they are a viewer. Refusals name their reason rather than presenting as an error, so a person can tell the difference between “ask the owner for a full seat” and “something is broken”.

A Skill scoped to a team belongs to the team, not to whoever wrote it. A teammate’s Skill offers Fork rather than Edit (see Sharing and forking).

What to read next

• Sharing and forking — how Skills work across a team.
• Teams and briefs — sharing the world itself.