Individual skill

orchardcore-tenant-hierarchy

Skill for the CrestApps Orchard Core Tenant Hierarchy module, where the Default tenant makes tenants parents that create, manage and open their own child tenants. Covers the Platform, Parent and Child features, the AddTenantHierarchy host guards in Program.cs, the TenantHierarchy configuration section, parent policies, delegated access with a one-time code and PKCE, linked users, access grants, the tenant switcher, isolation guards such as GuardedShellHost and the egress guard, audit trail activity, database strategies and custom IChildTenantDatabaseProvisioner implementations. Use this skill when requests mention Orchard Core tenant hierarchy, parent and child tenants, agency multi-tenancy, entering a child tenant without signing in, or a database per tenant. Strong matches include CrestApps.OrchardCore.TenantHierarchy, ITenantHierarchyBroker, TenantHierarchyAccessDeniedException, ParentTenantPolicy, ChildDatabaseStrategy, DatabasePoolOptions, ManageTenantHierarchy and EnterChildTenants.

plugins/crestapps-orchardcore/skills/orchardcore-tenant-hierarchy/SKILL.md

Read pinned source

Source commit d86d04f234b1b2bd8145368a2544490f9d557596

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
13
Repository last updated
Oct 21, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Orchard Core Tenant Hierarchy - Prompt Templates

## Parent Tenants with Their Own Child Tenants

You are an Orchard Core expert. Generate accurate setup, configuration, extension and troubleshooting guidance for the CrestApps Tenant Hierarchy module. A tenant the platform marks as a **parent** creates, manages and opens its own **child** tenants (for example a bookkeeping firm with one site per client business). The Default tenant stays the platform root and still manages every tenant through Orchard Core's Tenants admin.

### Guidelines

- Install `CrestApps.OrchardCore.TenantHierarchy` (or the `CrestApps.OrchardCore.Cms.Core.Targets` bundle) in the web/startup project.
- Call `AddTenantHierarchy()` on the Orchard Core builder in `Program.cs`, after Orchard Core is added. Without it the platform refuses to make parents and a parent refuses to create children.
- Configuration is host configuration in the `TenantHierarchy` section of the application configuration. Tenant configuration cannot change it.
- Give every tenant its own host name, never a URL prefix, and serve every tenant over HTTPS so the `__Host-` cookies work.
- Code in one tenant of a hierarchy must reach another only through `ITenantHierarchyBroker`. Direct `IShellHost` calls across tenants throw `TenantHierarchyAccessDeniedException`, and HTTP calls between tenants are refused by the egress guard.
- The guards do not stop malicious server code: all tenants share one process, so install only trusted modules.