The Problem

SharePoint pages sit still.

Out of the box, a SharePoint page is a place where content waits to be found — not a place where work gets launched.

• No native way to add a branded action button to a page
• Links to Power Automate flows, forms, or resources are buried in text
• Site owners hack buttons together with HTML embed web parts and broken styling
• No way to target different buttons to different audiences
• Restricted resources either 403 silently or just don't appear

The result: pages that describe work instead of launching it.

The Solution

A configurable action layer.

ButtonBuilder is an SPFx web part that lets site owners drop styled, branded action buttons onto any SharePoint page — without writing a single line of code.

• Colors, icons, labels, sizing — all controlled through the property pane
• Launches workflows, opens forms, navigates to resources, triggers custom URLs
• Audience targeting via Microsoft Graph — different buttons for different groups
• Restricted-view fallback for users without access
• Respects your SharePoint theme tokens out of the box

Content still sits on the page. But now the action sits next to it.

Feature · Styling

Full visual control, zero code.

Every visual knob you'd expect — and a few you wouldn't — exposed through the property pane:

• Colors — fill, text, border, hover, pressed
• Icons — Fluent UI icons or upload custom SVG
• Shapes — rectangle, rounded, pill, custom SVG path
• Effects — gradients, shadows, borders, transitions
• Sizing — small / medium / large, or custom width/height
• Theme tokens — bind to SharePoint theme colors so buttons re-skin automatically
• Behaviour — same tab / new tab / no-link (decorative)

Brand consistency without a designer in the loop.

Feature · Audience Targeting

Different buttons, different people.

ButtonBuilder reads group membership via Microsoft Graph and conditionally renders buttons based on who's viewing the page.

• Show a button to specific AAD groups or SharePoint groups
• Hide it from everyone else — no flicker, no visible gap
• Restricted-view fallback — show an "access denied" message, a "request access" link, or a custom message instead of nothing
• Useful for safety portals, exec landing pages, ops dashboards, contractor-only resources

One page, many experiences. No duplicate sites.

Who It's For

Built for portal owners who ship.

• Site owners tired of building Flow links into plain text
• Safety & ops portals where the right button needs to reach the right team
• Restricted document libraries that need a gated "request access" button
• Executive landing pages where polish matters more than coding time
• Branded intranets that need to look like the brand, not like SharePoint

If your page tells people what to do, ButtonBuilder lets them do it.