Organizations
An organization is a group of Parametra accounts sharing one credit pool and one roster of roles. It is created at signup and managed on the website; the addon reads it, marks projects as the organization's, and bills their work to the pool.
One group, two names
An organization is a group of Parametra accounts that share one credit balance and one member roster. The website calls it your Team — that is the label on the tab in your account. The addon and the API call the same thing your Organization. There is one group; the two words are interchangeable, and the glossary records the pairing.
Membership is an assignment, not an invitation. An admin adds an email address and that person is in the organization from their next request onwards. There is no pending state, nothing to accept and no token to pass on.
What an organization shares is a credit pool, a roster with roles, and visibility of the projects marked as the organization’s. Being in one does not by itself let you open a colleague’s project — that is granted per project, and Sharing & access keys covers it.
Starting one at signup
An organization is created on the website, at signup. The first step of the form has an Organization field marked (optional), with the placeholder Leave blank for a personal account. Type a name there and the organization is created along with your account; leave it empty and your account is personal.
The /signup page, step one, with the form filled in far enough to show the Organization field, its (optional) marker, the placeholder or a typed studio name, and the hint line underneath it.
The hint under the field reads Creating one makes you its admin. You can add your team afterwards. The role actually recorded is owner, which carries everything an admin can do and one thing more: the owner cannot be re-roled or removed through the account API. Asking to change that role returns The owner’s role cannot be changed. Transfer ownership first.
There is no way to create an organization from inside Blender. The addon reads which organization you are in and what standing you have there, and nothing else about it.
The four roles
Every member of an organization holds one of four roles. Only owner and admin can manage the roster; a role change may set admin, member or viewer, never owner.
Your own role is shown as a tinted pill. In the addon it is on the ORGANIZATION card in the account popup’s Account section, beside the organization’s name; on the website it is written out on the Organization card in the Team tab.
The addon account popup (header user icon), Account section, cropped to the ORGANIZATION heading and the card under it: the organization name, the credits line beneath it, and the role pill at the right of the card.
Adding and removing members
The roster is managed on the website, in the Team tab of your account. The tab appears only for accounts that belong to an organization. Everyone in the organization sees the roster; the controls — add, change a role, remove — are drawn for admins and the owner.
The website account page at ?tab=team, signed in as an org admin, showing the Members card with several member rows — each with an avatar, name, email and a role dropdown — the 'N of M seats used' line in the card header, and the Organization card on the right.
- Open Account → Team and scroll to Add a member under the roster.
- Type their email address and pick a role from the dropdown beside it — admin, member or viewer. Press Add.
- If the address already has a Parametra account, they are in immediately and the roster redraws with their row.
- If it does not, the answer is No account for that email. Ask them to sign up first, or resend with create=true to make the account for them — the API’s own sentence, printed verbatim — and a Create the account for them → link appears beside it. Pressing that is the resend it describes: the account is created and added, Cognito emails them a temporary password, and the line becomes Account created and added — Cognito emailed <email> a temporary password. Tell them to check their spam folder.
The bottom of the Members card on the Team tab: the 'Add a member' label, the email input, the role select open on admin/member/viewer, and the Add button — ideally with the red 'ask them to sign up first' message and the 'Create the account for them' link underneath.
A role is changed from the dropdown on that person’s row, and Remove beside it takes them out. Removal asks first, and says what happens: Their account survives and becomes personal. Nothing is deleted — they simply belong to no organization any more.
Five requests are refused, each with its own sentence. The last two are the account API answering: the Team tab draws no dropdown and no Remove on your own row or on the owner’s, so those rows show a plain role pill instead of controls.
The seat count is on the Members card header for admins, as N of M seats used. Buying more is a billing change rather than a roster one, and the Organization card links to Subscription & billing for it.
The addon cannot add, remove or re-role anybody. Its Organization tab is read-only — the name, the seats used, and your role — and it is drawn only for admins and owners. Members and viewers read their organization on the Account section’s card instead.
The addon account popup with the Organization nav entry selected, signed in as an org admin, showing the header card: the organization name, 'N of M seats used' underneath it, and the role pill at the right.
Organization projects
A project belongs to the person who created it unless it is marked as the organization’s at the moment it is made. That mark is the Organization project checkbox on the addon’s New Project form, and it is drawn only when your account is in an organization and your role is admin or owner. Its tooltip states the effect: everyone in your organization sees it, and its admins choose who can open it.
The addon launch screen's New Project form, signed in as an organization admin, showing the name field, the description box, the 'Organization project' checkbox ticked, the 'Start with the default theme' checkbox below it, and the Create button.
There is no way to convert a project afterwards from this form, and no silent downgrade: ask for an organization project without the standing to make one and the server refuses with only an organization admin can create an organization project rather than quietly making a personal one.
Marking a project as the organization’s does three things.
- —Everyone in the organization sees it in Open From Parametra — its name, description, owner and latest version.
- —Seeing is not opening. You can open it if you own it or if you have been given access to it; otherwise the row carries a lock button in place of the open arrow, and its tooltip reads Ask an administrator for access to <project>.
- —Work run against it is billed to the organization pool rather than to whoever pressed the button.
In Open From Parametra, the filter row carries Organization and Shared with me alongside All projects, My own and I can open, and each row is badged: a building for an organization project, a person for your own. Opening from Parametra walks the dialog.
The OPEN FROM PARAMETRA dialog with the Organization filter ticked, showing at least two rows — one carrying the open arrow button and one carrying the lock 'Ask an administrator for access' button — with the building badge visible at the right of each row.
Granting access does not require opening the project. In the addon, open the account popup, go to Projects, and press Access on the project’s row; that button is drawn for admins and owners. The dialog lists the organization’s members with a Give access button each, and Copy access key at the bottom for somebody outside the organization. Keys are minted for the project’s owner only.
Pooled credits
An organization has one credit pool. The Team plan is priced per seat, with a minimum of three seats, and its credits are pooled across the organization; Credits and plans has the rest of the metering.
Which balance a job spends is decided per job, in this order.
- The job is on an organization project — it spends the organization pool, whoever ran it.
- Otherwise, if you hold a personal balance, it spends yours.
- Otherwise — a member who has never held a personal balance — it spends the pool.
The addon tells you which of those you are in without asking you to work it out. The ORGANIZATION card in the account popup’s Account section reads either Credits are shared across the organization or You have your own credit allowance, and the usage bar underneath measures whichever balance that is.
On the website, the Organization card in the Team tab prints the pool itself — a number of pooled credits — over the line Members spend from the shared pool. Your role: …
There is no credit gate. A run that costs more than the balance holds still completes, and leaves the balance negative. On a shared pool that is somebody else’s balance too, so watch the figure before starting a full theme — roughly 220–275 credits and about twenty minutes.
Your city itself is not part of any of this: it lives in the engine process, not in your .blend, and How it fits into Blender explains what that means for saving and sharing it.
The Discord is fastest for anything scene-specific. Email suits licensing, billing and anything needing a file attached.
Contact support →