mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-13 07:40:59 +00:00
Maurice
d800e64f93
The demo account can look at its Account tab, API keys, MCP configuration, own AI connection and language, but not change them, and the server already refuses each of those writes. DemoLock renders such a section dimmed and out of reach under diagonal stripes in theme tokens, with a small Demo mode badge and one line saying why; useDemoAccountLock decides, on the desktop settings and the phone screens alike (a new pair in feature-pairs.json). Locked: the whole Account tab (profile, password, 2FA, passkeys, deletion), API keys, the MCP card with its tokens and connected apps, connecting an own AI model and the language picker, which shows English. The admin of a demo instance sees everything unlocked, 2FA included, so the old instance wide "Not available in demo mode" line under 2FA and its key are gone from all locales.
17 lines
709 B
TypeScript
17 lines
709 B
TypeScript
import { isDemoAccountEmail } from '@trek/shared';
|
|
import { useAuthStore } from '../../store/authStore';
|
|
|
|
/**
|
|
* Whether the account signed in here is the shared demo account of a demo
|
|
* instance. Every visitor signs in as that one account, so its Account tab,
|
|
* API keys, MCP configuration, own AI connection and language sit under a
|
|
* DemoLock; the server refuses the same writes (`demo-write.ts`). The admin
|
|
* of a demo instance, and every account of a real one, see the sections as
|
|
* they are.
|
|
*/
|
|
export function useDemoAccountLock(): boolean {
|
|
const demoMode = useAuthStore((s) => s.demoMode);
|
|
const email = useAuthStore((s) => s.user?.email);
|
|
return demoMode && isDemoAccountEmail(email);
|
|
}
|