Managing Companies

In the WPCloset ecosystem, Companies serve as your primary organizational tool. While a Site record represents a single technical instance of WordPress, a Company record represents the logical entity—such as a business, a specific department, or a project suite—that owns or utilizes those resources.

The Role of a Company Record

A Company record acts as a central hub that binds together your plugins, themes, environments, and sites. It provides a structured way to manage resources so that your dashboard remains organized and professional as your portfolio scales.

Managing by Company provides:

• Logical Isolation: Keep the assets and staging sites for “Project A” completely separate from “Project B.”
• Centralized Identity: Assign logos and metadata at the company level to help identify groups of assets at a glance.
• Efficient Governance: Control which plugins and themes are available to specific clusters of sites by anchoring them to a shared company identity.

Creating and Branding a Company

When you create a Company, you are setting up the “Vault” where all related WPOps activities for that entity will live.

Company Identity

The Company Name should be the primary identifier for the entity you are managing (e.g., “Internal Marketing Team,” “Blue Horizon Agency,” or “Academic IT Department”). This name appears throughout the dashboard to help you navigate your different projects.

Visual Branding (The Logo)

You can upload a Company Logo to each record.

• Purpose: In a dashboard managing dozens of entities, visual cues are vital. The logo helps you and your team quickly distinguish between different organizations without scrolling through text lists.
• WPOps Impact: This logo is used within your WPCloset dashboard to provide a high-end, organized interface that reflects the professional nature of your repository.

Resource Relationships

A Company is the anchor for your technical infrastructure. From the Company view, you manage three critical pillars:

1. The Fleet (Sites)

A Company can contain multiple Sites. For example, a single Company record might group a local.test site, a staging-site.com instance, and the final live-production.com URL. This grouping allows you to monitor the connection status of an entire project fleet in one place.

2. The Infrastructure (Environments)

Environments (such as Production, Staging, or QA) are defined at the company level. This allows you to mirror the real-world workflow of the entity you are supporting. One company might only need a “Live” environment, while an enterprise department might require a complex pipeline.

3. The Library (Assets)

Your private plugins and themes are assigned to a Company. This creates a Private Marketplace exclusive to that entity. This ensures that a custom plugin built specifically for your “HR Department” never accidentally appears as an update for your “Public Marketing” sites.

Use Cases for Company Management

The Company structure is designed to adapt to your specific management style:

• Individuals & Professionals: Group all your personal tools and hobby projects under a single “My Portfolio” company to keep your workspace clean.
• Agencies: Create a unique Company for every client. This provides a clean “separation of concerns,” ensuring that client-specific assets and sites never mix.
• Enterprise Teams: Use Companies to represent different internal departments or product lines. An IT department can manage a “Core Infrastructure” company for shared university tools and separate companies for specific departments with their own unique themes.

Best Practices

• Granular is Better: Avoid using a single “General” company for everything. Creating distinct records makes it much easier to audit activity, rotate keys, and manage deployments as you grow.
• High-Quality Logos: Using clear, recognizable logos makes the dashboard more intuitive for your team and provides a more polished experience when demonstrating the portal to stakeholders.
• Periodic Audits: Regularly review the “Sites” tab within a Company to identify and decommission old development environments that no longer require access to your repository.