Managing multiple projects in KOS Studio becomes essential when working across different product lines within your organization. This comprehensive guide explains how to switch between projects efficiently, helping you maintain organized workflows and streamlined development processes.
What Are KOS Studio Projects?
KOS Studio projects serve as organizational containers that separate different product lines within your KOS Organization. Each project maintains its own isolated environment containing:
- Artifacts and images specific to that product line
- Hardware profiles configured for project requirements
- Device configurations and releases
- Team member access controls and permissions
This project-based structure offers several key advantages:
- Project lifecycle management: Archive completed projects without affecting active work
- Improved organization: Keep different product lines completely separate
- Enhanced security: Control team access to specific projects
- Reduced clutter: Focus only on relevant artifacts and configurations
Switch projects
Follow these simple steps to switch between your assigned projects:
- Access the KOS Studio Menu
- Locate the KOS Studio menu button in the top-left corner of the interface
- Click on the menu button to open the dropdown options
- Select Switch Projects
- From the dropdown menu, click on “Switch Projects”
- This action opens the project selection modal
- Choose Your Target Project
- Review the list of available projects in the Select Project modal
- You’ll see both public and restricted projects assigned to your account
- Select the project you want to switch to from the displayed list
- Confirm the Switch
- Click the “Switch” button to change to your selected project
- The interface will update to reflect the new project context
What Happens After Switching Projects
Once you successfully switch to a different project, you’ll notice several changes in your KOS Studio environment:
- Updated image library: Only images associated with the selected project appear
- Filtered hardware profiles: Hardware configurations specific to the current project
- Project-specific artifacts: Relevant files and components for the active project
- Contextual releases: Device releases pertaining to the selected project
Project Management Best Practices
Organizing Multiple Projects
When working with multiple KOS Studio projects, consider these optimization strategies:
- Use descriptive project names that clearly identify the product line or purpose
- Regularly archive completed projects to maintain a clean workspace
- Document project-specific configurations for team collaboration
- Establish clear project access policies for team members