Executive & Operations View

The operating system for every brand.

Delta Crown becomes the pilot brand for a cleaner ops model: identity tells Microsoft who someone is, Microsoft routes them into the right places, and ops gets predictable access without manually stitching the business together.

Microsoft 365Microsoft 365Tenant foundation
Microsoft Entra IDEntra IDIdentity rules
Microsoft SharePointSharePointHubs + docs
Microsoft Teams collaborationTeamsDaily ops
Microsoft securitySecurityDLP + access
The operating rule Clean identity in.
Clean access out.

Stop treating SharePoint, Teams, mail, and apps like separate chores. Identity becomes the control panel.

Live state 6

Delta Crown users currently resolve through AllStaff. The next ops win is completing titles and departments so the rest of the dynamic groups light up.

The Mission

Ops should not have to remember where every permission lives.

The platform translates one clean person record into the workspace, documents, groups, and app access that person needs. That is the story: fewer one-off fixes, faster onboarding, safer access, repeatable brand rollout.

PeoplePeople are findable

Corporate support sees who belongs to Delta Crown and what role they play.

AccessAccess is explainable

Groups are driven by attributes instead of someone’s memory of a permission rabbit hole.

WorkspaceWorkspaces are obvious

Users land in brand spaces, not the HTT shared-docs junk drawer.

AppsApps can follow

The same identity model can drive FranConnect, Monday, Freshdesk, mail routing, and more.

What Changes By Role

Same platform. Different lens for every level.

The point is not to make everyone look at the same dashboard. The point is to make the same operating truth show up differently for executives, directors, managers, and frontline teams.

Executive

Portfolio confidence

See brand posture, ownership gaps, launch readiness, and risk without opening every site.

Director

Cross-brand comparison

Compare patterns across brands while keeping each brand’s data boundaries intact.

Manager

Faster onboarding

Know who belongs where, which workspace owns the work, and what still needs cleanup.

Frontline

Less scavenger hunting

Open the right Teams space, find the right files, use the right mailbox, and start working.

Identity Is The Control Plane

One person record controls the downstream experience.

Microsoft credentials anchor MFA/passkeys, directory visibility, dynamic groups, SharePoint permissions, Teams membership, distribution lists, and future SSO-backed application access.

Entra ID rules

Ops updates facts, not permissions.

Brand, company, department, title, role, location, manager, and support scope describe the person. Entra ID turns those facts into membership.

companyNamedepartmentjobTitlelocationmanager
User
1. User enters the ecosystemClean Microsoft identity with MFA/passkey-ready posture.
Profile
2. Profile attributes define contextDelta Crown Extensions, role, department, location, support scope.
Groups
3. Dynamic groups activateAllStaff now; Managers, Stylists, Marketing when metadata is complete.
Apps
4. Workspaces and apps light upSharePoint, Teams, mail routing, support tools, future SSO.

Golden Child Layout

The brand workspace is a product, not a folder.

Each Microsoft workspace has a job. Ops gets a clean front door, structured daily-work spaces, and access lanes that are easy to explain.

HubHub

Brand landing page, navigation, announcements, scoped search.

  • AllStaff read
  • Managers own
TeamsOperations

Daily work, bookings, task execution, franchise support rhythm.

  • Microsoft 365 group
  • 6 members live
Brand resourcesBrand Resources

Mapped Master DCE reference folders, playbooks, financial packs, product materials, and franchise resources.

  • Permission-mapped
  • Source-of-truth cleanup
MarketingMarketing

Campaign assets, social content, brand guidelines, launch calendars.

  • Marketing edit
  • AllStaff read
DocsDocs

Policies, SOPs, training, templates, leadership strategy materials.

  • Controlled source
  • No HTTHQ copy

Important: Graph proved the Delta Crown Operations M365 group and membership. Teams channel layout still needs final verification before launch materials promise specific channel names.

The Brand Family

What Delta Crown becomes is what every brand can have.

Delta Crown is the live pilot. The same operating model — clean identity in, clean access out — is the pattern designed to be reusable for Bishops, Frenchies, and TLL when (and if) HTT leadership approves. HTT corporate sits in the center as the shared-services hub. One tenant. One pattern. A platform built to scale to additional brand homes if sponsored.

Corporate Hub

HTT Brands

Shared services for the family
HR · IT · Finance · Legal
Leadership read-up
Hub-to-hub linking
● Live Pilot

Delta Crown

First brand on the platform
Identity + dynamic groups
Hub + spokes
Teams workspace
DLP + isolation
Pattern-ready brands

The next chapters

Same playbook, awaiting sponsorship
Bishops Frenchies TLL
Brand identity rules
Brand hub
Brand Teams

The connecting layer

Each brand is its own room. Corporate is the hallway. Leadership walks the hallway and gets the right view for their role — without giving every brand keys to every room.

Security + Collaboration

Separated securely. Connected securely. On purpose.

The opposite of "siloed" is not "wide open." Each brand stays in its own lane by default, with corporate connections for the things the family genuinely shares — and nothing more.

Separated securely

Each brand owns its space
  • Each brand has its own SharePoint hub and document libraries.
  • Each brand has its own Teams workspace, channels, and shared mailboxes.
  • Data Loss Prevention (DLP) rules block accidental cross-brand sharing.
  • Employees of one brand do not see another brand's content by default.
  • External and partner access is scoped per brand, not tenant-wide.

Connected securely

Corporate sees what corporate needs
  • Corporate hub links every brand for shared HR, IT, Finance, Legal.
  • Leadership has read-up visibility for portfolio-level decisions.
  • Cross-brand collaboration spaces exist only when sponsored and approved.
  • One identity, multiple lenses — same person, different view by role.
  • The directory makes people findable without making data wide open.
The point isn't isolation. The point is intentional connection. Brands stay private. Leadership stays informed. Collaboration happens in approved rooms instead of forwarded emails.

HTT Brands Corporate Access

Delta becomes visible to corporate without becoming wide open.

Microsoft people directory icon

Find the right person

Corporate operators can identify Delta Crown people by consistent Microsoft profile data.

Collaboration

Collaborate in approved spaces

Support teams use the correct Teams/SharePoint spaces instead of ad hoc links and folder archaeology.

Security

Keep authorization separate

Being visible in the ecosystem does not mean access to everything. Groups still decide what opens.

“If identity is clean, access becomes predictable. If access is predictable, operations can scale.”

Repeatable Brand Pattern

Delta is the operating pattern other brands can sponsor next.

01Standardize identity

Brand, company, department, title, role, location, manager, support scope.

02Standardize groups

Dynamic groups, M365 groups, distribution lists, and app roles.

03Standardize workspaces

SharePoint hubs, Teams workspaces, libraries, lists, and permission lanes.

04Standardize apps

SSO-ready access for FranConnect, Monday, Freshdesk, mail routing, and future tools.

The Playbook

Clean identity. Predictable access. Repeatable brands.

Start with a clean person record. Let attributes drive groups. Let groups drive SharePoint, Teams, mail, apps, and support visibility. Then repeat the pattern for every brand.