im-web today
Library
every image
Scope parameters
filters on metadata fields
Main group
a saved filter
Content group
a narrower slice
Product
main group + licenses + prices
Variant
content group + own prices
↑ licenses come in
License group
what buyers may do
Workspace terms
discount, subscription, quota
Purchase
price on the asset page
Which images
Everything starts with the library
Every image the tenant has, with its metadata: archive, media type, editorial or creative, supplier, place, date. Nothing in the library can be bought by itself.
Example
NTB’s library has hundreds of millions of images and videos from NTB’s own photographers and from suppliers like Magnum.
Who sees it
- Customers
- Tenant admins
- System admins
Which images
Metadata fields and scope parameters describe it
A metadata field is one property of an image and its possible values. A scope parameter is a filter built on one or more metadata fields, which scopes can then use. Developers set up the fields; system admins choose which parameters exist and which are required.
Example
The metadata field distributor has the values NTB, AP, AFP and more. The scope parameter Credit filters on two fields at once: credit and owner.
Who sees it
- Customers
- Tenant admins (some)
- System admins
- Developer is a planned role, not in Auth0 yet. Until then, every admin sees these settings.
Which images
A main group picks images by filter
A saved filter: "these images". It sets values for scope parameters, like which archive and which media family. New images that match join automatically.
Example
NTB Editorial: archive is SDL and media family is editorial and media type is image.
Who sees it
- Customers
- Tenant admins
- System admins
- No "all except" and no "all, including future values".
- Should each main group be used by only one product? Not enforced.
Which images
A content group narrows it down
A smaller slice inside one main group, made by adding more filters. When slices overlap, their priority decides which one counts.
Example
Magnum inside NTB Editorial: the same filters, plus supplier is Magnum.
Who sees it
- Customers
- Tenant admins
- System admins
- How overlapping content groups are resolved in the backend.
How they may be used
Licenses say what the buyer may do
A license is a name and its terms text, nothing more. Licenses come in license groups, and every license belongs to exactly one group. Customers read the terms on the asset page.
Example
Editorial licenses: Editorial use; Web and social media; Business website and commercial.
Who sees it
- Customers (some)
- Tenant admins
- System admins
- Licenses have no usage dimensions (channel, duration, reach); today these are agreed by email.
What it costs
A product puts a price on it
A product joins one main group and one license group, with a base price for each license it sells. That is what makes images buyable. Customers buy images, not products: they never see the product.
Example
NTB Editorial = the NTB Editorial main group + Editorial licenses, with Editorial use at 1 500 kr.
Who sees it
- Customers
- Tenant admins
- System admins
- Products are Draft or Published, but no screen changes it, and Draft products are still priced on the site.
What it costs
A variant prices a slice differently
A product inside a product. It points at one content group and has its own base prices.
Example
Magnum variant of NTB Editorial: the same licenses, but Editorial use costs 3 000 kr.
Who sees it
- Customers
- Tenant admins
- System admins
For whom
Customers can have their own terms
A workspace (the company or person buying) can get a discount or premium on a product, a subscription with unlimited downloads for a period, or a fixed number of downloads (a quota).
Example
Aftenposten has 10% off NTB Editorial, and a quota of 50 downloads this year.
Who sees it
- Customers (a lot)
- Tenant admins
- System admins
- Which wins when several apply: agreement, subscription, discount, variant or base price?
- What the "Global" price customers see without an agreement is.
For whom
On the asset page it all comes together
When a customer opens an image, im-web asks the price resolver: which product covers this image, which base prices apply, and does this workspace have a discount or subscription? The page shows the licenses with prices.
Example
Ola at Aftenposten opens a Magnum photo. It matches the Magnum variant, so Editorial use is 3 000 kr, less 10%: 2 700 kr excl. VAT.
Who sees it
- Customers
- Tenant admins
- System admins
- The resolver returns the pieces, not the final price or which rule won.
- Subscription holders should download directly. Not built yet.
im-web usage taken from: main 868163e (admin and public as deployed); LIP-1338 e021d1f (new product config UI, docs/glossary.md); LIP-1486 8210d7c (Suppliers page). No branch means main and LIP-1338 agree. im-admin is English only; Norwegian and Swedish exist only in im-public. Live API docs, which follow the team's current work: products, sales, user, search, indexer.