Frequently Asked Questions

Common questions and answers about using Precog.

Authentication & Security

What is Precog's password policy?

Precog doesn't have a traditional password policy because we exclusively support passwordless authentication and social sign-in methods.

How Authentication Works

  • Magic Link (Passwordless): We send a secure login link to your email. Click the link to sign in—no password needed.
  • Social Sign-in: Sign in using your existing accounts (Google, GitHub, etc.)

Why No Password Policy?

By not storing passwords, we:

  • Eliminate password-related risks - No password breaches, no weak passwords to worry about
  • Defer to trusted providers - Your email provider or social identity provider handles authentication security with their enterprise-grade policies
  • Simplify your experience - One less password to remember and manage

What This Means for Security

Your account security depends on:

  • Your email provider's security (for magic link authentication)
  • Your social identity provider's security (for social sign-in)

Make sure to:

  • Enable two-factor authentication (2FA) on your email account
  • Use a secure email provider with strong security policies
  • Keep your email account credentials safe

For organizations with specific security requirements, we support SAML SSO, which allows you to enforce your organization's authentication policies and centralize access control.

Does Precog support Active Directory integration?

Yes, Precog supports Active Directory (AD) integration through our SAML SSO feature.

How Active Directory Integration Works

Precog integrates with Active Directory via SAML (Security Assertion Markup Language), allowing your organization to:

  • Use existing AD credentials - Users sign in with their Active Directory accounts
  • Centralize authentication - Authentication is handled by your AD infrastructure
  • Maintain security policies - Your organization's AD policies and security controls apply

Do I Need to Use Active Directory Groups?

No, Active Directory groups are optional. While Precog can work with AD groups if you want to use them, they are not required because:

  • Precog has built-in access controls - Our organization roles and workspace permissions provide fine-grained access control
  • Flexible team management - You can manage team membership and permissions directly within Precog
  • No duplication needed - You don't need to replicate your AD group structure in Precog

When to Use AD Groups

You may choose to use Active Directory groups if:

  • You want to automatically sync team membership from AD
  • You prefer to manage all access control through Active Directory
  • You have complex organizational structures already defined in AD

When Built-in Controls Are Sufficient

Precog's native controls are often sufficient because they offer:

  • Organization-level roles - Owner, Admin, Billing User, and Member roles
  • Workspace-level permissions - Individual read/write access control per workspace
  • Flexible management - Easy to adjust as team needs change

For more information about setting up SAML SSO with Active Directory, see our SSO documentation.

Need More Help?

Can't find the answer you're looking for? Check out our Getting Help page for support options.