ApivomApivom
Get Demo

Apivom Key — one sign-in across every Apivom product

Key is the identity and access management layer behind the Apivom products. One account signs you in everywhere, each organisation is a customer account, and roles decide what each person can do. Key is included with the products and is not sold separately.

Infrastructure layer

Key in numbers

4
External identity providers
3
Second-factor methods, plus passkeys
365days
Sign-in event history
30 / 90days
Session limit, idle and maximum

One account, with access that stays under control

People sign in once, see only their own organisation, and get the access their role allows. Strong sign-in options and a sign-in history are built in.

Single sign-on

Sign in to one Apivom product and you are not asked for credentials again in another. Signing out is passed on to the products.

Organisations as customer accounts

Each customer is an organisation. The sign-in token carries it, and it decides which customer account’s data a product opens for you.

Roles per product

Access comes from roles defined for each product. A higher role includes the lower ones, for example Iris roles run from viewer up to admin.

Sign in with an existing account

Use a Microsoft, Google, LinkedIn or Autodesk account. The sign-in links to an account that already exists or was invited.

Second factors and passkeys

Authenticator app, security key and recovery codes, plus passkeys for passwordless sign-in.

Sessions and sign-in history

Sessions end after 30 days idle or 90 days at most, and sign-in events are kept for 365 days.

Included with the products

How the Apivom products use Key

You do not set Key up on its own. It is the sign-in and access layer the products share, so a person has one account and each product reads the roles meant for it. Here is where it is used today.

  • Iris. Staff sign in with Key and get one of six roles, from viewer to admin. Portal customers use a separate portal role that keeps them inside the portal.
  • Pivot, Atlas, Mars, Orbit, Abu, Halo. The same account opens each of them. Every product has its own roles, so access in one does not grant access in another.
  • Operations tools. The tools behind the platform, such as Ping, Blob, Opus, Staff and Otto, use Key for sign-in too.
  • Service accounts. Apivom’s own services, such as customer account provisioning, act with narrow service roles and signed credentials instead of shared passwords.
Sign-in security

Sign-in that is closed by default

Key does not let strangers register. People get in because they were provisioned or invited, and the second factor applies to those who have set one up.

  • No self-registration. A sign-in with an outside account only links to a person who is already provisioned or invited.
  • Second factor for those who set one up. Anyone with a configured authenticator app, security key or passkey is asked for it at sign-in.
  • Portal sign-in can require it. An Iris customer can require a second factor for its own customers in the customer portal.

Frequently asked questions

What is Apivom Key?

Key is identity and access management with single sign-on. It is the sign-in layer for every Apivom product: one account across products, organisations as customer accounts, roles per product, sign-in with Microsoft, Google, LinkedIn or Autodesk accounts, second factors and passkeys, and a sign-in history.

Is Key sold separately?

No. Key is an infrastructure layer that is included with the Apivom products. You do not buy or set it up on its own. If you want to know how sign-in and roles work for your use of Iris, Pivot or the other products, talk to us.

Which identity providers can people sign in with?

Four: Microsoft, Google, LinkedIn and Autodesk accounts. Self-registration is off, so signing in with one of them only links to a person who is already provisioned or invited. Passwords are not the only way in.

How does multi-factor sign-in work?

Key supports three second-factor methods: an authenticator app, a security key and recovery codes. Passkeys give passwordless sign-in. People who have set up a second factor are asked for it. Passkeys and second factors are offered, not forced on everyone. An Iris customer can require it for its portal customers.

How do organisations and roles map to products?

Each customer is an organisation, and the organisation decides which customer account’s data a product opens. Customers belong to one organisation. Access inside a product comes from roles defined for that product, and a higher role includes the lower ones.

What sign-in history is kept?

Sign-in events are recorded and kept for 365 days. Sessions are limited too: a session ends after 30 days without activity, and no session lasts longer than 90 days.

One sign-in, access that stays in order

Key comes with the Apivom products. Talk to us about how your people and customers should sign in.