Skip to content

Printix ​

Reads the Printix partner API and counts the active users per customer tenant — the figure that is billed.

Credentials (gear icon) ​

FieldMeaning
Auth URLhttps://auth.printix.net
API URLhttps://api.printix.net
Client ID / Client SecretAPI client of the partner account
Partner IDUUID of the partner account

Metrics ​

MetricCount
printingUsersactive users per tenant in the previous billing period — every user who signed in to Printix (client, app or administrator) at least once during the monthly billing cycle, whether they printed or not. The key keeps its historical name so mappings and history stay intact; until 2026-11-06 it counted the printing users.

Splitting one tenant across several customers ​

Some customers share one Printix tenant with their sister companies; the users differ only in the domain of their e-mail address. Multiverse can split such a tenant by domain:

  1. In the tenant's Printix Administrator create an application of the type Cloud Print API (Authentication → Applications → Create Application). Printix allows one such application per tenant and counts it like a user. Note its Client ID and Client Secret — the secret is shown once.
  2. In Multiverse → Printix click Split… in the tenant's row and store the Client ID and Client Secret under Cloud Print API access. The partner API knows no users; this application lets Multiverse read the tenant's user list. Test connection shows how many regular users the tenant has (guest users are left out), how many carry an e-mail address, the users per e-mail domain — and the fields of a user object. If the API returns no users, the dialog shows the keys and an excerpt of its response so the shape can be checked.
  3. Add a domain rule per domain that belongs to another customer (Assign… in the domain table prefills it): domain → customer. Domains without a rule, and users without an e-mail address, stay with the tenant's own customer. Several domains may point to the same customer (they form one part); a rule naming the tenant's own customer is the same as no rule.

From the next snapshot on the tenant appears as several customers: the tenant itself plus one per domain rule. Printix reports the billing figure — the active users of the previous billing period — per tenant only, so it is split in proportion to the user numbers per domain, rounded to whole users with the largest remainder; the parts always add up to the tenant's figure. The dialog previews that split under Next snapshot once a connection test has run.

A tenant with rules but no stored access bills as a whole — the snapshot says so, and the invoice runs repeat it. A user list that fails — or comes back empty for a tenant that bills users — no longer leaves everything with the tenant: the snapshot spreads today's figure by the users of the last successful read, so the customers of the rules keep their share (only a tenant whose users were never read stays whole); the snapshot carries a warning naming the day of that read, which the invoice runs repeat. The list marks every tenant's state: "N domain rules" (splits), "N domain rules · no access" (bills as a whole), "access stored" (no rule yet).

Specifics ​

  • Tenant IDs are stable → automatic rename detection. The customers of a split tenant carry the ID tenant ID:domain, so the rename detection covers them too.
  • The secret of a Cloud Print API application cannot be read back after saving — only replaced or deleted.