Identity and people

Sign in to company apps

How employees sign in to deployed apps, who can open each app and how IT sets the sign-in floor.

Deployment
BYOC

Employees open an app's address and sign in with Diakrin. IT does not set up a separate identity-provider application for each app, and each app decides who may open it.

How employees sign in to a company appAn employee opens a company app in your cloud. Without a session, the app redirects to Diakrin, which uses your identity provider when SSO is required. Diakrin checks the sign-in method, current membership and the app's audience, then returns a session to the app. The app never sees passwords or identity-provider assertions.Employeeopens the appCompany appin your cloudDiakrin sign-inthe brokerIdentity providerwhen SSO is requiredredirectsessionEVERY SIGN-IN IS CHECKEDMethod meets the app’s sign-in policyPerson is still an active memberPerson is in the app’s audienceTHE APP NEVER SEESPasswordsIdentity-provider assertionsSign-in secrets for other apps
Diakrin is the only party that talks to your identity provider. The app receives a session for a checked person, nothing more.

How sign-in works

  1. An employee opens the app address without a session. The app sends them to Diakrin.
  2. If they are not signed in to Diakrin, they sign in with a method your organization allows.
  3. Diakrin checks that the sign-in method meets the app's policy. It then checks that the person is still a member and is in the app's audience.
  4. Diakrin returns them to the app with a session. The app never sees a password or an identity-provider assertion.

If a check fails, the employee sees one plain reason, such as "This app requires company SSO" or "Ask the app owner to add you."

Choose who can open an app

Open the app and select the Access tab. Add people from your organization, a directory group synced from your identity provider, an access group your IT team manages, or turn on Everyone in the organization. Give a person an end date when their access should stop on its own.

Select Save access; the change applies within a minute without a new release. On Google Cloud, Diakrin's Open checks use the new list at once, but Identity-Aware Proxy in front of the app updates on the app's next deployment. Coding tools can do the same with app.audience.read and app.audience.update.

Your company policy can limit who may be added. If saving reports that someone is outside the company audience, ask IT to include them. Removed or disabled accounts lose access automatically. The app's builder and its technical owner can both manage its users.

Set the sign-in floor

Owners and admins set the organization floor under Settings → Organization administration → Sign-in:

  • Allowed methods: company SSO, Google, or email and password.
  • Require two-step verification.
  • Company email domains: leave empty to allow any verified email.
  • Session length: up to 8 hours.
  • Sign in again: how recent a sign-in must be.

Policy floors are organization-level. Projects and apps can only tighten them. An app can require company SSO or a shorter session, but it can never allow a method the organization does not. Admins set an app's policy on the app page.

Sessions and removal

A proxy session already issued stays valid until it expires. Removal takes effect at the next sign-in or within the policy session maximum, whichever is first. Use a 1-hour session for sensitive apps.

Removing someone from your organization ends their recorded app sign-in sessions right away. Removing them from an app's audience blocks their next sign-in.

Apps on Google Cloud

Apps on Google Cloud do not use this sign-in flow. They stay on your private network, behind an internal load balancer with Identity-Aware Proxy, which admits only the app's audience. Employees start from Open app in the console and need a network path to the app, such as your VPN.

Apps published earlier

Apps published before app sign-in was enabled keep using Open app from the console.

Next stepSet up your company cloud →