Session length

Use this article to understand how long Clipido keeps you signed in, how admins change session length, and why you may need to sign in again before the session expires.

Clipido uses short-lived access tokens plus a longer-lived refresh session. While your session is valid, Clipido refreshes access automatically in the background. When the session expires, you must sign in again.

Default session lengthCopy Anchor Link

New workspaces default to "14 days" of signed-in session time (expireClubSessionAfter: 14d).

During an active session:

You do not need to sign in every 15 minutes. The 15-minute access token is internal; Clipido renews it using your refresh session until the session length expires.

Change session length in the workspace appCopy Anchor Link

Workspace admins can change session length under Settings → Club:

1. Open Settings → Club.

2. In "Session expiration", open Session lifetime.

3. Choose a value:

   Option	Label
   10 days	"10 days"
   14 days	"14 days"
   30 days	"30 days"
   90 days	"90 days"

4. click Save changes.

The section description reads "How long club members stay signed in before re-auth is required."

Change session length in Admin CenterCopy Anchor Link

Organization admins can also set session duration per deployment:

1. Open Admin Center → "Deployments" → your deployment → "Advanced".

2. Under "Session Duration", choose:

   Option	Label
   1 day	"1 day"
   7 days	"7 days"
   12 days	"12 days (recommended)"
   30 days	"30 days"
   90 days	"90 days"

3. Save the deployment settings.

The field description reads "How long users stay logged in before needing to re-authenticate."

Both surfaces update the same underlying setting (expireClubSessionAfter). Use whichever admin path your organization prefers.

When you are signed out earlyCopy Anchor Link

You may need to sign in again before the configured session length if:

• An admin shortened session length after you signed in (existing sessions may not extend automatically)
• You cleared browser cookies for the hostname
• You switched between the default subdomain and a custom domain (sessions are host-specific)
• You signed out manually from Settings → Profile
• Auth rate limiting blocked repeated failed attempts ("15 requests per minute" on auth endpoints)

Signing in on a custom domain does not reuse a session from {slug}.clipido.app. Sign in on the hostname you plan to use.

Staying signed in across devicesCopy Anchor Link

Each browser and device holds its own session cookies. Signing in on your laptop does not sign you in on your phone. "Connected accounts" under Settings → Profile (Google or Microsoft) speed up sign-in on each device but do not extend session length.

Security noteCopy Anchor Link

Longer sessions (30 or 90 days) are convenient for trusted staff devices. Shorter sessions (1, 7, or 10 days) reduce risk on shared computers. Session cookies are httpOnly and cannot be read by page JavaScript.

For platform-level security details, Clipido documents httpOnly cookies, TLS, and token lifetimes in the Security and Privacy collection.

Related articlesCopy Anchor Link

• Data retention
• Data protection
• Sign-in problems on a custom domain