Do portal visitors need a BeeBlu account?
No. Public role-aware portals are designed for external consumers and do not require Supabase authentication.
Is portal content private?
Do not assume so. Portal routes and the AI-context endpoint are public. Publish only approved brand material.
Which operational roles are supported?
The current portal invite implementation supports marketing, developer, design, agency, and AI roles.
How long does a portal invite last?
The current backend creates portal invites with an expiry 90 days after issue. This may change during early access.
What can I export?
The brand-system export area supports CSS variables, W3C DTCG JSON, and PDF where implemented. Portal and role-specific exports vary by surface.
Does BeeBlu connect to Figma?
Yes. The current application can validate a Figma personal access token and file key, then push colour, typography, spacing, radius, and shadow tokens to a Figma Variables collection. Figma’s Variables API requires a qualifying paid Figma plan.
Does BeeBlu replace a design system?
No. BeeBlu is intended to operationalise and distribute brand and design-system foundations across additional teams, partners, and tools.
What does the AI-context endpoint contain?
The current public endpoint can return published brand name, colours, typography, spacing, prompt guidance, and governance metadata.
Does BeeBlu test colour accessibility?
The Brand System accessibility area provides a WCAG 2.2 contrast review across the configured palette, including normal text, large text, and UI or icon modes.
Is pricing final?
No. BeeBlu is currently presented as invitation-based early access. Pricing, billing, cancellation, and refund terms still need confirmation.