Projects
Manage multiple Power Apps projects with separate settings, colors, and configurations. Switch between them instantly.
What is the Projects Feature?
If you're building multiple Power Apps (one for HR, one for Sales, one for Operations), each probably has different brand colors and styling. The Projects feature lets you save separate settings for each app and switch between them with one click.
Example:
- HR App - Blue theme (#3B82F6)
- Sales App - Green theme (#10B981)
- Operations - Purple theme (#8B5CF6)
When you switch projects, all your settings (colors, prefixes) change automatically. Every component you generate uses that project's settings.
Why Use Projects?
Faster Workflow
Instead of changing colors every time you switch between apps, just switch projects.
Consistency
Components for the same app always have matching colors and styles.
Organization
Keep track of which settings belong to which app.
Teams
Projects stay personal to your account, also on a Team plan. What a team shares is the team library at /team/library, where members save components for each other.
How to Use
Finding the Project Switcher
The project switcher is in the sidebar of the library. You'll see your current project name with a dropdown arrow.
Creating a Project
- Click the project switcher dropdown
- Click "Create Project" (the dialog is titled New Project)
- Enter a name (e.g., "HR Portal")
- Choose a brand color
- Click "Create Project"
Switching Projects
- Click the project switcher dropdown
- Click on the project you want
- Settings update instantly
- All new component generations use that project's settings
Editing a Project
- Click the project switcher dropdown
- Click the gear icon next to a project
- Update name, color, or prefixes
- Click "Update Project"
Deleting a Project
- Click the project switcher dropdown
- Click the gear icon next to a project
- Click "Delete"
- Click "Yes, delete" next to the "Delete project?" question
Deleting a project removes its settings permanently. Already-generated YAML code is not affected.
Project Settings
Each project stores:
Brand Color
The primary color used for component backgrounds, buttons, and accents. This is the color that appears in your generated YAML.
Variable Prefixes
Each project stores its own nine control-name prefixes (lbl, btn, gal, con, ico, img, txt, var, gbl). Changing them needs Ultra, Team or Lifetime; see the Variable Prefix page.
Best Practices
Name Projects Clearly
Use descriptive names like "HR Portal Production" instead of "Project 1".
Match Brand Guidelines
Get the exact hex color from your company's brand guidelines. Consistent colors across all apps look professional.
One Project Per App
Create a separate project for each Power App you're building. Don't try to share projects between different apps.
Default Project
Your first project is auto-created when you sign up. You can rename it or use it for your main app.
Create a "Sandbox" project for testing and experimenting. Keep your production app projects separate.
Free, Components and Ultra-level
| Feature | Free | Components | Ultra-level (Ultra, Team, Lifetime) |
|---|---|---|---|
| Number of Projects | 1 | 1 | Unlimited |
| Brand Color | ✓ | ✓ | ✓ |
| Quick Switch | ✓ | ✓ | ✓ |
Free and Components accounts get one project. Creating more needs Ultra, Team or Lifetime. See pricing.
How Project Colors Apply
When you generate YAML for a component:
- PowerLibs checks your active project
- Gets the brand color from that project
- Applies it to buttons, highlights, and accent colors in the YAML
- You copy code with your brand colors already applied
You don't need to manually change colors after pasting - they're already correct for your app.
Project settings are stored in the cloud with your account. Switch devices and your projects are there.