# Tighter access, masked secrets and firm request limits

5 November 2026. Roles and members can no longer reach past their own access, more secrets stay masked, and requests, lists, uploads and webhook replies get firm limits.

## Improved

- **Analytics:** Your web analytics allowance now counts only events from sites you track. Events from a site waiting for review cost nothing, and one IP address counts at most 10,000 events a day. Only your own hostnames and their subdomains are tracked at once now. A sibling such as www.acme.com beside app.acme.com, or a neighbour on a shared host, waits for you to Track or Block it. Automatic tracking also stops at 100 sites.
- **Platform:** Behaviour change: asking a console API list for every row with pagination=false now returns at most 500 rows. The answer's hasNextPage says when there are more, and $page reads the next page. The console reads every page itself. The SDK's FAQ read gets up to 500 questions of a collection.
- **Platform:** Behaviour change: one request may now carry at most 20,000 values, counting keys and list items, or 50,000 for workflows and email templates. It may also hold at most 1,000 values with HTML in them, and 20,000 tags in all. Past any of these it answers 413, too large. A 503 asks you to retry when the server is busy checking HTML.
- **Assets:** Behaviour change: an SVG upload can now be 1 MB at most, down from 5 MB, and hold up to 10,000 elements. A larger file answers 413 with UPLOAD_TOO_LARGE. An SVG too complex to clean in time is refused with a message saying so. SVGs are now cleaned apart from the rest of the server, so a hard one no longer holds up other requests.
- **Webhooks:** A webhook endpoint now has 15 seconds in all to answer, from connecting to the last byte. Before, the 15 seconds counted only silence. BuildBase reads at most 64 KB of the reply, and the status code still decides whether the delivery worked. A workflow's HTTP Webhook step timeout is now a whole-request deadline too.

## Fixed

- **Billing:** Behaviour change: only an owner or admin can now change your Stripe keys on Billing > Credentials. That covers saving, replacing or deleting them, and setting up the Stripe webhook. The secret key spends your money, and the signing secret decides which Stripe events are trusted. A custom role with the credentials permission now gets 401 there, though it can still read the masked keys.
- **Access control:** A member can no longer change or delete a role that holds a permission they lack. The request answers 403 and names those permissions, and the Roles screen shows that role read-only, with the reason. A change to a role now reaches the API keys it limits at once, instead of up to five minutes later.
- **Webhooks:** Behaviour change: rotating a webhook's signing secret now needs permission to update webhook endpoints, not to create them. Rotating a company log stream's secret likewise needs permission to update enterprises. A role that may only add endpoints can no longer rotate one, and an editor who sees the button can now use it.
- **Security:** Saving organization settings now answers a member who is not an owner or admin with only the fields they can read. Before, the answer carried the whole row, Slack webhook URL included.
- **Workspaces:** Workspace members can no longer remove someone who holds more access than they do, and get a 403 that says so. Leaving a workspace yourself is unchanged. With Can invite members set to Admin only, only admins can now revoke an invitation. Resending an invitation now checks its role as sending does. So a member who cannot invite an admin cannot resend an admin invitation either.
- **Email:** Behaviour change: only its maker, an admin or the organization's owner can now open, rename, copy or delete an email template. Anyone else gets 404. A system template can still be read and copied by anyone who may read templates, and only an admin can change it. A template id that does not exist now answers 404, not 200 with null.
- **Workflows:** An HTTP Webhook step's header values are now masked wherever a workflow is read. They show as bullets, plus the last four characters of a long value. Runs and logs keep only the masked form, while the step still sends the real value. Content-Type and similar headers, and values made only of merge tags, stay readable. Saving a step with its mask unchanged keeps the stored value. Behaviour change: an exported workflow carries the masked values, so set them again after importing it.
- **Security:** Reading your SMTP settings back now shows none of the password, only whether one is set. Saving the form unchanged keeps it. Client secrets, social sign-in secrets, the Apple sign-in private key and deploy hook secrets now stay masked on every read. That holds whatever fields a request asks for.
- **Content:** Behaviour change: an API key that reads content now gets each item's creator as a person's id, never a name or email, and no sync hashes. A post's suggested posts now include only published ones, so a draft's title never reaches your live site.
- **Users:** An attribute with Allow public view off now never reaches the person. The SDK's attribute read, both attribute writes and a profile update leave it out, past your tenth attribute too. The console's user editor now stores every attribute by its type, and refuses a value of the wrong type with 400.
- **Workflows:** A value merged into a step's JSON now arrives as data. That covers Update Audience Member's attributes, an HTTP Webhook body or headers, and Send Email's variables. Text a person typed, such as their name, can no longer change the JSON around it. Transform Data no longer reads merge tags inside a value a second time. Behaviour change: attributes that are not valid JSON now fail the step with a clear message, instead of finishing with nothing written.
- **Content:** Behaviour change: a testimonial's company website and a tracking script's privacy link must now be an http or https address. Anything else answers 400. A value saved earlier that is not one is left out of what readers get.
- **Links:** A link destination BuildBase has blocked now stays blocked with any query string, and with or without a trailing slash. Creating a link to a blocked destination, or pointing one at it, answers 400 with the reason. Tracked email links follow the same rule.
- **Email:** Behaviour change: subscribing from a newsletter's archive page now asks for a captcha, a check that a person, not a script, is signing up. It uses your organization's captcha setting, which works with no setup. A form of your own calling the subscribe route must send captcha too, or it gets 400. For the built-in check, fetch one from GET /api/public/newsletters/:orgId/:slug/challenge. The confirmation email now opens with Hello, without the name typed. A burst of sign-ups for one address sends one email.

Source: https://www.buildbase.app/changelog/tighter-access-masked-secrets-and-firm-request-limits
