Schools and nurseries

Arbor customisation: what you can change.

School office teams work through registers, timetables and lists throughout the day. Tweaksy lets them request clearer labels and more readable tables on Arbor's browser pages.

No card needed. Try 8 standard builds a month on our sample office page with one computer. A paid plan is needed for your own work sites, from £9.99 a month for two computers. Desktop Chrome. Cancel any time. See the office demo first.

Ideas to try

Small requests for a clearer working day

Start with information already visible on your page. These examples are possible requests; check the result in the preview before keeping it.

  • 01

    Make the class name and session date larger above this register

    Keep the context clear while working through the current register.

  • 02

    Increase spacing between the rows in this pupil list

    Make adjacent rows easier to distinguish on a crowded screen.

  • 03

    Use stronger contrast for the attendance codes already shown

    Read the displayed codes more easily without changing any marks.

  • 04

    Keep the column headings visible in this timetable table

    Follow the day and period labels while scrolling.

Ready-made changes related to these ideas

These general browser tools use the page elements your software exposes. Read their requirements and preview them on a suitable screen.

Custom Arbor screens, automations or a developer?

The right approach depends on what you want to change. Use Arbor settings for features the product already provides, and Tweaksy for small changes on an accessible browser page.

Browser customisation

Modify the screen you work with

A request such as “Make the class name and session date larger above this register” starts with information already visible. Tweaksy builds the change on that page for you to preview, then you can approve it for matching screens on your account.

Workflow automation

Know what needs the platform

If you need Arbor automations to run when no browser is open, update records or move data between systems, look at the product's built-in workflows or supported integrations. Tweaksy's saved screen changes apply in Chrome when a matching page is open; they are not a background integration service.

Developer work

Connect systems or add new capabilities

For a custom Arbor integration, ask the provider which APIs and developer options are available for your version and plan. A developer may be needed for data exchange, server-side logic or features outside the existing browser page.

Explore Arbor's official options ↗

A small change, ready for your team

  1. Choose one screen

    Open an accessible Arbor web page in desktop Chrome. Start with a simple change to text, spacing or a visible list.

  2. Describe and preview

    Describe the change in your Tweaksy account. Build it with the extension and check the preview in the original tab.

  3. Approve and share

    Approve the exact version to enable it. Your other logged-in computers receive it when they sync, on matching pages.

Questions about Tweaksy and Arbor

Which Arbor screens can I use?

These ideas concern Arbor pages available to you in desktop Chrome. They do not enter attendance marks, change school records or alter who can view pupil information; Arbor mobile apps are outside scope.

Can I modify Arbor without a developer?

For a small change to an accessible browser screen, you can describe what you want in plain English and preview it with Tweaksy. Custom Arbor integrations, new stored fields and background workflows need the product's own configuration or developer tools. Start with the browser requirements above.

Are these ready-made integrations?

These are ideas for changes to request on a browser page, not prebuilt Arbor integrations. The result depends on the page layout, information currently visible and your browser permissions. Preview each change on your own screen.

What information is used to build a change?

Creating a change uses your request and relevant page details, processed by Tweaksy and its AI service. Automatic filtering reduces sensitive information, but visible personal or business details can still be included. The privacy policy explains who handles your data and your choices. Try a demo or a page without confidential information first.

Does this replace Arbor settings or permissions?

No. Tweaksy can adjust a page in your browser; it cannot add server-side fields, retrieve records you cannot access or change account permissions. Review any change affecting page behaviour before approving it.

What happens when Arbor changes its layout?

A saved change may need rebuilding after a software update. Check it on the updated page, switch it off if needed and preview a revised version before approving it again.

Can I use it with colleagues?

Each desktop Chrome using Tweaksy needs the extension and a login to your Tweaksy account, within your plan's computer allowance. Approved changes sync to those computers. Managed browsers may require your administrator to allow the extension.

Start with one screen and one useful change.

Try a clearer label, a larger reference number or a tidier list. Preview it, then decide what to keep.

No card needed. Try 8 standard builds a month on our sample office page with one computer. A paid plan is needed for your own work sites, from £9.99 a month for two computers. Desktop Chrome. Cancel any time. See the office demo first.

Product names belong to their respective owners. Tweaksy is an independent product made by OptiCab Ltd. Listing a product does not imply a partnership, endorsement or verified compatibility with every screen.