Sign in & access

The admin center lives at https://admin.zeeker.com. Sign-in is the same Zeeker identity used everywhere — there's no separate admin account.

Sign in

1. Open https://admin.zeeker.com.
2. Click Sign in. You're redirected to https://id.zeeker.com.
3. Pick your sign-in method (email + password, Google, Apple).
4. After verifying, you're returned to the admin center.

If this is your first time, the admin center will offer to either Create a new community or Request access to an existing one.

How access is granted

You get admin access in one of three ways:

1. You created the community. You're the owner with full powers.
2. Another owner / admin invited you. They sent an invite from their Members tab; accepting puts you in the role they assigned (admin or moderator).
3. You requested to join an existing community and an owner approved + promoted you.

Without access to any community, the admin center shows a marketing page directing you to either create a community or contact an owner.

Switching communities

If you're an admin / moderator across multiple communities, the community switcher at the top-left of the sidebar lists them all. Pick one to swap context.

Leaving Admin View preserves the last selected managed community for the next time you explicitly enter Admin View. Signing in still opens regular Social by default; logout or revoked access clears the saved admin context.

Opening the Admin Center, restoring its last selected community, or switching communities there does not enable Admin View in Social, Chat, or any other Zeeker app. Admin View changes only through an explicit control in the app where it is used.

Current apps record that control as a versioned explicit intent. Old, unversioned Admin View cookies from earlier Admin Center releases are discarded during app startup, so revisiting Admin Center cannot revive or renew them. A current Admin View choice remains active until you turn it off, sign out, or lose access.

The switcher remembers your last active community across sessions, including across browsers when you're signed in.

Product feature access

Some community products, including Embed, can require a separate feature entitlement even when you already administer the community.

Selecting Deploy opens the Embed Center for the active community. Navigation alone never submits an access request. If Embed is restricted, the Embed Center shows why, lets you add an optional reason, and provides an explicit Request access action. After submission, the screen shows the pending state and prevents duplicate requests.

Access approvals and rejections are privileged actions. They require a current server-side sign-in; an expired session sends you through sign-in again instead of silently completing the action with a stale page.

Two-factor authentication

We strongly recommend enabling 2FA from https://id.zeeker.com → Settings → Security. Once enabled, every admin center sign-in will require a TOTP code (Authenticator-app or hardware key).

For high-privilege accounts (community owners with large communities), 2FA is required — we'll prompt you to set it up on sign-in.

Sessions

The admin center session lives in an httpOnly cookie scoped to *.zeeker.com and lasts 30 days. You can revoke active sessions from https://id.zeeker.com → Settings → Sessions.

Losing access

If you lose access (e.g. the owner removes your admin role), the admin center bounces you back to the marketing page. You can still use zeeker.com normally — admin access is independent of your social-app account.