Terminology proposal, 7. oktober 2026

From Ferdinand (UX), Elisabeth and Arkitekst. Under discussion: the team is asked for feedback. Our feedback is from the admin and tenant admin perspective, noting where a term reaches customers.

Agree

Suggest change

Needs decision

Not in the proposal

Feedback on the proposal

Each concept the proposal names, with our verdict. Admin is what the team sees on the deployed test environment.

Current in im-web todayWord proposed and acceptedWordOurs we suggest a changeNot covered no word proposed in this languagewho sees it

Concept	In im-web today	Proposed, norsk	Proposed, English	Our verdict and comment	Seen by
Library Every image a tenant offers, sellable or not.	API archive (a source: sdl, shutterStock) Admin Image librarycatalog Public SDLShutterstock	Bibliotek	Library	Agree Clearer than "archive", which im-web uses for a source (SDL, Shutterstock). Also name what is in the library but in no group, so not for sale.	Customers (some) Tenant admins System admins
Scope A saved filter over the library: the images a product can sell.	API scope, type "primary" Admin Content (menu)Main group	GruppeHovedgruppe	GroupMain group	Suggest change The admin already uses "Main group". Plain "Group" sits next to "License group" in the same menu. If Group is adopted, rename license group too.	Customers Tenant admins System admins
Secondary scope A narrower filter inside one scope, e.g. Magnum within editorial. Has a priority when groups overlap.	API scope, type "secondary" Admin Content group	UndergruppeInnholdsgruppe	Sub-groupContent group	Suggest change Follows the scope term. With Main group, keep the admin’s "Content group".	Customers Tenant admins System admins
Scope parameter A filter scopes can use, built on one or more metadata fields: Credit uses credit and owner. Required ones must be set on every main group. AND across parameters, OR within one.	API scope parameter Admin Advanced settings › Scope parametersRequired parameters	AvgrensningFilter “Must work both as the action and as what you made”	ConstraintFilter	Suggest change One word for three things: the filter, the chosen values and the action. Use Filter for the parameter and "Define group" for the button. im-web already calls a main group "a saved filter".	Customers Tenant admins (some) System admins
Product One scope + one license group + a base price per license. What gets priced. Draft or published.	API product, type "main" Admin Products & variants	SamlingProdukt	CollectionProduct	Suggest change "Collection" sounds like a set of images, which is the group. The priced offer gets a content word. Stock sites use "Collections" for saved boards. im-public already has albums.	Customers Tenant admins System admins
Variant A product inside a product, priced differently, e.g. Magnum images cost more.	API product, type "variant" Admin Variants	(Spesial) settVariant “Shown to end users as "variant"”	(Special) setVariant	Needs decision Contradicts itself: renamed to Special set, yet customers see "variant". Which word do customers see? "Special" implies premium. A cheaper variant would be odd. Our lean: keep "Variant", which im-admin ships and the proposal itself uses for customers. Same word in both languages.	Customers Tenant admins System admins
Pack Prepaid downloads. In the API a subscription of type "quota" with a download limit.	API subscription type "quota"PACKED Admin Per quotaPack (sales)Subscriptions and creditsDownload quota Other, Customer centre klippekort	Klippekort	CreditsImage pack	Suggest change English uses "Credits" for both the product and its unit. Norwegian keeps them apart. English should too. Check the Swedish word: TT is a tenant.	Customers (a lot) Tenant admins System admins
Pack unit What a pack holds and a download uses up.	API downloadLimitquantityLimit Admin Quotadownloads	Et klipp	CreditDownload	Suggest change im-web counts downloads everywhere. "Download" matches it, and Getty and Shutterstock. "Credit" is already the photo credit line. Only if some images use several units is a currency word right.	Customers (a lot) Tenant admins System admins
Supplier Someone who delivers images to the service, e.g. Magnum.	API supplierdistributorName Admin SuppliersSupplier Public DistributorsDistributørerDistributörer	Leverandør	Supplier	Agree Matches im-admin. Supplier replaces Distributor everywhere. To fix in im-web: The public search filter still says Distributors / Distributører / Distributörer. Rename it Suppliers / Leverandører / Leverantörer.	Customers Tenant admins System admins
Supplier settings Who a supplier is (Visma ID, org number, contact) and which incoming credits map to them.	API supplierssupplier-mappingsdistributor-config Admin System › Suppliersmappings	Leverandørstyring	Supplier management	Agree Fits: Visma ID and org number sit on the supplier. im-admin’s plain "Suppliers" says the same in fewer words. Mappings match the credit field, not portal filters as the proposal says.	Customers Tenant admins (some) System admins
Tenant The organisation selling images in the portal: NTB, TT.	API tenant Admin System › TenantsTenant role Other, im-web docs "a customer with its own branding"	Forhandler “Can be all of NTB or individuals (Elisabeth)”	VendorReseller	Suggest change In English, vendor and supplier are synonyms. Next to Supplier it will get mixed up. An organisation (NTB) and a person who sells (Elisabeth) need separate terms. im-admin has "Tenant role" for the person.	Customers Tenant admins System admins
Platform admin Runs the platform for all tenants: tenants, indexing, suppliers. The Loki team.	API superadmin Admin System › TenantsMetadata Indexer	Not coveredPlattformadministrator “Loki-teamet (as "System admin")”	Not coveredPlatform admin	Needs decision The proposal calls the Loki team "System admin". im-web’s API calls them super admin, and "system admin" is the tenant role above. Our lean: Platform admin, so "system admin" can stay the tenant role.	Customers Tenant admins System admins
Asset One image, video or (later) audio file with its metadata.	API MediaObjectAsset (a rendition) Admin AssetsAsset ActivityImage ID Public Asset IDFil-IDmediafiler	Mediefil “To be done”	Not coveredMedia file	Needs decision Mediefil fits im-public’s Norwegian (Fil-ID, filer). English is split between asset and media. Our lean: Mediefil / Media file for customers. "Asset" can stay in code.	Customers Tenant admins System admins

Not covered by the proposal

Concepts im-web has that the proposal doesn't name. Our suggestions, for the same discussion.

Concept	In im-web today	Ours, norsk	Ours, English	Comment	Seen by
Metadata field An asset property and its possible values, e.g. distributor: NTB, AP, AFP. Scope parameters are built on these.	API metadata fieldkeylabeldataType Admin Advanced settings › Metadata fieldsUsed by	Metadatafelt	Metadata field	The asset properties scope parameters are built on. Developers only. Our lean: Metadata field, as im-admin says.	Customers Tenant admins System admins
License group A set of licenses. Every license belongs to one. Half of a product.	API license grouplicense type (summaries) Admin LicensesLicense group Public Purchase a license	Lisensgruppe	License group	Clashes with Group if Group is adopted for scopes. Our lean: keep it. With Main group for scopes there is no clash.	Customers (some) Tenant admins System admins
Credit line Who to credit when publishing an image (IPTC Credit Line).	API credit Admin credit mappings Public CreditKredittKredit (sv)Foto:	Kreditering	Credit line	With "Credit" as the pack unit, customers see "Credit" twice on the details page with two meanings. Our lean: label the byline "Credit line" / "Kreditering", never a bare "Credit", whatever the pack unit becomes.	Customers Tenant admins System admins
Subscription Unlimited downloads within a date range, for a fixed price.	API subscription type "time" Admin SubscriptionsTime-limitedSubscription plan Public Included in your subscription	Abonnement	Subscription	Needs a name next to the pack, and an umbrella word for both. Our lean: Abonnement / Subscription, as im-web says. Umbrella: Avtale / Plan ("Subscription plan" is already in im-admin).	Customers (a lot) Tenant admins System admins
Customer group Who prices, discounts and subscriptions apply to. In im-web, a workspace.	API customerGroupId (= workspace id) Admin WorkspaceCustomer group (errors) Public Workspacearbeidsområde	Arbeidsområde	Workspace	Ferdinand suggested "Customer group" earlier; the UI says Workspace. Our lean: Workspace, because prices attach to a workspace id. "Customer group" only if pricing ever targets something else, e.g. several workspaces at once.	Customers Tenant admins System admins
Price list A discount or premium on a product for one workspace, as a percentage or fixed price.	API price listbase price Admin Discounts & premiumsBase price Public % Discount	Rabatt / tillegg	Discount / premium	im-web’s Discount, Premium and Base price work. Our lean: keep them, plus Grunnpris / Base price. Drop "price list" from the UI.	Customers (some) Tenant admins System admins
Tenant admin Runs one tenant’s portal: content, licenses, products, subscriptions, discounts, customers.	API tenant permission "admin" Admin AdminTenant role Public Admin (menu link)	Administrator	Admin	The role that runs a tenant’s portal day to day. Our lean: Admin, as im-web’s guide says.	Customers Tenant admins System admins
System admin Above the tenant admin, within one tenant: sets up the scope parameters main groups can use.	API tenant permission "systemAdmin" (not created yet) Admin Advanced settingsSystem adminsystemAdmin	Systemadministrator	System admin	This is the missing role: someone with more rights than an admin sets up scope parameters and metadata fields for a tenant ("Advanced settings" in the admin). The proposal’s "System admin = Loki team" mixes this tenant role with the platform team. Decide: is it a tenant’s own power user, or the Loki team acting inside a tenant?	Customers Tenant admins (some) System admins
Developer Sets up metadata fields: the asset properties scope parameters are built on.	Admin Advanced settings › Metadata fields Other, Prototypes Developer	Utvikler	Developer	A planned role, not in Auth0 yet: sets up metadata fields. Grouped with System admin under Advanced settings until then. Our lean: Developer, as planned.	Customers Tenant admins System admins

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.

Proposal as received

Copied unchanged, typos included.

Term	Description	Norsk	English	Rationale
Product	Et "product" er et scope med lisensieringsregler. Kundene kjøper BILDER, ikke products eller scopes. Et product kan ha en rekke avgrensinger, men det er scope som bestemmer disse avgrensingene. Produkter er både bilder, videoer og på sikt lyd.	Samling	Collection	Naturlig og etablert for store samlinger som ikke nødvendigvis har tydelige avgrensinger. Medieagnostisk.
Variant	Nytt konsept, underkategori av produkt, f.eks. bilder fra Magnum, som koster mer enn andre, og som derfor må kunne separeres fra bilder fra andre leverandører.	(Spesial) sett	(Special) set	Nøytralt og enkelt. Likt på norsk og engelsk.
Scope	En avgrenset mengde bilder. Et scope definerer hva som kan bli et produkt, men dette kan ikke kjøpes før lisensiering er på plass.	Gruppe	Group	De som trenger ordet: tenants (og utviklere).
Secondary scope	Et secondary scope er en ytterligere avgrensing, og er alltid en del av et større scope. Mot sluttbruker presenteres dette som en "variant".	Undergruppe	Sub-group
Scope parameters		Avgresning / Avgrens gruppe / Definer gruppe	Constraint / Define group	Her trenger vi noe som fungerer både som handlingen man utfører og det man har laget
Distributor config	Her definerer adminbrukere: - mapping av filtre fra bildeleverandør mot portalens egne filtre - integrasjon til f.eks. Visma for fakturering - all metadata	Leverandørstyring	Supplier managment	Tar utgangspunkt i rollen som bruker funksjonen.
Packs (klippekort)	Flere mulige betegnelser Elisabeth og Ferdinand har tenkt på: punch card, bundles, bulk deal, downloads. (Downloads brukes hos andre store internasjonale tilbydere som Getty, Shutterstock.)	Klippekort	Credits	Klippekort fungerer egentlig fint på norsk, og er godt etablert, men vi trenger et godt engelsk alternativ som fint lar seg oversette til andre språk.
-	Valutaen som benyttes i packs/klippekort må også kunne omtales.	Et klipp	Credit
Distributor	Noen som leverer bilder til tjenesten.	Leverandør	Supplier
Tenant	De som selger bildene i tjenesten.	Forhandler	Vendor	Dette kan være hele NTB eller enkeltpersoner (Elisabeth)
System admin	Loki-teamet
-	Den totale mengden av bilder tilgjengelig fra forhandler bør ha et fast navn.	Bibliotek	Library
To be done
Mediefil (asset)