Sign in to your workspace
Sign in here with your staff account. No browser login is required.
Need access or a password reset? Contact your workspace owner.
← Back to the websiteKeep clients, conversations, and calendars moving from one organized workspace.
Built for the people behind The Trade Show Calendar.
Sign in here with your staff account. No browser login is required.
Need access or a password reset? Contact your workspace owner.
← Back to the websiteUse a named key for the test workspace during an active development window.
Checking development access…
Development-key sessions are read/review only. Use ordinary owner sign-in to manage development access, change accounts or protected settings, publish, activate services or grant customer permissions.
Use dev-assistant and your saved key at the browser’s private preview challenge, then choose Continue with development access. Ordinary sign-in remains available.
A workspace owner using ordinary sign-in can open Team & access and enable a 1–24 hour window; the default is 12 hours. Save the first key privately when it appears. Later windows reuse that saved key.
Open the test preview. At the browser’s Private preview challenge, use dev-assistant as the username and your saved development key as the password. On the staff sign-in page, choose Continue with development access. That button appears only after the server accepts the outer development credential.
Disable development access ends key access and invalidates development sessions. It keeps the saved key, assistant account, passwords and ordinary access. Enable a later window to use the saved key again; sign in again to create a fresh development session.
Staff sessions have a 12-hour absolute limit and a 4-hour idle limit. A development window ending or being disabled can end key access earlier. This does not keep you permanently signed in. A browser may remember Basic credentials; close the private preview browser context if necessary before choosing ordinary credentials.
It provides read/review access plus sign-in and sign-out. It cannot edit protected settings, manage development mode, change accounts, publish, activate services or grant customer permissions. Use ordinary owner sign-in for those operations. A development key does not sign into a customer’s calendar console or prove calendar ownership.
A disabled or expired window needs an ordinary owner to enable it. If you did not save the first key, ask the owner; there is no reveal or rotate action in this candidate. Use the ordinary login or existing owner assistance path for lockouts. A key cannot repair an unavailable preview or bypass its server guards.