Workspace settings

Workspace Settings contains configuration for the selected workspace. The settings you can change depend on your workspace role and plan.

General

General settings contain the workspace name and lifecycle controls.

Changing the workspace name does not silently change its slug, existing short Links, QR destinations or historical Analytics.

Workspace identity

If you belong to more than one workspace, Bytes can show a small workspace icon beside the workspace name in the switcher and workspace lists.

Workspace Identity:

• is available on every plan
• is a simple recognition mark, not a theme
• is separate from the Workspace Brand Kit
• does not recolour the Bytes application
• falls back to an initial when no icon is uploaded

Owners and administrators can upload, replace or remove the workspace icon. Other workspace members can see the effective icon where they can access that workspace.

For best results, use a roughly square PNG, JPEG or WebP image no larger than 5 MB.

Members and ownership

Owners and administrators can manage workspace access from the Members section.

Depending on your role, this includes:

• inviting people
• changing permitted member roles
• removing workspace access
• reviewing pending invitations
• transferring ownership safely

Removing somebody from a workspace does not delete their Bytes account.

Ownership transfer is an explicit workflow. Bytes will not allow a normal role change or leave action to orphan a workspace.

Billing & Plans

Billing & Plans shows the current workspace plan and available plan actions.

Starter, Pro and the Business baseline are available with monthly and annual self-service pricing in GBP, USD and EUR where the application offers Checkout. Enterprise remains a bespoke commercial enquiry rather than a generic self-service Stripe purchase.

The plan and currency shown at Checkout come from the Bytes commercial catalogue. Regional prices are deliberate catalogue prices rather than automatic currency conversions.

Plan entitlement remains controlled by trusted Bytes billing state. Returning from Stripe Checkout does not by itself grant a paid plan. Bytes waits for trusted billing state before treating the workspace as upgraded.

If your workspace already has a paid Stripe subscription, use only the plan-change actions that Bytes explicitly makes available for that billing state. Do not create a second subscription as a workaround for changing an existing paid plan.

Catalogue prices are shown excluding applicable taxes. For a new self-service purchase, Stripe Checkout can calculate tax from the billing location and the tax registrations that apply to the sale. Checkout may also ask for a business tax ID where relevant. The Checkout page is the authority for any tax amount actually calculated and collected at purchase time.

Availability of a GBP, USD or EUR catalogue price does not itself mean that tax is collected in every country or US state. Tax collection depends on the applicable tax rules and Jawwws' active registrations.

Customer-facing invoice and payment-history work is tracked separately. Do not rely on Workspace Settings as a complete invoice archive unless that capability is visible in your workspace.

Brand Kit

The Brand Kit tab stores reusable output defaults for the workspace.

Brand defaults

On Pro and above, Brand Kit can store:

• a primary logo
• a primary brand colour
• a secondary brand colour
• fallback text for supported output surfaces

These defaults can be used by supported shared-page, print and report outputs.

Brand Kit does not recolour the normal Bytes application shell, workspace switcher, admin screens or security screens.

When fallback text is blank, Bytes uses the workspace name where text is needed because an image cannot be shown.

Resetting the Brand Kit colour fields uses the normal Bytes blue (#0E9CE6) and orange (#FF764C) defaults.

QR defaults

QR branding follows a separate entitlement model:

Plan	QR appearance
Free	Safe black and white
Starter	Safe black and white with an optional centre mark
Pro and above	Reusable single-colour Brand Kit treatment and per-export custom colour controls

A configured QR centre mark is treated as a single-colour mark when Bytes generates a QR code. Its visible pixels are recoloured to the effective QR foreground colour. An uploaded blue mark, for example, becomes black in a safe monochrome QR or red when the effective QR foreground is red.

Transparent and near-white negative space is preserved so the mark remains legible.

Use a roughly square PNG, JPEG or WebP image. Transparent PNG or WebP normally gives the cleanest centre-mark result. Brand Kit images are limited to 5 MB.

QR safety still wins

Brand Kit is a reusable preference, not permission to create an unsafe QR code.

When a QR is exported, Bytes first resolves the intended use, physical size, scan distance and QR Output Profile. The selected appearance is then applied only inside that safe envelope.

If a requested appearance is not safe for the selected output, Bytes blocks or falls back rather than silently weakening QR reliability.

See QR codes for the export workflow.

Editing from QR Export

Workspace owners and administrators can open a focused Edit Brand Kit panel directly from QR Export.

Changes saved there update the reusable workspace Brand Kit. Closing the editor returns to the export without losing the export context.

A member who can use the workspace's effective Brand Kit does not gain permission to edit it.

Downgrades

When a workspace moves to a plan that does not include a stored Brand Kit capability, Bytes preserves the stored settings and assets but does not apply gated features while the lower plan is active.

Workspace lifecycle

Workspace lifecycle actions are deliberately different:

• Leave workspace removes your membership
• an empty, dependency-free workspace can be removed when the product allows it
• a used workspace is archived rather than treated as disposable history
• an eligible customer-archived workspace can be restored

Archiving a workspace does not silently rewrite its existing public Links or QR destinations.

Owners cannot leave a continuing workspace without first resolving ownership.

Developer API

Developer API access is available on every plan.

API keys belong to one workspace and inherit that workspace's access and limits.

Business workspaces can also configure customer-managed outbound Workspace Webhooks.

Roles and access

Only people with the appropriate workspace role can change shared configuration.

Some settings remain visible or usable to members even when management is restricted. Bytes enforces workspace access and management permissions server-side.

Sensitive information

Do not paste API keys, webhook signing secrets, authentication cookies or other credentials into support messages, public documents or screenshots.