Licensing

A licence is what lets you use udStream and the other udSDK products against this server. Licences belong to an organisation, not to the server administrator — an organisation holds a number of seats and decides which of its members get one.

Looking for the open source notices instead? They are on the 3rd Party Licenses page.

Tiers and Add-ons

Every licence is one tier, optionally with add-ons on top:

Add-ons sit on top of a tier rather than replacing one, so a member needs a tier before an add-on can be assigned to them.

There is also a Previewer tier, which is not a seat and cannot be bought or assigned. It is granted for the life of a single session to someone opening a scene that has been shared for preview — see Scenes.

Your Own Licence

Settings → License shows your effective licence and every grant behind it.

You may hold grants from more than one source — from two organisations you belong to, for example. The effective licence is the best of them: the highest tier you hold, with the add-ons from all of them combined.

Each grant shows which organisation granted it and when it expires (or that it is perpetual). Relinquish gives a grant back, returning the seat to the organisation so somebody else can use it. That is worth doing when you no longer need it, and it cannot be undone from your side — the organisation has to assign it again.

Organisation Licences

The Licenses tab of an organisation is where its seats are managed. Seeing the tab requires the View Billing Info permission; the actions on it need more than that:

See Permissions.

Seats, capacity and consumption

For each product the organisation holds, the tab reports:

• Capacity — how many seats it has.
• Consumed — how many are currently assigned to members.
• Available — what is left to assign.

Capacity comes from allocations. An allocation is one entry in the organisation's ledger: a quantity of one product, valid from a date, either perpetual or until an expiry. Allocations are added by a purchase or by a server administrator, and they are never edited or deleted — removing seats records a negative entry instead, so the running total is correct and the history stays readable. Allocation history shows the whole ledger, including entries that have been voided or have expired.

Assigning a seat

Open Assign on a product and tick the members who should hold it. Unticking a member takes the licence back and frees the seat immediately. The dialog reports how many seats are left as you go, and refuses to overcommit — if every seat is in use you have to free one or buy more.

Two things are worth knowing before you start:

• Add-ons need a tier. A member with no tier shows as Needs a license first, and the add-on cannot be ticked until they have one.
• Removing a tier removes that member's add-ons with it. The dialog says so before you save.

If a member already holds an equal or better licence from somewhere else, the dialog says so — assigning a second one would consume a seat that changes nothing for them.

Buying seats

If the server has purchasing enabled, Purchase seats buys more. Choose the products and quantities you want, and everything in the basket is bought together in a single Stripe checkout. Purchased seats arrive as allocations shortly after payment completes, ready to assign.

Purchase history lists what has been bought and the state of each purchase — Pending, Complete, Failed, Refunded — with a link to the receipt. Viewing it requires the View Billing Invoices permission.

Purchasing is switched on and configured by the server administrator, so if the button is missing on your server, that is why. See the administrator guide's Licensing & Purchasing page.

Activity

The Activity tab records administrative changes to the organisation, newest first, including licence assignments and revocations. It is the place to look when a member's licence changed and nobody remembers doing it.