Latest News from the Applivery team
App Distribution
New feature

πŸ” New: Share Builds externally using One-Time Password

Karla avatar
Shared by Karla β€’

If your organization enforces SSO-only authentication, sharing a build with an external freelancer, QA studio, or partner has always meant a compromise: either create exceptions in your identity configuration or ask external users to go through an authentication flow they don't have access to.

Neither option is acceptable when compliance is non-negotiable.

OTP (One-Time Password) access solves this. It lets you grant temporary, identity-verified access to any external user β€” at the publication level β€” without touching your global SSO configuration.

βš™οΈ Key Capabilities

πŸ“§ Email-based allowlist

Add the email addresses of authorized external users directly to a publication. No Applivery account or SSO enrollment required on their end.

⏱️ Time-limited, single-use codes

OTPs are valid for 5–10 minutes and cannot be reused. Each access attempt requires a fresh code, ensuring no credentials can be shared or replayed.

πŸ” Single-use access

Optionally remove an email from the allowlist after the first successful download, enforcing strict one-time access. Re-adding is always possible if needed.

⏳ Temporary user lifecycle

OTP users are created automatically and auto-deleted after 30 days. Existing workspace users are never counted twice.

πŸ”” New build notifications

When a new build is published, OTP users on the allowlist can receive a notification email with a fresh code β€” no need to re-request access manually.

πŸ“… Combine with Expiring Publications

Pair OTP access with an expiring publication for a fully time-bounded and identity-verified external sharing flow, with zero manual cleanup.

πŸ“Œ Use Cases

  • External freelancers or contractors: One-time build review without creating permanent accounts.
  • External QA studios: Time-limited access to a beta without relaxing global authentication.
  • Partner or customer previews: Share a specific build securely with a named list of recipients.
  • SSO-enforced organizations: Distribute externally without creating SSO exceptions or compromising your identity policy.

πŸ“š You can learn more about OTP by following this link.

If you have any questions or need more information, please contact your Customer Success Manager.