BeeBlu public portals are designed for people who need to use the brand without working inside the internal BeeBlu application.
Create an agency invite
Open Portal Invites and enter the external collaborator’s email address. Choose the operational role that best matches the work:
- marketing;
- developer;
- design;
- agency;
- AI.
BeeBlu creates a role-scoped link and sends it through SendGrid. Current invite records expire after 90 days unless the implementation changes.
What the role changes
The role affects which portal sections and actions are emphasised. An agency may need approved assets, guidelines, and downloads, while a developer needs tokens, code-oriented exports, and implementation context.
The underlying brand kit remains the same.
Portal access is public-facing
Portal visitors do not need an internal BeeBlu account. Treat portal content as publishable material:
- do not include confidential campaign plans;
- do not upload personal data into guidance;
- review asset licensing;
- hide draft or internal-only tokens;
- verify the portal before sending an invite.
Resend or revoke
Portal Invites lets brand owners review sent invitations, resend a link, or revoke access by deleting the invite record.
If an agency engagement ends, revoke the invite and review any exported packs that remain outside BeeBlu. Revocation cannot recall files that have already been downloaded.