Settings & Customization
Master the PowerLibs settings panel to create components that perfectly match your brand and requirements.
Overview
The Settings tab is where PowerLibs components come to life. Every component in the library has a Settings tab; components you saved yourself in Custom YAML do not. The editor groups its options by what they change: text, list items, on/off options and, where available, colours.
Accounts with a paid plan other than the old Components subscription can change every setting. Every other account sees the real editor locked, with an Unlock button (accounts on the Components subscription also see "Settings customization requires Ultra."). See pricing for what each plan includes.
Current Setting Types
Content & Text
The most common settings you'll find:
- Text Content - Change what text is displayed in buttons, labels, titles
- Button Labels - Customize action button text
- Titles & Headings - Update component titles and descriptions
- Placeholder Text - Set form field placeholders
Functional Settings
Settings that change how components work:
- Add/Remove Elements - Add more tabs to tab bars, more buttons to button groups. Each editor has a maximum, for example six segments on the Button Group
- Element Configuration - Name tabs, configure menu items
- Behavior Options - Toggle features on/off
- Style and Size Options - Pick a style, variant or size where the editor offers one
Theme & Colors
Some components offer basic theming:
- Color Fields - Where a component's editor has colour fields, pick a colour there; it wins over the global Brand Color. Where such a field has a Use brand color link, that link takes the component back to the Brand Color
- Light/Dark Theme - Switched with the sun/moon button in the card header, not in Settings. Dark theme YAML on paid components needs a paid plan
Most editors change content and behaviour rather than detailed styling. Text sizes, spacing and borders can only be changed where a component's own editor offers a field for them.
Advanced Customization
Global Settings Integration
Global settings feed into every component's preview and generated code. Open them from your avatar menu, then Settings (the entry is shown to accounts that have, or had, a paid plan other than the old Components subscription):
- Profile Information - Your name and your project name
- Brand Color - One colour used by every component; the default is #3B82F6
- Font - Written into every generated YAML. Choose one of the 14 Power Apps fonts (the default is Open Sans) or Use app theme, which leaves the Font property out so your controls inherit App.Theme.Font
- Brand color in copied YAML - Fixed color (the default) writes the color itself, for example
RGBA(59, 130, 246, 1). AppTheme.BrandPrimary writes a reference to the theme that PowerColors exports, so changing that one formula recolors every pasted component, including hover and pressed states that use the full brand color. Paste the theme into App.Formulas first, or the pasted controls show formula errors. Light tints of the brand (a soft hover background, for example) and shades worked out from it stay fixed, because Power Apps cannot change the opacity of a theme color. - Variable Naming - Nine prefixes for generated control and variable names: lbl, btn, gal, con, ico, img, txt, var, gbl. Custom prefixes only apply with a paid plan other than the old Components subscription; everyone else gets the defaults
Click Save Changes to store them; the page then reloads so every preview and every copied YAML uses the new values.
Any signed-in account can also set the Brand Color from PowerColors: under Use it in your components, click Use as my brand color. The switch below that button turns AppTheme.BrandPrimary on or off.
Your preferences also store a default theme (light or dark, applied to the website when you sign in) and a fill-parent flag; neither has a control in the Settings popup today. The project name, brand colour, font, colour mode and prefixes you save in Settings belong to your active project, so each project keeps its own: see Projects and Variable Prefix.
Global settings cannot be overridden per component. A component only has a colour of its own where its editor shows a colour field, and a colour picked there wins over the Brand Color.
Your Changes Are Kept
Changes you make on the Settings tab are saved in your browser, per component, about half a second after you stop typing. When you come back or reload the page, the card says "Restored your unsaved changes" and shows a Reset link. The draft lives in this browser on this device only; it is not stored with your account.
Reset to Default at the bottom of the Settings tab (or the Reset link in that notice) puts every setting of the component back to its default and deletes the draft.
Share a Configured Component
The link button in the card header, next to the sun/moon button, copies a link that opens the page at this component. Once you have changed a setting, the link also carries your settings, and whoever opens it sees "Showing a shared configuration" above the component. On a phone the button only appears after you have changed a setting.
- A very large configuration does not fit in a link; you then see "This configuration is too large to share as a link."
- For safety, text from a link loses its line breaks and double quotes, and anything that looks like a formula is dropped, so a link cannot add formulas to the YAML you copy.
- A shared link wins over a draft the recipient already has for that component.
Component-Specific Examples
Each component type has unique functional settings:
Navigation Components:
- Text Content - Change app title, user name, menu labels
- Menu Items - Add/remove navigation items, configure labels
- User Profile - Show or hide the user profile area on Navigation Bar, NavBar with Tablist, Mega Menu Navbar, NavBar with Scrollable Content and Sidebar with Navbar
- Logo - Show or hide the logo, or paste your own SVG logo, on the navigation bars that offer it
Tab Components:
- Add/Remove Tabs - Increase or decrease number of tabs
- Tab Labels - Name each tab (Home, Profile, Settings, etc.)
Button Components:
- Button Text - Change what the button says
- Size and Style - Most buttons have a Size (Small, Medium or Large); some also have a Style
- Add item - The Button Group lets you add segments, up to six
Customization Workflow
1. Start with Defaults
Every component loads with sensible defaults that work well in most Power Apps.
2. Apply Global Theme
Use global settings to establish your brand colour and font across all components.
3. Fine-tune Individual Components
Adjust specific components to meet unique requirements or design needs.
4. Test in Power Apps Studio
Paste the YAML into Power Apps Studio and check the result there. The preview has no device or screen-size switcher.
Best Practices
Content Consistency
- Use consistent language and terminology across components
- Keep button labels clear and action-oriented
- Maintain consistent naming for similar elements (tabs, menu items)
- Test all text content for clarity and length
Functional Organization
- Group related tabs or menu items logically
- Don't add too many tabs or buttons (3-7 is optimal)
- Use descriptive names that users will understand
- Consider the user's workflow when organizing elements
Theme Selection
- Choose a consistent theme (light/dark) across your app
- Test your chosen colors in the actual Power Apps environment
- Consider your organization's brand colors when available
- Ensure good contrast for accessibility
Testing & Validation
- Always test components in Power Apps Studio after customization
- Verify that all text fits properly in different screen sizes
- Check that functional elements (tabs, buttons) work as expected
- Test with real data when possible
Troubleshooting Common Issues
Settings Not Applying
- Settings can only be changed with a paid plan other than the old Components subscription; other accounts see the editor locked with an Unlock button
- A colour chosen in the component's own Settings wins over the global Brand Color; use the Use brand color link next to the colour field, where there is one, or Reset to Default to go back to the brand colour
- Verify that you're in the correct settings section
- Reload the page; your changes are kept in the browser and restored after the reload
Colors Not Displaying Correctly
- Colour fields take a hex value such as #3B82F6
- Ensure sufficient contrast ratios
- Test in both light and dark themes
- Verify Power Apps color compatibility
Responsive Issues
- Test components at different screen sizes
- Ensure text remains readable at smaller sizes
- Verify touch targets are adequately sized
What's Next?
Once you've customized your component, learn how to export YAML code and import it into Power Apps Studio.