Yekar.AI
Login

Protect the workspace

Add a second step to sign-in, and see where you are signed in

Keep a leaked password from being enough, and keep a forgotten browser from staying signed in.

Get startedRead the docs
Captured from the product Demo workspace
Turn on an authenticator app for any account, require it across the organization, and end any signed-in browser from one list.

What this changes for your team.

Anyone can add an authenticator app as a second step after their password or Google sign-in, with ten recovery codes shown once for a lost phone; an organization can require it of everyone, and a person who has not set one up is held at a setup screen before the workspace opens. Sign-ins are records Yekar.AI keeps on the server: Where you're signed in lists every browser on the account with its system, workspace, network and last use, and ends any one of them. A session unused for three days signs itself out - an organization can shorten that to 15 minutes - and a password change or reset ends every other session. An organization with single sign-on can require it, so a password or Google sign-in no longer opens the workspace at all.

How it works in practice.

  1. 01

    Scan the code under Settings → Account → Two-factor sign-in, confirm with the app's number, and save the recovery codes.

  2. 02

    An Owner or Admin turns on Require two-factor sign-in, Sign out after inactivity or Require single sign-on under Settings.

  3. 03

    Review Where you're signed in and sign out any browser you do not recognise.

What you can plan around.

What to expect, including limits that matter to your team.

The authenticator key is stored encrypted and recovery codes only as hashes; wrong codes are limited like wrong passwords, a code is accepted once, and replacing the codes or turning the step off needs a current code.

Requiring two-factor or single sign-on is applied where a membership is bound; the requirement is audited, and turning on single sign-on ends every session that did not come through the identity provider.

A browser stays signed in only while its session record exists; signing one out deletes that record, and no code, key or address reaches a log or audit row.

Complete the operating path

View all capabilities
Protect the workspaceProtect the keys to the workspace

Store the credentials people sign in with so that a copy of the database does not become a set of working logins.

Protect the workspaceContain where a tool can send data

Limit each integration to the destinations it declares, so a compromised tool has nowhere to send your data.

Make actions accountableMake every external action accountable

Make every integration call act as a deliberate team, user, platform, or customer identity.

Bring one real process

See how Yekar.AI fits the way you work.

Start with a job your team already owns, plus the tools and decisions around it.

Get started