- Which applications can connect to Clavkey?
- Any application that supports standard SSO protocols (SAML 2.0 or OpenID Connect) connects without custom code, which covers the large majority of modern SaaS and internal tools. For legacy apps that don't speak those protocols, Clavkey can front them through secure hosting so they still sit behind your single sign-on.
- How do users sign in, and who manages it?
- Your people sign in once through a single, secure sign-on and reach every application they're entitled to. Clavkey is the platform that powers it: the directory, the MFA enforcement, the access policies, and the secure hosting behind your apps. You configure everything in Clavkey, and your users get one secure sign-in.
- What MFA methods are supported?
- Authenticator apps (TOTP), passkeys, and hardware security keys, with phishing-resistant options available for high-privilege accounts. You can require MFA globally, or step it up only for sensitive applications and administrative actions.
- Can we manage access for clients and contractors, not just staff?
- Yes. Clavkey is built for staff and external users alike. You can grant clients, partners, and contractors scoped, time-bound access governed by the same policies and audit trail as your internal team, without provisioning separate infrastructure.
- How does offboarding work?
- Because access is centralized, removing a user revokes their access to every connected application and hosted resource in a single action. There are no per-app accounts to chase down and no lingering credentials, which closes one of the most common gaps in access security.
- Do you host the applications themselves or only gate them?
- Both, depending on what you need. Many teams keep their apps where they are and simply put them behind Clavkey's single sign-on. Others move sensitive internal tools and client portals into Clavkey's secure hosting so they live entirely behind the identity layer. The two approaches mix freely.
- Can Clavkey host a sensitive application like an employee portal?
- Yes, that's exactly what secure application hosting is for. An employee portal, a client portal, or any internal tool can run in an isolated, hardened environment behind a single, authenticated sign-on, with identity-gated access, MFA, encryption, and a full audit trail by default. Your users reach it through single sign-on, and it is never exposed to the open internet.
- How does secure private network access work, and can it replace our VPN?
- Clavkey provides identity-based private network access. Staff, clients, and partners reach internal resources only after they are authenticated and authorized, over encrypted connections scoped to what they need. There are no shared VPN credentials and no always-on tunnels. Access follows the person, governed by the same policies, MFA, and audit trail as your applications, which lets most teams retire a legacy VPN.