Organizations

WindowSill supports multi-organization membership, allowing users to create and join multiple organizations. For larger enterprises, administrators can create sub-organizations to manage different teams, departments, or regions under a unified billing structure.

Note

Organization features require WindowSill Pro. The Microsoft Store version does not support organization management.

Organization Structure

Users can belong to multiple organizations simultaneously. Each organization operates independently with its own configuration and members.

For enterprises needing hierarchical management, administrators of a parent organization can create sub-organizations. This enables:

Departmental separation (e.g., Engineering, Marketing, Sales)
Regional management (e.g., EMEA, APAC, Americas)
Project-based isolation
Subsidiary or acquired company integration

graph TD
    Parent[Contoso Inc.<br/><i>Parent Organization</i>]
    Sub1[Engineering<br/><i>Sub-Organization</i>]
    Sub2[Marketing<br/><i>Sub-Organization</i>]
    Sub3[EMEA Region<br/><i>Sub-Organization</i>]
    
    Parent --> Sub1
    Parent --> Sub2
    Parent --> Sub3

Per-Organization Features

Each organization—whether parent or sub-organization—manages its own:

Feature	Description
Members	Users belonging to that specific organization
Domain Verification	Verified email domains for auto-provisioning
Join Policies	Rules for how users can join (invitation-only, verified domain, open)
Device Tokens	Authentication tokens for silent deployment
WindowSill Settings	AI providers, extension policies, privacy settings
AI Usage Statistics	Usage metrics and analytics for that organization

Administration

Admin Inheritance

Administrators of a parent organization are automatically administrators of all its sub-organizations. This inheritance cannot be overridden—parent admins always have full access to sub-organizations.

Sub-organizations can have their own dedicated admins who only have access to that specific sub-organization (not the parent or sibling organizations).

Member Management

Members belong to a specific organization and do not automatically have access to parent or sibling organizations. A user can be:

A member of only the parent organization
A member of only a sub-organization
A member of both parent and sub-organizations (counted once for billing)

Settings Inheritance

Sub-organizations inherit WindowSill settings from their parent organization by default. Administrators can:

Use inherited settings — Sub-organization follows parent configuration automatically
Override specific settings — Customize settings for the sub-organization
Reset to parent — Revert overridden settings to follow the parent again

flowchart TD
    Parent[Parent Organization Settings]
    Sub[Sub-Organization Settings]
    Registry[Local Registry Keys]
    User[User Preferences]
    
    Parent -->|inherited by default| Sub
    Sub -->|overridden by| Registry
    Registry -->|overrides| User
    
    style Parent fill:#e1f5fe
    style Sub fill:#fff3e0
    style Registry fill:#fce4ec
    style User fill:#f3e5f5

Priority (highest to lowest):

Local Registry Keys — Device-specific overrides (see Registry Keys)
Sub-Organization Settings — Team/department configuration
Parent Organization Settings — Enterprise-wide defaults
User Preferences — Individual user settings

Tip

Use parent organization settings for company-wide policies (e.g., telemetry settings). Use sub-organization overrides for team-specific needs.

Billing

Only the parent organization has access to the billing page. The parent organization is billed for all distinct members across:

The parent organization itself
All sub-organizations

If a user is a member of both the parent and one or more sub-organizations, they are counted only once for billing purposes.

Important

Sub-organizations do not have their own billing. All subscription management, invoices, and payment methods are controlled at the parent organization level.

Table of Contents