# Workspace role limits, usage bounds and safer sign-in page tags

31 October 2026. Workspace members can no longer grant more access than they hold, usage reports are whole numbers up to 1,000,000, and the shared sign-in page loads fewer tags.

## Improved

- **Sign-in page:** Behaviour change: BuildBase's shared sign-in address now loads only tags a vendor publishes and you set up with an ID. Those are GA4, Google Ads, Meta, X, LinkedIn, TikTok, Reddit, Microsoft Advertising, Plausible and Ahrefs. Google Tag Manager containers, custom scripts and session recorders (Clarity, Hotjar, PostHog) no longer load there. Every organization's users sign in on that one address, so it runs no code a single organization controls. On your own verified sign-in domain, every tag still loads.
- **Billing:** Behaviour change: each usage report must now be a whole number from 1 to 1,000,000. A fraction or a larger amount answers 400, and nothing is recorded or billed. Send a larger amount as several reports. This holds for single and batch reports, from the SDK, the server SDK or the console API. Before, any amount of 1 or more was taken, and 1.5 was billed as 2.

## Fixed

- **Workspaces:** Workspace members can no longer give anyone more access than they hold. Only the workspace's creator and its admins can make someone an admin. Anyone else cannot change their own role, act on a member who holds more than they do, or grant a permission they lack. This covers changing a member's role, editing the workspace's role permissions, adding a member and inviting one. A refusal is a 403 with a sentence that says why.
- **Workspaces:** Behaviour change: an admin who did not create the workspace can no longer change their own role, and gets a 403. The SDK's member list already keeps that choice switched off. Workspaces on the default roles see no other difference, since only admins hold these permissions there.
- **Email:** In a workflow's Send Email step with Custom Content, merged values now arrive in the HTML as plain text. A name or form answer typed as a link or an image shows as those characters, never as a working link or image. Your own markup around the merge tag is sent as you wrote it. Behaviour change: a step output you merged in as HTML now shows as text.

Source: https://www.buildbase.app/changelog/workspace-role-limits-usage-bounds-and-sign-in-page-tags
